By submitting this form, you agree to our 

Across your organization, teams are rapidly adopting AI and machine learning. They’re pulling ML models and datasets from public sources like Hugging Face and wiring them into workflows that are now reaching production. For platform and security leaders, this creates a familiar challenge: artifacts are entering the software supply chain outside established governance and controls.

Unmanaged AI artifacts carry real risks. They can’t be traced back to their source, they don’t follow compliance processes, and they often bypass the review gates you rely on for code and containers. Left unchecked, they become blind spots and liabilities in your supply chain. Without action, AI artifacts become the weakest link in your supply chain security.

The answer is to manage ML models and datasets with the same level of control and oversight as every other artifact in your supply chain. By managing them through a unified platform—with shared repositories, consistent policy enforcement, and full observability—you ensure that ML workflows are governed by the same standards as the rest of your software supply chain.

The growing adoption of ML models and datasets introduces both opportunity and risk. On one hand, models accelerate delivery by enabling new capabilities at unprecedented speed. On the other hand, they introduce opaque dependencies, security blind spots, and compliance risks into the supply chain—areas where governance practices are still catching up.

Some risks begin earlier in the lifecycle, like poisoned training data or tampered weights during model creation, which can compromise a model before it ever reaches a registry. But the most immediate challenge for platform and security leaders is governance once these artifacts enter the supply chain. Teams often pull models directly from public sources like Hugging Face, bypassing review and scanning. Without versioning and provenance tracking, it’s nearly impossible to prove which model is in use, where it came from, or what depends on it. And without consistent policies, organizations struggle to demonstrate compliance when auditors or regulators come calling.

These risks can’t be left unmanaged. The question is how to bring ML artifacts under control.

ML models and datasets are artifacts, and like any artifact, they need to be versioned, audited, and controlled with the same enterprise-grade policies you’ve put in place for packages like code libraries and container images. As organizations deliver production applications powered by AI, the priority for platform and security leaders is clear: maintain visibility, integrity, and trust in the components that make up these builds.

Cloudsmith’s new ML Model registry support

A Single Source of Truth for ML Models in DevOps

Cloudsmith extends artifact management to ML models and datasets, promoting them to first-class artifacts in your supply chain. This means you can control, secure, and distribute models alongside your language libraries, containers, and other binaries, all governed by the same policies and observability already in place.

: Require approvals, license checks, and compliance gates before a model or dataset is deployed.

: Every artifact is versioned, hashed, and immutable, so tampering can be detected and blocked.

: Capture where a model or dataset came from, how it has changed, and what depends on it.

: Manage ML models (PyTorch, TensorFlow, ONNX, and more) alongside other binary artifacts in the same repositories.

: Proxy and cache models and datasets directly from the Hugging Face Hub, while continuing to use the Hugging Face SDK for training and deployment — ensuring developers keep their workflows while you enforce governance.

DevOps has always been about balancing efficiency, stability, and security. The rise of ML workflows doesn’t change that balance - it heightens the need for it. By incorporating ML models and datasets into Cloudsmith, you extend the same supply chain controls that protect your code and containers to the AI artifacts now driving production systems.

The result: faster innovation without unmanaged risk, and a single platform to govern every component that ships to production.

Learn more about Cloudsmith's ML Model Registry here.

Alison Sickelka

VP of Product

Extending Supply Chain Governance to AI and ML Artifacts

Healthy competition makes industries stronger, products better, and benefits customers. JFrog has recently published two blog posts (

) criticizing our platform, a clear sign that Cloudsmith’s approach - built cloud-native, open, transparent, and customer-focused - is winning over customers.

JFrog’s own CEO has framed Cloudsmith as just “

fluffy marketing spin and empty presale promises.

” We disagree strongly. Our platform is proven in production every day, powering software delivery for some of the world’s most demanding organizations. Enterprise customers 

use Cloudsmith to build, secure and deliver software at scale

. And we are open about our capabilities for anyone to evaluate firsthand, through a 

 that shows exactly what it’s like to work with Cloudsmith.

