Moving to Cloudsmith lets a startup data platform eliminate distribution friction and control customer access
A completed migration for a startup technology & software organization from Cloud container registries.
- Company size
- Startup
- Industry
- Technology & Software
- Package formats
- Switching from
- Cloud container registries
Before state
The customer distributed a software agent, used to collect metadata locally within customer infrastructure, to a growing base of enterprise customers using Docker Hub. Docker Hub's high per-seat pricing meant that projected growth would eventually make the distribution model financially unsustainable. The platform also lacked entitlement tokens, so the team could not manage differentiated access levels for individual customers, and usage analytics were limited, leaving little visibility into which software version each customer was running. The interface itself created a confusing experience for end users, driving a steady stream of support inquiries. Facing these limits, the engineering team weighed building a custom distribution platform from scratch against finding a specialized alternative.
Pain points and value drivers
- Docker Hub's high per-seat pricing meant projected growth would make the distribution model financially unsustainable.
- The platform lacked entitlement tokens, so the team could not manage differentiated access levels for each customer.
- Usage analytics were limited, leaving the team with little visibility into which software version each customer was running.
- The interface created a confusing experience for end users, driving a steady stream of support inquiries.
Outcomes
- Eliminated deployment friction, with almost no support questions about image downloads after moving to branded hostnames and Cloudsmith's global infrastructure.
- Gained visibility into exactly who is using which software version through entitlement tokens.
- Strengthened its security posture with automated vulnerability scanning and signed, verified images.
- Avoided the cost and engineering effort of building and maintaining an in-house distribution platform.
- Plans to expand usage to manage hardened images and libraries internally, and to add automated lifecycle and cleanup policies for software versioning.
In their words
“Distributing the Remote Executor in a safe and reliable way was a very important goal.”
“We used to have Docker [Hub] as a main mechanism to distribute the Remote Executor, but ... Docker [Hub] ... did not allow for a large customer base or controls on the artifacts that are being distributed.”
“Cloudsmith implemented this feature called entitlement tokens, and that is exactly what we wanted ... a simple way to tell our customers how to download the artifacts without adding too much complexity into the ... pipelines to deploy the product.”
“The goal is to use Cloudsmith as the gold standard for all the artifacts we use to build and distribute the product.”