FerroBox

Brand lore, not a feature list

The Anvil

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.

The pipeline

Roughly the order an artifact goes through, start to finish.

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.

Keeping the smithy running

Not a single step — ongoing concerns that apply the whole time.

Ledger

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.

Why iron

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.