Secure, managed Hex repositories for Elixir and Erlang teams
Hex is the package manager for the BEAM ecosystem, used by Elixir and Erlang teams to share internal libraries at scale. Cloudsmith gives you a fully managed, private Hex repository with fine-grained access control, governance policies, and full audit trails - no infrastructure to run.
Simplify and streamline operations. Cloudsmith is a secure store for all packages, containers and assets.
- Use Hex + 30 other formats
- Store Elixir and Erlang packages alongside Docker images and OS binaries in a single platform
- Centralize all software artifacts - packages, containers, and raw files - under one governed platform
How we support Hex
mix hex.publish and mix deps.get commands. Cloudsmith acts as a fully compatible private Hex repository with no changes to your existing workflows.Why teams choose Cloudsmith for Hex
Signs you're ready to switch to Cloudsmith for Hex
mix deps.audit runs or bolt-on tools rather than continuous, automated scanning at the registry level. Cloudsmith scans every Hex package on upload so vulnerable packages never reach your builds.Get started with Hex on Cloudsmith
Frequently asked questions
Yes. Cloudsmith acts as a fully compatible private Hex repository. You configure it as a repo in your mix.exs using mix hex.repo add, and from that point all standard commands - including mix deps.get, mix hex.publish, and mix hex.organization auth - work without any modifications to your workflow.
Yes. Cloudsmith performs automatic CVE and vulnerability scanning on all Hex packages at upload time. Findings are surfaced in the Cloudsmith dashboard and you can configure governance policies to quarantine or block packages that contain known vulnerabilities before any team member fetches them.
You can authenticate CI pipelines using API keys or OIDC-based token exchange, removing the need to store long-lived credentials. Generate a scoped API key from the Cloudsmith dashboard and pass it to mix hex.repo add, or use Cloudsmith's OIDC integration for keyless authentication in supported CI environments.
Yes. Cloudsmith's policy engine lets you create rules that govern which packages can enter your repositories. You can block specific package versions, require metadata fields to be present, or automatically quarantine packages that do not meet your defined criteria before any build fetches them.
Yes. Cloudsmith integrates with major identity providers via SAML 2.0, supporting SSO for all users. SCIM provisioning is also supported, enabling automatic user onboarding and offboarding as your team changes without manual management of individual repository memberships.
Yes. A single Cloudsmith workspace supports 30+ package formats including Hex, Docker, NPM, Maven, Python, and more. This gives your security and platform teams a single source of truth for all software artifacts across every format your organisation uses.
Cloudsmith distributes packages via a CDN-backed network with 600+ global edge points of presence. Teams in Europe, North America, and Asia-Pacific all benefit from low-latency dependency fetches, reducing the time your CI pipelines spend waiting on mix deps.get.
Yes. You can upload existing Hex packages directly to Cloudsmith using the Cloudsmith CLI or REST API. Once migrated, you update your repo configuration in mix.exs to point at Cloudsmith, and your team's existing workflows continue without disruption.
Cloudsmith records every package upload, download, policy action, and configuration change in immutable audit logs. You get a full timeline of who published or fetched which package and when, exportable for ingestion into your SIEM or third-party analytics tooling.
Cloudsmith is fully managed. There is no server to provision, no registry software to install, and no infrastructure to maintain. Cloudsmith handles availability, scaling, backups, and upgrades, and provides a contractual SLA so your team can focus entirely on building software.