Software Artifact Management Features | Cloudsmith

Platform Features

Cloud-native Artifact Management

Gain complete control over every package, container and software asset used across your business. Use Cloudsmith as the single source of truth for your work.

Unlimited packages and repositories

Use Cloudsmith to store every package, container, model and dataset.

Core package management

Use package managers or our CLI to push and pull software artifacts.

30+ formats supported

Native support for 30+ package formats, Hugging Face assets, and raw files of any type.

Private repositories

Secure access to your software artifacts using access controls and private repos.

Public repositories

Share your packages publicly or with customers using Cloudsmith Broadcasts.

Multi-format repositories

Bring related artifacts together, and manage dependencies in your preferred pattern.

Connected repositories

Link repositories together so packages resolve across them through a single endpoint.

Container registry

Bring your containers to Cloudsmith and unlock a single source of truth for all software dependencies.

Raw files

Manage files of any type and serve them along with your software packages.

Proxy and cache upstream registries

Packages pulled from OSS registries pass through checks and policies en route to developers.

Retention rules

Keep your workspace tidy and costs down by deleting unwanted packages.

Custom domains

Wrap Cloudsmith's delivery endpoints in your own domain.

Workflow Integrations

Connect Cloudsmith to your CI/CD platforms, configuration management tools and container registries using the CLI, REST API and official plugins.

Cloudsmith CLI

Configure and interact with your Cloudsmith workspace without leaving the terminal.

Cloudsmith Github action

Build software using GitHub actions and push directly to Cloudsmith.

Terraform Provider

Cloudsmith is verified Terraform provider, enabling you to configure resources automatically.

CircleCI orb

Publish packages to Cloudsmith with the help of our CircleCI orb.

Webhooks

Use a range of actions taken on Cloudsmith to trigger webhooks and third-party integrations.

Package promotion workflows

Carry out checks and then automate how packages move between your repos.

CI/CD platforms

Publish and pull packages from GitLab CI/CD, Jenkins, Azure DevOps, Bitbucket Pipelines, Buildkite and more.

Configuration management

Distribute packages to your fleet with Ansible, Chef and Puppet.

Dependency update tools

Keep dependencies current from your own repositories with Dependabot and Renovate.

Canonical upstreams

Connect Docker Hub, Docker Hardened Images, Chainguard, RapidFort and WizOS as upstream sources.

Slack and Microsoft Teams

Send Cloudsmith events to the channels where your teams already work.

Datadog

Bring Cloudsmith observability data into your existing monitoring.

IDE extensions

Work with Cloudsmith from VS Code, Cursor and Theia.

MCP support

Use MCP through the Cloudsmith CLI to connect AI tooling to your workspace.

Machine learning

Integrate with MLflow and AWS SageMaker to manage your models alongside your software.

Frequently Asked Questions

  1. What is a repository in Cloudsmith?
    A repository is a storage location for software packages and containers. Each repository has its own permissions, policies, upstream sources and retention rules, and you can create as many as you need.

  2. Can one repository hold packages of different formats?
    Yes. Cloudsmith repositories are multi-format, so one repository can hold packages of every supported type and related artifacts can live together.

  3. What are connected repositories?
    Connected repositories link multiple Cloudsmith repositories so packages from all of them resolve through a single repository and a single endpoint.

  4. Does Cloudsmith have virtual repositories?
    Connected repositories are Cloudsmith's equivalent of virtual repositories.

  5. How does upstream proxying and caching work?
    Cloudsmith can proxy packages from upstream registries such as PyPI, npmjs and Docker Hub, and optionally cache them in your repository.

  6. How do I keep repositories from growing out of control?
    Retention rules automatically delete packages that exceed a repository's configured limits for count, age or total size.

  7. Can I serve packages from my own domain?
    Yes. Custom domains can be account-wide, working across all repositories in your organization, or per-repository.

  8. Can I use Cloudsmith as a container registry?
    Yes. Cloudsmith includes a Docker registry where you can push images, and you can configure upstream Docker registries and cache the images your teams request.

  9. What can I control on each repository?
    Each repository has its own settings for access controls, upstream proxying, retention rules, Geo/IP rules, entitlement tokens, EULA enforcement, custom domains, webhooks, signing keys, license compliance and security scanning.