Contracted support & SLA
Agreed response times, issue triage, and fixes for supported open-source software. Keep your critical workflows running with confidence.
Get contracted support for pixi, rattler and rattler-build and organization-controlled binaries.
Organization controls
Agreed response times, issue triage, and fixes for supported open-source software. Keep your critical workflows running with confidence.
Enterprise builds that can lock configuration such as allowed channels, proxy settings, certificates, and other policy-sensitive options.
Support for internal CAs, self-signed certificates, and custom trust stores.
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.
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.
[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.Report issues, ask questions, request fixes
Talk directly with our engineering team
Triage, investigate, implement fixes
Get patches and releases through your support channel
The same projects, developed in the open.
The same open-source tools, with assurances and controls for your organization.
Everything in Open source, plus:
Tell us about your use case and requirements.
Define the supported projects, versions and response expectations.
Get your customized binaries and policy configuration.
Work with the maintainers whenever you need help.
No. Same source, same release; we compile, configure and sign it.
You are on stock pixi. Same source, same version numbers. Swap the binary and projects, lock files and channels keep working.
No. Every upstream release is built for you on the same day, with the same version number.
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.
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.
Yes. It covers the tools and their dependencies; the SLA is agreed per organization.
Yes. One seat per person who runs an enterprise build, on any number of machines. CI runners per agreement.
Yes. All three on Linux, macOS and Windows.
No. That plan is package hosting on prefix.dev. This is support and builds for the tools. They can be combined.
Yes. DPA, SBOM and provenance per release, and our CVE remediation policy.
The maintainers. prefix.dev GmbH develops and maintains pixi, rattler and rattler-build, and runs the prefix.dev package hosting platform.
Talk directly with Wolf Vollprecht, CEO of prefix.dev, and the team maintaining the stack.
Book a call