Sacra estimates that Anaconda hit $150M in annual recurring revenue (ARR) in July 2025.

The customer base behind that ARR is broad. More than 10,000 large enterprises rely on Anaconda, 95% of the Fortune 500 use it, and the total user base exceeds 50 million across 21 billion downloads. Organizations actively using Anaconda quadrupled in 2024 alone to over one million.

That scale creates a revenue concentration dynamic. Dividing $150M ARR across 10,000 large enterprises implies roughly $15,000 per enterprise, equivalent to about 25 Business-tier seats at list price, which likely functions as a floor rather than a true average.

Larger regulated deployments, self-hosted contracts, and professional services engagements carry materially higher contract values, suggesting a smaller subset of deeply embedded enterprise accounts drives a disproportionate share of revenue.

Anaconda was valued at $1.5 billion in its Series C round, which closed on July 31, 2025. The round raised over $150M and was led by Insight Partners, with participation from Mubadala Capital.

Before the Series C, Anaconda raised financing from BlackRock-managed funds in September 2022.

The company said the round was tied to a 10x increase in new enterprise customers over the preceding two years. Citi Ventures invested in the company in a separate transaction, and Snowflake Ventures participated alongside a partnership announcement in 2021.

The company's earliest institutional round was a $24M Series A in 2015, led by General Catalyst and BuildGroup, when the company was still operating under the name Continuum Analytics.

Total equity funding raised across all rounds stands at $233M as of July 2025. The Series C proceeds are allocated to new AI features, strategic acquisitions, global expansion, and liquidity options for current and former employees.

Anaconda is a common way that data scientists, machine learning engineers, and Python developers set up and manage their software environments, and increasingly a way enterprises govern which open-source packages and AI models their teams are allowed to use.

The core problem Anaconda solves is that Python projects depend on dozens or hundreds of open-source libraries, and those libraries frequently conflict with each other, introduce security vulnerabilities, or behave differently across operating systems.

Without a managed approach, developers end up with slightly different setups, production environments break in unpredictable ways, and security teams lack visibility into what software is actually running inside the organization.

The entry point for most users is Anaconda Distribution, a free installer that bundles Python, the conda package manager, over 300 pre-vetted libraries, Jupyter notebooks, and a graphical interface called Navigator.

A developer installs it once, opens Navigator or a terminal, creates an isolated environment for a project, installs the packages they need from Anaconda's curated channels, and exports that environment as a file so teammates can reproduce it exactly. Navigator provides the same workflow through a point-and-click interface for users who prefer not to use the command line.

For enterprises, the product extends into a governed control plane. Admins configure private channels, essentially an internal software store, so employees can only install packages that have been vetted, scanned for vulnerabilities, and approved by the security team.

Anaconda operates as a B2B SaaS business built on top of a large free distribution base, with monetization concentrated in enterprise governance and deployment controls rather than in the underlying open-source software itself.

The go-to-market structure is a product-led funnel that converts at the organizational level. Individual developers and students use Anaconda Distribution, Miniconda, AI Navigator, and Notebooks for free, creating familiarity with the tooling before any commercial conversation happens.

Teams of up to 15 can self-serve into Starter ($15 per user per month) or Business ($50 per user per month) plans without a sales interaction. Above 16 seats, or for any organization with 200 or more employees, the motion becomes sales-led with custom pricing.

That 200-employee threshold is a monetization mechanism. It draws a line between hobbyist and small-team usage, which Anaconda tolerates as top-of-funnel, and commercial enterprise usage, which requires a paid license regardless of whether the team is using advanced features.

This structure preserves the open-source adoption flywheel while capturing value from organizations most able to pay.

The pricing tiers are designed to mirror an organizational maturity curve. Free gets users into package management and notebooks. Starter adds collaboration. Business adds SSO, vulnerability tracking, policy enforcement, private repositories, and signature verification.

Custom adds self-hosted deployment, AI Catalyst, multi-team governance, and implementation services. Each tier upgrade is typically tied to an operational need such as compliance requirements, security audits, or regulated deployment environments, rather than arbitrary feature gating.

JFrog is the closest enterprise rival when procurement decisions are made by DevOps or platform engineering teams rather than data science organizations.

JFrog's Artifactory natively supports Conda repositories alongside Docker, Maven, npm, PyPI, and OCI artifacts, which means enterprises already standardized on JFrog can treat Python package governance as an incremental use case rather than a separate platform purchase.

JFrog serves roughly 7,300 customers including approximately 82% of the Fortune 100, and over 1,000 customers above $100K ARR, giving it a procurement footprint that Anaconda has to displace rather than complement in many large accounts.

The competitive dynamic is primarily about buying center. When the decision-maker is a data or AI platform owner, Anaconda's Python-specific depth and opinionated workflow tends to win. When the decision-maker is a centralized DevSecOps team looking to consolidate artifact management, JFrog's horizontal platform and existing relationships are often the default.

ActiveState competes directly on the security and provenance axis, explicitly marketing to Anaconda users and framing its platform as a more rigorous alternative.

Where Anaconda's model centers on trusted distribution and policy governance over curated packages, ActiveState emphasizes rebuilding artifacts directly from verified source code, a closed-loop supply chain narrative that resonates in highly regulated accounts where provenance standards are strict.

Posit, formerly RStudio, competes through its Package Manager product in organizations that run significant R workloads alongside Python. Since Anaconda deprecated active maintenance of its R channel in November 2025 to concentrate on Python, Posit becomes more attractive wherever package governance is inseparable from R publishing and analytics application deployment.

