docs · the source of truth
The kit documents itself.
Every page here is a file in the repository, rendered at build time. When the code changes, the page changes with it — there is no second copy to drift.
the kit
What rents the box, checks the fit, and serves the model.
package
The launch kit
The consumer front door: what you need, the seven-stage story, the quick start, and every configuration knob the kit reads.
launch-kit contract
The launch kit’s function contract
Every must and must-not the snipe enforces — the fit gate, the vanish walk, the pin rule, the watch band, the price lock, the offline suite.
catalog
The catalog
What the knowledge base is, which three files carry it, and the rule that a performance number is only ever a capture.
gateway
One endpoint over every cell
The gateway cell: one OpenAI-compatible door in front of every live worker, reconciled against the fleet on a tick — never restarted for a membership change.
the tunnel
What reaches it afterwards, and what the reaching costs.
the platform
How this site and its environments are built, served, and kept honest.
platform
The platform map
The planes, the hostnames, the ports, the environment rule and the vendoring rule — this site included.
environments
Why /api is relative
One build artifact serves every environment: nginx resolves the address from the Host header, so no page carries an API constant.
storage
Events belong here, gauges do not
Why the events plane stores facts and lifecycle rows and never a metric path — Postgres for accounts, ClickHouse for events, the hcapi snapshot for gauges, nothing duplicated.
Read the catalog before you rent.
The catalog is the part that saves the money, and it is readable without running anything. Three files, and the CLI that reads them.
| file | owns | a question it answers |
|---|---|---|
models.yaml | checkpoints, quants, drafts, engine pins, minimum TP per class, traps | which engine and flags does this model need, and where does it fail? |
hardware.yaml | instance classes, card counts, VRAM, floors, observed price bands | what does this class cost, and what does it demand of a host? |
performance.yaml | measured cells only — a null field is a bench owed | what did this exact shape actually do, and where is the capture? |
The CLI reads all three: onefrontier catalog models, catalog hardware, fit, best, perf, advise. Its manual is the command's own --help, and it is the flag home. See the catalog's own page.
Three ways to read this site, depending on what you need.
You want a model serving today
Read the launch kit, run the dry run, then the snipe. Rehearsal costs nothing and needs no key.
You want to know what fits what
Read the models. Each page carries the weights per card, the engine pin, and the trap that page exists to record.
You want someone else watching
Read pricing. One flat number per cell, no share of savings, and the kit stays free either way.