What it does
A mirror, a forge, and a build fleet — in one service
Each of these has a page of its own: what it actually does, how it works, and what it costs you to have it. Nothing on this page is a plan — every one of them runs today.
Mirror what you depend on
Every ecosystem your builds pull from, cached on hardware you own and still answering when upstream is not.
Drop-in proxy
One config line. Every artifact it fetches is kept, and served locally next time.
A catalog you can query
What you have, what a release depended on, and when each artifact was last pulled.
Prefetch before you go dark
Warm the cache while you still have a network, as a background job you can poll.
Retention and GC
Reclaim space by age and last use, with pins and OS images protected automatically.
Boot a machine from your mirror
Mirror OS images like packages, then install a bare machine with every byte from you.
Know what you actually have
A copy is only worth keeping if you can say what it is — checked against what upstream published before it is stored, and provable again years later.
Pull audit
Who changed the mirror, and what this build actually pulled from it.
Verified against what upstream published
Checked against the digest upstream published, and refused before it is stored.
Snapshots you can replay
Freeze what the mirror holds under a name, and verify later that nothing moved.
Locked down by default
Anonymous to read, token-gated to change, and it refuses to start up unsafe.
Host it, build it, ship it
The repositories, the machines that build them, the gate production is reached through, and the clients you drive all of it from.
A build service that uses the mirrors
Build your code against your own mirror. Runners poll out, so no inbound ports.
Self-hosted git forge
Host your repos beside the mirrors, and let a push trigger the build that deploys it.
Production is reached by promotion
Production is where work arrives by having passed staging — not a host you deploy to.
What your fleet is, beside what it says it is
What your machines actually are, beside what your document says they are.
Clients for how you actually work
A CLI, a dashboard, and an Android/iOS app that watches builds and mirror health.