Posit's competitive strength is workflow adjacency: Package Manager is sold as part of a broader analytics operating environment including Workbench and Connect, which mirrors Anaconda's own bundling logic.

Databricks and Snowflake occupy an unusual position as both distribution partners and long-term threats.

Anaconda has a native integration with Databricks and a partnership with Snowflake that embeds Anaconda packages into their Python execution environments. These relationships increase Anaconda's reach and make it easier for Anaconda to become the default curated package layer inside enterprise AI estates.

Both platforms are also building more self-sufficient dependency management. Snowflake's Artifact Repository supports package policy controls across both Anaconda packages and PyPI, and Databricks increasingly pushes customers toward first-party governance primitives. The risk is that once a platform owner proves it can govern Python dependencies natively, customers may question whether a dedicated third-party package governance layer is still necessary.

Astral's uv is a Rust-based tool that replaces pip, virtualenv, pyenv, and related utilities with a single fast binary, and it is gaining adoption among Python developers who find Conda's complexity unnecessary for pure-Python workflows. uv does not replicate Anaconda's enterprise governance or binary package management for compiled scientific libraries, but it erodes Anaconda's developer convenience moat in workloads that do not require those capabilities.

prefix.dev and its Pixi tool attack from the conda-adjacent angle, offering private channels, security attestations, lockfiles, and conda/PyPI interoperability with a more modern developer experience than classic Conda workflows. If prefix.dev matures its enterprise controls, it could become the preferred front end for teams that want conda-forge reach without Anaconda's commercial licensing posture.

Anaconda's near-term TAM expansion is the extension of its package governance model to AI models and datasets through AI Catalyst.

The enterprise problem is structurally similar to the package problem Anaconda already solved: open-source models are proliferating, but enterprises cannot consume them directly without validation, licensing review, security scanning, and deployment controls. AI Catalyst gives organizations a curated model catalog with benchmarks, quantized variants, AI Bills of Materials, policy controls, and governed deployment pathways to private cloud or self-hosted inference servers.

This product extension uses the same trust infrastructure, curation, metadata, provenance, and policy enforcement, that Anaconda already built for packages, applied to a new artifact type with a larger and faster-growing governance problem. It also expands the buyer from data science teams to AI platform owners and CISOs, who are increasingly responsible for open-source model risk.

Anaconda's traditional buyer has been the data science team or the platform engineering group supporting it. The platform's evolution toward security, compliance, and deployment governance opens the buying conversation to CISOs, IT administrators, and procurement teams with larger and more durable budgets.

The Excel integration is an important top-of-funnel expansion. Anaconda Code and Anaconda Toolbox for Microsoft Excel bring Python capabilities directly into spreadsheets, reaching analysts, finance teams, and operations users who would not start in a terminal or Jupyter notebook. This creates a ladder from spreadsheet-native usage into managed environments, private channels, and enterprise governance, converting a population that was previously outside Anaconda's addressable market into a potential upgrade path.

The Databricks partnership reinforces this expansion into regulated industries. Financial services, healthcare, and government organizations face the sharpest collision between open-source AI adoption and governance requirements, making them the most likely to pay for curation, controls, and on-premises deployment. These are also the accounts where contract values are highest and switching costs are most durable.

Anaconda's support for self-hosted, on-premises, private cloud, and air-gapped deployments makes it suited to multinational enterprises that need region-specific data residency or sovereign AI architectures, requirements that are common in Europe and government markets where purely SaaS AI tooling is often a non-starter.

The EU AI Act's obligations for general-purpose AI models, which began applying in August 2025, increase demand for internal systems that document model and package provenance, control distribution, and support auditability. Even where Anaconda is not itself the model provider, this regulatory backdrop increases the value of its governance tooling internationally and creates a compliance-driven buying trigger that did not exist two years ago.

The combination of deployment flexibility and regulatory alignment gives Anaconda a basis to expand share in markets such as government, financial services, healthcare, and European enterprise, where governance requirements are most acute and willingness to pay is highest.

Platform absorption: Anaconda's value proposition sits between enterprises and open-source ecosystems, but the platforms where Python actually runs, Databricks, Snowflake, and major cloud providers, are all building more native package and dependency governance capabilities. If those platforms internalize enough of the governance workflow, Anaconda risks becoming an optional premium layer rather than a required control point. Its partnership distribution strategy could accelerate that outcome by training customers to expect those controls as built-in features.

Trust failure: Anaconda's business depends on serving as a trusted intermediary for open-source software and AI artifacts, the entity that validates, scans, and curates so enterprises do not have to. A significant missed vulnerability, a lag in model or package freshness, or a failure to keep pace with emerging compliance requirements such as EU AI Act documentation standards would cut into its primary differentiation rather than a peripheral feature. Recovery could be difficult given how deeply embedded Anaconda is in enterprise development workflows.

Tooling commoditization: The developer tooling layer below Anaconda is improving quickly. Tools like uv eliminate the need for Conda in pure-Python workflows, prefix.dev and Pixi offer a more modern conda-adjacent experience, and PyPI's own security posture is strengthening through Trusted Publishing and attestations. If environment management becomes fast, cheap, and secure enough through commodity tools, Anaconda may be forced to compete primarily on compliance ROI in regulated verticals rather than on developer convenience across the broader market, a narrower and more competitive position.