Package management, with enterprise guarantees.

Get contracted support for pixi, rattler and rattler-build and organization-controlled binaries.

Enterprise build
  1. pixi init my-project
  2. pixi add numpy
  3. Resolved in 1.2s
  4. Installed 8 packages

Organization controls

  • Allowed channels
  • Proxy settings
  • Custom certificates
  • Locked configuration

What enterprise support gives you

Contracted support & SLA

Agreed response times, issue triage, and fixes for supported open-source software. Keep your critical workflows running with confidence.

Organization-controlled binary

Enterprise builds that can lock configuration such as allowed channels, proxy settings, certificates, and other policy-sensitive options.

Certificates and PKI

Support for internal CAs, self-signed certificates, and custom trust stores.

Direct maintainer access

A direct line to the engineers who maintain pixi, rattler and rattler-build. No generic support tiers; talk to the people who know the code.

Control what developers can change

Centrally enforce your organization's package management policy while preserving the normal pixi developer experience. Our enterprise builds can lock critical configuration and prevent unauthorized changes.

  • Keep your environments secure and compliant
  • Reduce risk from untrusted sources
  • Use internal CAs, self-signed certificates and custom trust stores
  • Let developers stay productive
# Example configuration
[policy]
channels = ["conda-forge", "prefix.dev/acme"]
proxy = "https://proxy.corp"
locked = ["channels", "proxy", "tls"]

[tls]
ca_bundle = "/etc/acme/ca.pem"
trust_store = "/etc/acme/trust"

# Enforced in the build.
# Not changeable by users.

Support from the people who build it

  1. Your team

    Report issues, ask questions, request fixes

  2. Direct channel

    Talk directly with our engineering team

  3. prefix.dev maintainers

    Triage, investigate, implement fixes

  4. Fix / release

    Get patches and releases through your support channel

Same open-source core. Enterprise controls around it.

Open source

The same projects, developed in the open.

  • pixi: fast, modern package management
  • rattler: core libraries for package management
  • rattler-build: reproducible package builds
  • Public development, issues and community

Enterprise contract

The same open-source tools, with assurances and controls for your organization.

Everything in Open source, plus:

  • Contracted support & agreed response times
  • Supported versions and backports
  • Policy-controlled binaries and configuration
  • Private communication channel
  • Coordinated fixes and releases

How it works

  1. 1

    Talk to us

    Tell us about your use case and requirements.

  2. 2

    Agree scope & SLA

    Define the supported projects, versions and response expectations.

  3. 3

    Receive enterprise builds

    Get your customized binaries and policy configuration.

  4. 4

    Ongoing direct support

    Work with the maintainers whenever you need help.

Questions we get before the first call

Is the enterprise build a fork of pixi?

No. Same source, same release; we compile, configure and sign it.

What happens if we stop paying?

You are on stock pixi. Same source, same version numbers. Swap the binary and projects, lock files and channels keep working.

Will we lag behind upstream releases?

No. Every upstream release is built for you on the same day, with the same version number.

Can pixi be locked to our own channels only?

Yes. Allowed channels, mirrors, proxies and CA certificates are compiled in and not overridable. Private channels on prefix.dev or your on-premises prefix.dev instance both work.

Can we roll it out with our existing installer pipeline?

Yes. Deploy through your installer pipeline or fleet management tooling; updates come from a private self-update channel. Laptops and CI runners get the same binary.

Is there a CVE remediation SLA?

Yes. It covers the tools and their dependencies; the SLA is agreed per organization.

Is a seat one person, regardless of machines?

Yes. One seat per person who runs an enterprise build, on any number of machines. CI runners per agreement.

Are pixi, rattler and rattler-build all covered, on every platform?

Yes. All three on Linux, macOS and Windows.

Is this the same as the Enterprise plan on the pricing page?

No. That plan is package hosting on prefix.dev. This is support and builds for the tools. They can be combined.

Can we get a DPA and a security questionnaire?

Yes. DPA, SBOM and provenance per release, and our CVE remediation policy.

Who is prefix.dev?

The maintainers. prefix.dev GmbH develops and maintains pixi, rattler and rattler-build, and runs the prefix.dev package hosting platform.

Need pixi in a controlled production environment?

Talk directly with Wolf Vollprecht, CEO of prefix.dev, and the team maintaining the stack.

Talk to Wolf, our CEOBook a call