From per-repository silos to shared artifacts across plants and teams

A completed migration for an enterprise industrial & manufacturing organization from Mixed or self-managed tooling and GitHub Packages.

Company size
Enterprise
Industry
Industrial & Manufacturing
Package formats
Developers
201–500
Switching from
Mixed or self-managed tooling, GitHub Packages

Technology stack

  • Terraform

Before state

The customer relied on a self-hosted GitHub Enterprise Server to store and manage artifacts, with isolated, per-repository structures. This made it difficult for internal teams to collaborate and nearly impossible for customer plants to access the software they needed. The setup lacked centralized storage, secure sharing, and the high availability of a fully managed, cloud-native platform. It also had no built-in security scanning or governance, leaving the organization exposed to vulnerabilities and licensing risk when using public upstreams, with no way to enforce policies or scan packages before use. Development teams used a wide variety of tools and languages, including Unity, Docker and Python, without native package support or a unified platform, leading to slow builds and a fragmented developer experience.

Pain points and value drivers

  • Per-repository artifact storage prevented real sharing of artifacts between developers and teams.
  • There was no artifact scanning, leaving the organization exposed to vulnerabilities and licensing risk from public upstreams.
  • A wide variety of tools and languages, without native package support, led to slow builds and a fragmented developer experience.

Outcomes

  • Consolidated artifact management for over 200 developers onto one fully managed, cloud-native platform.
  • Gained native support for all package types in use, including Unity, Docker and Python, eliminating the need for multiple tools.
  • Added built-in vulnerability scanning, license compliance and policy enforcement, letting developers block downloads when issues are found.
  • Made it easier to connect customer plants to a central, globally accessible repository than to the previous self-hosted solution.

In their words

“The main problem with our previous GitHub solution is that there was no real sharing of artifacts. The artifacts were stored in a per-repository structure so there was no sharing between developers and teams.”

Team lead DevOpsOn the previous GitHub Enterprise setup

“There was no solution for artifact scanning, which is one of the biggest reasons we moved to Cloudsmith.”

Team lead DevOpsOn the lack of security scanning

“We don't have to think about how to operate the platform. It's fully managed. Now we focus on managing artifacts and security policies, not infrastructure.”

Team lead DevOpsOn moving to a fully managed platform

“With competitors, you are a number. At Cloudsmith, you talk to real people who take your problems seriously.”

Team lead DevOpsOn the support relationship with Cloudsmith
Customers

More success stories

BHS Corrugated

BHS Corrugated replaced fragmented, self-managed repositories with Cloudsmith, giving more than 200 developers a centralised platform for secure artifact management, vulnerability scanning and global software distribution.

  • GitHub Packages migration

ProGlove

ProGlove develops innovative wearable technology for industrial environments. Discover how Cloudsmith supports its software delivery and distribution needs as it brings connected technology to businesses worldwide.

  • JFrog Artifactory migration

Software downloads with license acceptance built in

An industrial wearables maker needed customers to accept its EULA before downloading, with a record of who did. Cloudsmith gave it that, plus individual user management, after a three-month migration from Artifactory.

  • JFrog Artifactory migration