About
We got tired of maintaininggolden images by hand
ProvenCloud exists because base image maintenance is the least glamorous, most consequential work in a platform team — and almost nobody has time to do it properly.
The short version
Our founding team spent years running platform and security engineering inside regulated companies — fintech, health data, a stint in public sector infrastructure. In every one of them, the same thing was true: a small number of base images underpinned everything in production, and maintaining them fell to whoever had least recently said no.
It usually worked until it didn't. An auditor asks which version of a library is on the fleet, and the honest answer takes three days to assemble. A critical CVE lands on a Friday, and someone rebuilds an image by hand at 11pm from a Packer template nobody has read since the person who wrote it left.
We built the thing we kept wishing we could buy: a catalog of clean-room images with real documentation, a full software inventory, no credentials baked in, and a patch cadence you can put on a roadmap. No control plane to adopt, no agent to install. Just an AMI ID and the paperwork to defend it.
We're deliberately small, and we publish what we run ourselves. Customer demand decides which images come next — tell us what you need and it goes on the list.
Our mission
Make a secure, auditable base image the cheapest option a team has — so that doing the right thing stops competing with shipping.
How we got here
- 2019
Founding team meets running platform security at a regulated fintech.
- 2023
Third audit in a row derailed by undocumented base images.
- 2025
First internal image pipeline built, every build documented from day one.
- 2026
ProvenCloud opens its AWS and Azure catalog ahead of marketplace launch.
Principles
How we decide what ships
These are the rules we argue about internally, written down so you can hold us to them.
- 01
Document everything, assume nothing
If we can't explain why a package is on an image, it doesn't ship. Every build has a manifest a reviewer can read in an afternoon.
- 02
Boring beats clever
No agents, no sidecars, no proprietary runtime. An AMI ID you can drop into the launch template you already have.
- 03
Patch on a schedule you can plan around
Predictability matters more than speed. You should know when the next revision lands before you need it.
- 04
Own the exceptions
Every hardening control we could not apply is listed, with the reason. Silence in a compliance document is a liability.