Companies that use Cloudsmith

Source: Analysis of job postings that mention Cloudsmith (using the Bloomberry Jobs API)

My analysis shows that Cloudsmith purchasing decisions are driven primarily by DevOps and platform engineering leadership, with DevOps Engineers and SREs representing 42% of hiring activity, followed by Backend Engineers at 21%. These teams are prioritizing artifact management, CI/CD pipeline acceleration, and supply chain security. Directors of Customer Support and Sales roles account for only 10% combined, suggesting Cloudsmith itself is scaling its go-to-market operations while its customers focus on technical implementation.

The day-to-day users are predominantly infrastructure and platform engineers who manage artifact repositories, container registries, and package distribution. I noticed these practitioners work with multi-format artifact management spanning languages, containers, and operating systems. They're responsible for integrating Cloudsmith into development pipelines, managing dependencies, and ensuring secure software supply chains. One posting mentions needing to "design, deploy and configure.Net Applications" and manage artifact delivery, while another describes building platforms that enable developers to "securely and seamlessly publish their artifacts."

The core pain points revolve around scale, security, and developer productivity. Companies are trying to "tackle scale and complexity through best-in-class artifact management" and "secure software by default." I found revealing phrases like "accelerate CI/CD pipelines, reduce egress costs, and eliminate repository performance bottlenecks" and "protect and accelerate, no matter the scale." These organizations view artifact management as critical infrastructure that must handle Fortune 500 scale while reducing costs and friction in software delivery workflows.

Source: Analysis of Linkedin bios of 547 companies that use Cloudsmith

I analyzed these companies and found that Cloudsmith's typical customer operates in technically complex domains where software is either the core product or a critical enabler. These aren't just "tech companies" in the abstract sense. They're building semiconductor chips, developing AI platforms, creating financial technology, manufacturing medical devices, operating telecommunications networks, and producing enterprise software. What unites them is that they're all shipping sophisticated software or firmware, often embedded in hardware or deployed across distributed systems.

The company size and maturity varies dramatically. I see early-stage startups with seed funding and 20 employees sitting alongside Fortune 500 enterprises with 20,000+ staff and post-IPO financing. However, even the massive enterprises (Analog Devices, Equinor, Macy's) that use Cloudsmith likely do so within specific engineering teams rather than company-wide. The growth-stage companies in Series A through D funding seem particularly well-represented, suggesting Cloudsmith appeals to teams scaling their engineering operations.

Source: Analysis of tech stacks from 547 companies that use Cloudsmith

I noticed that Cloudsmith users are mature, security-conscious engineering organizations building containerized software with sophisticated access controls. The extremely high correlation with Docker Hub tells me these companies are heavily invested in container-based development and distribution. When I see this paired with enterprise identity tools like Okta and Okta Advanced Server Access showing up hundreds of times more frequently than normal, it's clear these are companies that need to manage complex permission structures across their engineering teams and external partners.

The pairing of Cloudsmith with Docker Hub makes perfect sense because companies distributing containers need a private package repository to complement their container registry. They're likely managing multiple artifact types across the software supply chain. The Okta correlation is particularly telling because it suggests these companies have significant compliance requirements or are selling to enterprises themselves, so they need robust identity management. Golinks appearing 409 times more often indicates large engineering teams that need internal tooling to stay organized. Panther's massive 2360x correlation, even with just 8 companies, points to serious security monitoring needs, which aligns with companies managing sensitive package distribution.

The full stack reveals these are sales-led, enterprise-focused companies in growth or mature stages. They're not early startups experimenting with tools. They've reached a scale where security, compliance, and developer productivity justify investments in specialized tooling. The Watershed presence suggests they're also large enough to care about ESG reporting, reinforcing that these are substantial organizations with formal operations.