From per-image to org-wide pricing

This pricing change turns Chainguard from a niche security purchase into infrastructure that an entire engineering org can standardize on. Per image pricing makes every new workload feel like another budget request. Org wide access flips that dynamic. Once a company buys the catalog, teams can swap in hardened images for Python, Node, Redis, and other building blocks without reworking contracts each time, which is exactly how broad internal rollouts happen.1 2

• The earlier model looked more like high priced security tooling, with enterprises paying about $20K to $30K per image per year. That works for a few mission critical containers, but it discourages a platform team from replacing hundreds of images across many apps.2
• Catalog pricing aligns with how container risk actually spreads. A large company does not run one image, it runs fleets of base images and packages reused across many services. Unlimited access to 1,400 plus images and 10,000 plus packages lets Chainguard sell a standard, not a SKU list.1 2
• This also sharpens the wedge against scanners like Wiz and Snyk, and against Docker's hardened images. Chainguard is not charging mainly to find problems after developers build containers. It is charging to be the default source those developers pull from in the first place.2 3

The likely end state is that secure images get bought more like a company wide developer platform and less like a point security product. That favors vendors that own the base layer, bundle many images and packages together, and can keep expanding from containers into libraries, VMs, and compliance heavy enterprise workflows.1 2 3