JFrog’s latest tests seem intentionally designed to mislead. Rather than respond point by point, we invite customers to conduct their own comparisons. We welcome head-to-head evaluations because this is where our truly cloud-native, massive-scale architecture really shines. We believe our vision for the software supply chain serves customers best today and into the future. We’ve faced off against JFrog in a number of competitive situations recently, and we’ve won more than we’ve lost. It’s the spirit of healthy competition that has prompted all of this recent attention from JFrog. We welcome it.

JFrog has been able to test our platform because we let them trial Cloudsmith, too. The same cannot be said about JFrog, since they block our domain (and possibly others) from even signing up. This lack of openness ultimately hurts customers; many large organizations have multiple artifact management systems in place, and access to both systems would let us better support customers’ interoperability requirements.

Openness and transparency are core to who we are

: “Hide nothing, then there is nothing to hide.”

Openness and honesty, both in how we operate our business and how we communicate, are essential for building trust with customers and also how we work together as Cloudsmithers. Transparency is second nature for Cloudsmith; it’s how we make decisions, share information, and hold ourselves accountable.

We avoid that “lies, damned lies, and statistics” feeling when sharing information. We focus on facts, context, and clarity.

That’s why anyone can sign up for a Cloudsmith developer account - yes, even if you’re from JFrog - and experience our platform firsthand; no gatekeeping, no NDA. It’s why we share platform status and service issues, no matter how minor; it’s more important to share the small stuff than to stick to a claim of “flawless 100% uptime.”

Transparency isn’t just fluffy marketing - it’s how we operate, every day.

We believe in Community and Open Ecosystems

Security of the software supply chain depends on collaboration. From open standards to public registries, collaboration is how enterprises actually build software securely and at scale. We support open ecosystems because they accelerate innovation and benefit everyone.

Closed platforms and walled gardens are tempting to legacy software vendors like JFrog, but they inevitably lead to lock‑in and slow progress. Our approach is different: Cloudsmith is designed to integrate, not isolate. We recognize that we are the trusted control plane and data plane for software artifacts. To do that effectively means working alongside the tools and ecosystems our customers already rely on, rather than forcing a single‑vendor stack.

Competition pushes every company to deliver more value to customers. We welcome direct competition with JFrog because it helps us to improve our platform and our customer experience.

Artifact management is critical infrastructure. Software teams depend on us to build, secure, and deliver their products. Choosing an artifact management platform is a decision about who you trust, and who you want to work with for the next 5-10 years and beyond.

Cloudsmith’s growth has been built on long‑term partnerships. We understand our customers’ needs, deliver meaningful improvements, and act as a trusted partner as requirements evolve. That’s what real competition is about: 

Competition, transparency and building the future of the Software Supply Chain

Exploring AI and the future of the software supply chain

AI assistants will shape the future of the software supply chain, and today, we’re sharing a glimpse of a powerful idea in motion: 

 server that connects large language models (LLMs) like ChatGPT and Claude directly to your software supply chain using the emerging 

Imagine managing policies, surfacing security insights, or orchestrating package workflows with a simple natural language prompt. No dashboards, no scripting, just a simple question or instruction that delivers the right end result. If this sounds interesting, you should 

This isn’t a launched product (yet), but it’s a clear signal of where we think Cloudsmith is headed: toward 

 that make it easier to control your software supply chain.

is a standard way to make information available to LLMs. Similar to an API, MCP provides a documented, standardized way for a client to integrate services from external sources.

MCP enables AI assistants to query and interact with software supply chain data, so it creates a foundation for smarter workflows and more accessible control over artifact management.

In essence, adding MCP capabilities to Cloudsmith offers up an entirely new interface to your software supply chain, with AI agents and LLMs working together to achieve your goals. We're exited to see MCP becoming a flexible new point of integration between our customers' third-party services and Cloudsmith.

MCP server demo

Our MCP prototype leverages Cloudsmith’s API-first architecture to provide programmatic access to developers through their AI assistant. Through standardized MCP requests, you can ask questions about your software supply chain or take safe, controlled actions - like managing policies or promoting packages - directly within Cloudsmith. This opens up conversational workflows with the Cloudsmith platform.

