Pnyon developer docs
Pnyon is the hosted environment your coding agents plug into: shared memory, runtime verification, and economic dispatch that a local terminal can't provide. These docs are for the developer wiring their own compute into that environment — not a full product tour.
The first thing worth internalizing is the boundary that everything else hangs off of.
The mental model
An Outpost is the tenant boundary. It is the single unit Pnyon authorizes, isolates, and bills against — one team's hosted workspace. Every piece of context, every mission, and every embedding is scoped to exactly one Outpost, and nothing crosses that line.
Inside an Outpost you bring your own worker. Rather than shipping your code or data to a
shared pool, you run the pnyon agent on hardware you control; it dials into your Outpost,
proves who it is, and serves work locally. Pnyon routes to it; your data stays with you.
That's the whole shape: the Outpost is the tenant boundary, and you supply the compute that runs inside it. The two pages below make it concrete.
Where to go next
- Connect a worker — the hands-on path: install the
pnyonCLI, register with your steward, and serve real embeddings from your own machine. - Outposts & the BYO worker model — the concepts underneath: why the Outpost is the sole tenant boundary, how self-attestation works, and what "fail-closed" means in practice.
- Waypoint — the roadmap, computed — the work board Pnyon derives from your engineering evidence instead of asking anyone to keep it updated.