Perl
ActivePerl: Perl Distributions & Enterprise Support
The Trusted Perl Distribution, Backed by Enterprise Support
ActiveState builds and maintains ActivePerl for Windows and Linux. Existing customers can log into download current builds. New to ActiveState? Talk to our team to get access, whether you need a specific version (Perl 5.32 and above) or an enterprise deployment.

Get ActivePerl
Existing customers: Log in to download your current ActivePerl build.
New to ActiveState? ActivePerl access is provided through our team, not a public download. Contact us to get set up, whether that's a standard Windows/Linux/macOS build, or an enterprise support agreement.
The ActivePerl distribution includes:
Core Perl interpreter
Pre-verified third-party modules
Comprehensive documentation
PerlScript & ISAPI (Windows only)
Running Perl in Production? Here's the Real Risk.
The language isn't the risk. Running it unsupported is. Outdated interpreters, unpatched CVEs in CPAN dependencies, and no clear path forward when something breaks in a system nobody currently on staff originally built, that's what turns a stable legacy system into a liability.
ActiveState offers commercial support, core language remediations, and custom builds for teams that can't afford downtime or an unanswered vulnerability.

Why Teams Choose ActiveState for Perl
Supported Perl distributions
Built, tested, and maintained releases across the versions enterprises actually run in production, including versions no longer supported by the community.
Security patching and CVE remediation
On a contractual SLA, not best-effort, including CPAN module dependencies and core language remediations.
Migration and modernization support
For teams moving off end-of-life versions, consolidating custom builds, or migrating specific workloads off Perl entirely.
Who This Is For
Security and infrastructure teams
responsible for systems they didn't build and can't easily replace.
Engineering leaders
who need a defensible answer when an auditor asks about EOL software in production.
Organizations
evaluating whether to maintain, migrate, or replace legacy Perl systems and need expert guidance either way.
FAQs
Still have questions?
Talk to our team.
How does a Curated Catalog work with my existing tools?
It acts as a trusted upstream source for your artifact repository. Developers pull from the catalog instead of public registries. AI coding assistants can also be pointed to it, keeping AI coding on rails.
Will a Curated Catalog slow down my developers?
No, the opposite. Components are pre-vetted, so developers skip security approvals and CVE cleanup. Same workflow, secure by default.
Is there a cost to use ActivePerl?
Community-tier runtime builds are available at no cost for existing customers. Enterprise-level commercial support, custom builds, and indemnification are available on a paid basis.
What platforms does ActiveState provide ActivePerl builds for?
Windows and Linux for standard builds.
What's the difference between ActivePerl and the Curated Catalog?
ActivePerl is ActiveState's built, tested Perl distribution. The Curated Catalog extends the same model of vetted, continuously remediated builds across every open source language your organization runs, not just Perl.
What does "built from source" actually mean?
ActiveState compiles every component from original source code in a SLSA Level 3 environment, rather than distributing pre-compiled binaries. This provides full transparency and tamper-proof integrity.
Who do I talk to about a Perl support contract or enterprise licensing?
Use the Contact Us form on this page. A member of our team will follow up directly.
Running More Than Perl?
If Perl is one piece of a larger open source footprint, the Curated Catalog extends the same model, vetted, continuously remediated builds, delivered through the artifact repositories and package managers your teams already use, across nine modern ecosystems: Python, JavaScript, Java, .NET, C, C++, R, Go, and Rust.
Same standard your Perl deployment gets. Same governance, applied everywhere your developers are pulling packages from.