For example, you might ask your AI assistant to identify what package is trending up in usage month over month or see all of the versions of a particular package in use across your workspace. In the future, your AI assistant will be able to review your organization’s compliance and security requirements and recommend or create a set of policies in Cloudsmith’s Enterprise Policy Manager based on that input.

Building this prototype was a good reminder of a few fundamentals. First, an API-first foundation makes it easier to experiment, so it’s good that Cloudsmith is built truly API-first. Second, the data running through platforms like Cloudsmith can offer valuable insights when it’s made accessible to clients in lots of different ways. We’re giving developers and AI assistants simpler ways to ask questions, take actions, and get things done.

There’s still plenty to figure out, but MCP is already making artifact management and software supply chain management more intuitive and straightforward, especially at enterprise scale.

 for select customers and partners. If you're exploring the intersection of DevOps, AI, and supply chain security, we’d love to work with you. 

Prototyping an MCP Server

Your software artifacts are your intellectual property; that’s why Cloudsmith is built to put you in control. Cloudsmith provides a flexible, powerful permissions system and 

 to control authentication, team membership and manage your users' lifecycle.

Managing users across hundreds of applications and systems can be a painful process, though. And we want Cloudsmith to be the artifact management platform of choice for enterprise customers. So we are pleased to let you know that we are expanding on the System for Cross-domain Identity Management (SCIM) capabilities in Cloudsmith. By integrating Cloudsmith with your identity provider (IdP) via SCIM, you can automate provisioning and de-provisioning users in Cloudsmith, letting your IdP serve as your single point for managing user access in Cloudsmith.

What is the System for Cross-domain Identity Management (SCIM)?

SCIM, or System for Cross-domain Identity Management

, is an open standard designed to manage user identity information. SCIM communicates user identity data between IdPs such as 

, and service providers requiring user identity information (such as enterprise SaaS apps, like Cloudsmith). SCIM uses RESTful APIs to transfer user data between systems.

SAML is primarily used for single sign-on (SSO) authentication between applications and systems. SAML enables users to log in once to a single system, proving they are who they say they are, and then access multiple other systems without having to log in again.

Where SCIM differs is that it is API-based, not login-based. When changes to identities are made in the IdP, including create, update, and delete, they are automatically synced to the service providers (like Cloudsmith) according to the SCIM protocol. For end users, this means that they have seamless access to applications for which they’re assigned, with up-to-date profiles and permissions.

Get Early Access to SCIM on Cloudsmith Now

To demonstrate our commitment to providing enterprises with the control they need, we are offering early access to SCIM provisioning and de-provisioning capabilities. By participating in the early access program, you get an exclusive opportunity to explore these capabilities firsthand and shape the final release with your feedback.

To sign up for early access, please reach out to 

. We look forward to partnering with your enterprise on this journey of enhanced control and efficiency.

Thank you for choosing Cloudsmith as your trusted platform. Stay tuned for more updates as we continue to empower enterprises with cloud-native artifact management.

Take control of user management with Cloudsmith's new SCIM capabilities

CircleCI, a Continuous Integration/Continuous Delivery service, 

 that they were investigating a security incident that impacted their platform and customers. CircleCI included in the disclosure recommended actions all customers should take in response to the incident.

Cloudsmith leverage CircleCI as an orchestrator for our build and deployment processes, and when we became aware of the incident, we immediately followed the recommended set of actions.

Cloudsmith already has a policy to ensure secrets are rotated regularly. However, directly after the disclosure of the CircleCI incident, we rotated every secret held within the secure contexts of our pipelines. All access tokens, OAuth tokens, SSH keys, and PGP keys contained within these contexts were rotated.

As an additional measure, we have consulted with audit logs within CircleCI, our SCM service, and our internal services to verify that no unauthorized access attempts were made at any time. This has also been cross-referenced with our observability platforms.

Cloudsmith Blog

Extending Supply Chain Governance to AI and ML Artifacts

Competition, transparency and building the future of the Software Supply Chain

Prototyping an MCP Server

Take control of user management with Cloudsmith's new SCIM capabilities

Cloudsmith's response to CircleCI security incident