Predictable costs, proactive support

A completed migration for an enterprise technology & software organization from JFrog Artifactory.

Company size
Enterprise
Industry
Technology & Software
Package formats
Developers
51–200
Switching from
JFrog Artifactory

Technology stack

  • GitLab
  • GitLab CI/CD
  • Terraform

Before state

The customer ran on JFrog Cloud, storing over 15TB of artifacts and growing, across Python, NuGet, npm and Java packages, with GitLab for source control. Usage-based billing was unpredictable. Support was slow and inconsistent: critical tickets took days to resolve, and it took the team almost a year to resolve billing issues. The previous platform's fragmented artifact organization and limited visibility made it difficult to implement comprehensive vulnerability scanning or enforce policy compliance. With the contract set to expire and the security team group demanding stronger software supply chain security, staying on the existing platform would have continued to restrict velocity, security and scalability.

Pain points and value drivers

  • Security was the primary driver behind the migration.
  • Support from the previous vendor was slow and inconsistent, with critical tickets taking days to resolve.
  • An unanticipated data transfer incident alone resulted significant additional charges.
  • Hidden fees and unpredictable costs limited budget transparency.
  • The previous platform lacked visibility into artifacts, limiting security assurance and control.

Outcomes

  • Reduced artifact storage significantly through selective migration.
  • Moved to a fully managed, cloud native platform with transparent pricing.
  • Simplified, consolidated and cleaned up repositories.
  • Achieved faster software delivery and increased control.
  • Reduced risk exposure using built-in security features.
  • Completed the time-sensitive migration using a mono-repo structure, later reorganized into an application-based structure for long-term maintainability.
  • Enabled consistent team-by-team rollout through reusable workflows and example setups built by the platform team.
  • Reduced noise from irrelevant vulnerability alerts, letting teams focus on risks that actually threaten production.
  • Automated quarantine and blocking of non-compliant or vulnerable packages through Enterprise Policy Manager.
  • Consolidated six package formats, including npm, Helm, Maven, Python, NuGet and Docker, into unified multi-format repositories.
  • Eliminated hidden data transfer fees, bringing predictable, transparent costs to the team's budget.
  • Gained direct, proactive support access to engineers, replacing slow, inconsistent vendor support.

In their words

“The migration was pretty painful. We recognized the issues with them relatively quickly. Much of the problem came when we went asking for help, most calls turned into a sales pitch instead of solving the problem. It took months to turn off our original cloud instance, and almost a year to resolve the billing issues.”

VP of architecture and governanceOn the experience of leaving the previous platform

“The most important capability for us is the ability to quarantine and block vulnerable artifacts. Ease of access to vulnerability information, and the ability to act on it, has been the biggest change for us. Our internal governance scores continue to improve, and Cloudsmith has been a major contributor to that. We're a stone's throw away from having zero high or critical vulnerabilities in our supply chain.”

VP of architecture and governanceOn vulnerability management after migrating

“Cloudsmith support responded to us before we even asked the question. They didn't just give us an answer, they monitored the impact and optimized it for us. It felt like they were part of my team. That level of engagement blew my mind. Support here is better than the support I have on any system I'm responsible for. Not just better than JFrog, better than all of them.”

VP of architecture and governanceOn the support experience with Cloudsmith

“With JFrog, once something was running, you couldn't stop it. With Cloudsmith, there's a control panel, I can stop things immediately. I don't have to SSH into a box. That's what cloud-native really means to us.”

VP of architecture and governanceOn operational control after migrating
Customers

More success stories

ConstructConnect

ConstructConnect switched from JFrog Cloud to Cloudsmith to simplify software delivery, strengthen supply chain security and gain greater control over infrastructure costs and global distribution.

  • JFrog Artifactory migration

DataHub

DataHub transformed how it distributes software to enterprise customers, replacing costly distribution infrastructure with Cloudsmith’s secure platform, granular access controls and automated vulnerability scanning.

  • Cloud container registries migration

Font Awesome

Font Awesome replaced an unreliable, self-managed package distribution system with Cloudsmith, improving uptime, performance and the experience of delivering private packages to customers worldwide.

  • Mixed or self-managed tooling migration

Kong Keeps Internet Connected With Cloudsmith Distribution

Kong replaced its resource-intensive, self-managed distribution infrastructure with Cloudsmith, eliminating outages, freeing up three engineering resources and enabling reliable software delivery to more than 40,000 customers.

  • Pulp migration

myob

With hundreds of developers across Australia and New Zealand, myob needed a consistent way to manage and distribute software assets. Cloudsmith provides a centralised platform to simplify artifact management at scale.