What it sells
Automated software vulnerability patching.
Business model breakdown
Buyer: who owns the budget?
UnverifiedSecurity / platform engineering teams shipping container images.
Trigger: what makes them buy now?
Container images with CVEs that have no upstream fix (won't-fix, end-of-life packages) blocking releases or audits.
Workflow: what inputs become what output?
Customer submits a Dockerfile; agents patch every CVE (backport or craft fixes), validate against a working exploit and compatibility tests, then return a rebuilt image with SBOM, Cosign signature and SLSA provenance.
Economics: what it saves and how it charges
Claims 0 CVEs per release, ~24 hours from disclosure to patch, ~30% engineering hours saved per week, first clean image in 48 hours.
Distribution: how it reaches customers
Contact-form-led: start with one Dockerfile and the team reaches out within a business day.
Funding history and coverage
| Round date | Stage | Amount | Investors | Source |
|---|---|---|---|---|
| 2026-06-04 | — | $2.1M | — | news.google.com |
Profiles summarize public reporting and company websites. Business-model notes are MaxBC's reading of that material, not confirmed facts; unknowns are left blank rather than guessed. Updated 2026-10-12.