Cloudsmith Enterprise Artifact Management

What do you like best about the product?

What I like best about Cloudsmith is its support for a wide range of package formats like Docker, RPM, DEB, and more — it’s incredibly versatile and saves us time managing multiple repositories. I also really like the new web app; it's clean, modern, and intuitive to use, which makes everyday tasks much easier and more efficient.
On top of that, having a direct Slack channel with the Cloudsmith developers has been incredibly helpful, their responsiveness and willingness to assist make a big difference.

What do you dislike about the product?

For the way I’ve used Cloudsmith so far, I’ve identified a few areas that could be improved:
• Intermittent CI/CD install failures – our pipelines sometimes fail when adding repositories; a simple re‑run usually succeeds, but the flakiness costs time.
• New web‑app usability – there’s no “select all packages on this page” option, and for DEB / RPM packages the target distribution and architecture aren’t immediately visible (both these were available in the old web-app).
• Bulk deletion via API – it would be much handier to delete packages in groups instead of having to specify each one individually.
• openSUSE repo re‑installation – reinstalling a repository that already exists fails on openSUSE, whereas the same action works on RHEL and Debian/Ubuntu.
• Distinct RPM icons – SLES and RHEL packages use the same logo; separate icons would make them easier to tell apart.
• Multi‑platform Docker copies – when copying a multi‑platform Docker image from one repo to another (via API or UI), only the primary image gets copied; the additional ones are left behind.

What problems is the product solving and how is that benefiting you?

Cloudsmith helps us solve the challenge of managing multiple types of artifacts in one place. We use it primarily as a repository manager and Docker registry, which allows us to centralize and secure our packages, streamline our CI/CD pipelines, and simplify customer access.

What do you like best about the product?

Doesn't have frequent outages, pulls images as and when necessary

What do you dislike about the product?

nothing particular, it's pretty convenient to use

What problems is the product solving and how is that benefiting you?

We store binaries for our repositories

What do you like best about the product?

Cloudsmith provides a simple UI to configure multiple internal and external repositories for various projects and repository types. We have some configured for our internal development uses and others for distributing artefacts and container images to customers.

We moved to Cloudsmith from Sonatype Nexus repository OSS to gain support and move to a hosted solution. The onboarding was simple, and it was easy to get our CI pipelines integrated with the service.

I particularly liked that Cloudsmith can handle the signing of RPMs, which previously was cumbersome and prone to breaking in our automated pipelines.

The ability to throttle and limit individual entitlement tokens has also been a key tool for us.

What do you dislike about the product?

When we first started using Cloudsmith, on paper it seemed like it ticked a lot of boxes, with security scanning, audit logging and it would allow us to simplify all our disparate repository services into one. As we are a small ISV, we opted for the Pro plan, as $700 per month to host some artefacts seemed like a silly amount of money. We understood the usage-based limits of our plan; however, we quickly realised that many of the features we liked about Cloudsmith also required the next tier plan. Even things as simple as audit logs to identify excessive bandwidth use.

Unfortunately, looking at the cost of artefact management solutions, it seems that this pricing is the norm. Whilst we like what Cloudsmith offers, the value for money doesn't quite stack up in the way it is currently priced.

What problems is the product solving and how is that benefiting you?

Consolidating multiple disprate repositories. Hosting artifacts and containers for customers and developers.

What do you like best about the product?

We chose it for its strong supply chain security, especially its protection against dependency confusion and package tampering. Our teams appreciate the visibility into package usage, automated policy enforcement, and centralized artifact management, all of which supported internal compliance and developer experience.

What do you dislike about the product?

There is some toil and operational overhead with Cloudsmith, including:

Manual steps required for initial rollout and configuring coverage across all services and the usage dashboards are not as detailed as we would have liked

What problems is the product solving and how is that benefiting you?

It has helped to simplify our internal compliance through license checks/policy enforcement & has improved developer velocity by giving teams a single, managed registry for both internal and third-party packages. This reduces friction in our CI/CD workflows and makes it easier to control what goes into our prod environment.

What do you like best about the product?

Cloudsmith is easy to set up, reliable, and supports multiple package formats in one place. The UI and CLI are both intuitive, and it fits nicely into our CI/CD pipelines

What do you dislike about the product?

Pricing can become a bit expensive at scale, especially with lots of artifacts, but overall the value is still strong.

What problems is the product solving and how is that benefiting you?

It replaced the need to host and manage our own Maven repository. Cloudsmith gave us a reliable, secure way to publish and distribute Java packages without the operational hassle.