SaaS
Minimus
Minimus, the hardened minimal container image provider, is ending operations: its registry (reg.mini.dev) is turned off on 22 October 2026 after a 60-day maintenance period, and no further updated images will be published
departs 22 Oct 2026
Quick answers
- Is it true that Minimus shuts down its hardened container image registry?
- Yes. Minimus has officially announced it, effective 22 Oct 2026. Minimus sells hardened, minimal container images — stripped-down, near-zero-CVE drop-in replacements for standard base and application images (a competitor to Chainguard Images and Docker Hardened Images) — pulled from its registry at reg.mini.dev.
- When does it take effect?
- 22 Oct 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Treat this as a base-image migration with a hard security deadline: after 22 October 2026 your Minimus images are frozen and will accumulate unpatched CVEs.
What this means for you
Minimus sells hardened, minimal container images — stripped-down, near-zero-CVE drop-in replacements for standard base and application images (a competitor to Chainguard Images and Docker Hardened Images) — pulled from its registry at reg.mini.dev. In an official notice on minimus.io, the founders say the current business and investment climate has left the company unable to continue operations. The wind-down has two dates that matter to anyone pulling these images in their builds. Beginning Monday 24 August 2026 Minimus enters a 60-day maintenance period: it keeps making bug fixes, provides commercial support, and continues maintaining images with upstream updates. On Thursday 22 October 2026 it ceases operations and turns off the registry. Images already pulled before 22 October keep working, but no new or updated (patched) images are published after that, so anything you pin to reg.mini.dev stops receiving the security updates that were the entire reason to use a hardened image. Enterprise Edition customers will be contacted individually starting 24 August about structured termination of their agreements, including refunds for the remaining contract period beyond 22 October.
Where to go
Treat this as a base-image migration with a hard security deadline: after 22 October 2026 your Minimus images are frozen and will accumulate unpatched CVEs. Inventory every Dockerfile, compose file, and build pipeline that pulls from reg.mini.dev, then repoint each to another hardened/minimal image source and rebuild and test before the cutoff. The closest like-for-like replacements are Chainguard Images and Docker Hardened Images; Google's distroless images cover many runtime bases for free. If you would rather not depend on a single vendor again, you can build your own minimal images from Wolfi/apko or from official -slim / distroless bases. Whatever you choose, re-verify that your application still builds and runs on the new base (users, shells, package managers and CA certs often differ between hardened images) and update any image-scanning baselines. Enterprise customers should also confirm refund and support terms in the individual outreach Minimus says begins 24 August.
- Chainguard Images — hardened, low-CVE container images (chainguard.dev)
- Docker Hardened Images (DHI) — Docker's hardened, minimal image line
- Google distroless base images (github.com/GoogleContainerTools/distroless) — free, minimal runtime bases
- Build your own minimal images from Wolfi/apko, or from official -slim / distroless bases
Minimus, a provider of hardened, minimal container images, is shutting down. In an official notice on minimus.io, the founders write that “the current business and investment climate has resulted in a situation in which we are unable to continue operations.” The Minimus registry (reg.mini.dev) is turned off on 22 October 2026.
What Minimus does is what makes this a dated migration rather than a curiosity. It sells stripped-down, near-zero-CVE base and application images — drop-in replacements for standard Docker Hub or distro images, in the same category as Chainguard Images and Docker Hardened Images. If your builds pull from reg.mini.dev, you are depending on Minimus to keep those images patched against new vulnerabilities.
There are two dates. Beginning Monday 24 August 2026, Minimus enters a 60-day maintenance period: it will keep making bug fixes, provide commercial support, and continue maintaining images with upstream updates. On Thursday 22 October 2026, it ceases operations and turns off the registry. Images you already pulled before that date “will, of course, continue to function, but no further updated images will be provided” — so anything pinned to reg.mini.dev stops receiving the security updates that were the whole point of a hardened image.
For Enterprise Edition customers, Minimus says it will reach out individually starting 24 August to discuss a structured termination of the agreement, including “any applicable refunds for the remaining contract period beyond 22 October.”
The migration is a base-image swap with a security deadline attached. Inventory every Dockerfile, compose file, and CI pipeline that references reg.mini.dev, then repoint each to another hardened or minimal source and rebuild before the cutoff. The nearest equivalents are Chainguard Images and Docker Hardened Images; Google’s distroless images are a free option for many runtime bases; and if you would rather not re-bet on one vendor, you can build your own minimal images from Wolfi/apko or from official -slim/distroless bases. Budget time to re-test — hardened images differ in their users, shells, package managers, and bundled CA certificates, so a swap is rarely zero-effort — and refresh any vulnerability-scan baselines once you have moved.
Entry changelog
- — last reviewed.
- — Entry created from Minimus's official wind-down notice on minimus.io (banner + full modal notice, signed by founders Ben, Dima, and John). Dates quoted directly from that notice: 60-day maintenance period begins Monday 24 August 2026; registry (reg.mini.dev) ceases operations Thursday 22 October 2026 — the latter is the sunset date. Surfaced via an HN discussion (item 49409301) that linked only to a screenshot; verified against the vendor's own site before publishing. No detect: fingerprint — Minimus images are pulled as reg.mini.dev/<name>:<tag> where the image name varies, which the CLI's name:tag image matcher cannot cover with a single generic token.
Put this countdown in your README
Building on Minimus? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/minimus-shutdown)Spot an error or a changed date? Tell us and it’s corrected the same night.