Migrating to Cloudsmith lets an enterprise fintech move all pipelines to a single source of truth
A completed migration for an enterprise financial services organization from Azure Artifacts and Cloud container registries.
- Company size
- Enterprise
- Industry
- Financial Services
- Package formats
- Developers
- 51–200
- Switching from
- Azure Artifacts, Cloud container registries
Technology stack
- Security tooling
- Terraform
- Intune
- Jamf
Before state
The organization ran a fragmented artifact setup across Azure Artifacts and Azure Container Registry, neither of which covered every format the organization relied on. Developers pulled directly from public registries, leaving security with limited ability to block risky downloads. No lifecycle controls were in place, leading to storage sprawl for container images.
Pain points and value drivers
- Artifact management was fragmented across Azure Artifacts and Azure Container Registry, with neither covering every format in use.
- Developers pulled directly from public registries, leaving security with limited ability to block risky downloads.
- No lifecycle controls were in place, leading to storage sprawl for container images.
Outcomes
- All pipelines were migrated within three months, with cooldown policies introduced shortly after.
- A single source of truth now covers all artifacts, with ingestion controlled centrally through malware blocking and cooldown policies.
- Retention rules have already reduced storage sprawl.
- Developer rollout was automated using device management scripts, extending coverage to a tail of non-engineers using AI coding tools.
- Container tooling costs are being reduced, since Docker pulls and controls are now managed centrally.
- Consolidating endpoint security tooling on developer machines into Cloudsmith is under consideration.