Ore
Raw material
Code and packages before any of this touches them — the raw material everything below is built from.
In FerroBox: Not a FerroBox feature. Just what an artifact is before it's pushed.
Brand lore, not a feature list
The Lore of Iron & Code
A Rust server, built the way iron is: heated, tested, and hardened before anything sharp is trusted to it. Here's the vocabulary FerroBox uses for that — and the real feature each term maps to.
Roughly the order an artifact goes through, start to finish.
Raw material
Code and packages before any of this touches them — the raw material everything below is built from.
In FerroBox: Not a FerroBox feature. Just what an artifact is before it's pushed.
Host it yourself
A repository you own. Push to it, and it's shaped and stored here, under your own roof.
In FerroBox: A Forge repository — one you host and push directly to.
Cache the outside world
A cache standing between you and an upstream registry, so an outage somewhere else doesn't become your outage.
In FerroBox: A Mirror repository — a pull-through cache in front of an upstream source (crates.io, npmjs.org, and so on).
Several sources, one endpoint
Multiple sources melted into one — several Forge and Mirror repos served from a single address.
In FerroBox: An Alloy repository — a virtual repo that aggregates several others behind one URL.
Test the purity
The test every artifact undergoes on arrival. Fail it, and it doesn't get used.
Harden the shape
Quenched and hardened until the shape is final — signed, so its origin can't be quietly swapped out later.
In FerroBox: Cosign checks on OCI and Helm artifacts. The vulnerability index is signed with a different public key.
Not a single step — ongoing concerns that apply the whole time.
Clear the waste
What's left over once the useful metal is taken. Cleared out so the forge doesn't fill up with scrap.
In FerroBox: Garbage collection, storage quotas, and retention rules.
One template, no exceptions
The strict template every piece has to fit. No exceptions, no pieces that are “close enough.”
Guard the door
The walls and the guards. Decides who's allowed anywhere near the hot metal in the first place.
In FerroBox: SSO (OIDC), RBAC, and scoped robot tokens for CI.
Write it down
The indelible mark in the smith's own book: every piece that came in, went out, or got melted down.
In FerroBox: The audit trail and webhooks.
Iron doesn't get strong by accident. It's dug up rough, purified under heat, folded until the impurities work themselves out, then quenched until the shape holds for good. That's not a metaphor we picked because it sounded nice — it's roughly the order of operations above: test it (Assay), shape it (Forge, Mirror, Alloy), harden it (Temper), guard it (Bastion), and keep a record of all of it (Ledger).
We wrote FerroBox in Rust for a similar reason smiths reach for iron instead of something softer: it costs more up front to get right, and then it doesn't bend the first time something leans on it.
That's the vocabulary. For what it actually does, see the Concepts page, or head back to GitHub.