From four multi-day outages to none

A completed migration for an SMB government & nonprofit organization from Mixed or self-managed tooling.

Company size
SMB
Industry
Government & Nonprofit
Package formats
Switching from
Mixed or self-managed tooling

Technology stack

  • Snyk
  • Identity and access management

Before state

The customer ran a self-hosted artifact repository for years to support a growing educational software platform built on microservices. The setup worked while the platform was small, but as the number of microservices grew from around seven to more than forty, the system began to fail. The repository repeatedly ran out of disk space, causing multi-day outages while the team manually extended disks to work around the problem. This happened four times in total, and the backups for the repository eventually grew larger than the organization's other backups combined. The engineering team spent significant time firefighting these issues instead of building new features, while the organization was also planning a broader move of its infrastructure to AWS.

Pain points and value drivers

  • The self-hosted artifact repository could not scale past roughly 40 microservices without the system starting to fail.
  • The repository repeatedly ran out of disk space, causing multi-day outages that required manual fixes.
  • Backup size for the repository grew to dwarf the size of the organization's other backups.
  • Engineering time was consumed by firefighting infrastructure problems instead of building features.

Outcomes

  • Eliminated outages from running a self-hosted artifact repository.
  • Reduced the storage footprint significantly compared to the legacy setup.
  • Scaled from around 40 to over 100 microservices in production without added operational burden.
  • Freed the engineering team to focus on higher-value work instead of maintaining infrastructure.
  • Strengthened its security posture through dependency proxying, vulnerability scanning and SSO integration alongside Snyk.
  • Completed the migration in about a month, with hands-on support throughout.

In their words

“Once we [migrated to Cloudsmith and] stopped having outages and operational issues, our team was totally free to focus on higher-value tasks instead of maintaining our artifact repository.”

Chief technology officerDescribing the impact of the migration

“When we started off with our self-hosted artifact repository we had 7 microservices which was fine but when we approached the 40 something mark, that’s when things started to fall apart. We now have 100+ microservices in production with Cloudsmith and we’re scaling with ease.”

Chief technology officerOn scaling past the limits of the legacy setup

“Our primary goal was to eliminate the overhead of managing a self-hosted solution while improving security, scalability, and performance.”

Chief technology officerOn the goal of the migration

“Cloudsmith’s support team was excellent. They were always responsive and proactive. They made migration seamless and were with us every step of the way, troubleshooting issues in real-time via Slack.”

Chief technology officerOn working with Cloudsmith during the migration

“The usability is great, I’m a release manager so I’m in the product at least 5 to 10 times a day and I find it really easy to use; I never struggle to find anything.”

QA managerOn day-to-day use of the platform
Customers

More success stories

ISC - The Internet Systems Consortium

The Internet Systems Consortium manages thousands of software packages used by developers and organisations worldwide. Cloudsmith helps ISC ensure consistent, controlled package availability and reliable distribution at global scale.

The New England Center for Children

The New England Center for Children moved away from an unreliable, self-hosted repository to Cloudsmith, eliminating outages, reducing storage overhead and scaling its platform to support more than 100 microservices.

  • Mixed or self-managed tooling migration