Built by itself, with receipts
What the product's own record shows about how it was built.
The strongest fact about Saphan Studio is how it exists: it has been built by its own fleet, in production, from the first weeks — orders, gates, dispatches, reviews, merges, costs, refusals, all in its own record. This is not a demo assembled for a launch; it is a month of production history that happens to be the product's own ledger.
What that record shows, with the discipline that no number leaves the building without its reference: multi-machine fleet operation (a macOS control plane, VMs, an Android device, a GPU box running local models); double-digit merges landed in a single day with exactly one hard conflict — the bottleneck was vendor rate limits, not correctness; a measured corpus of over a hundred agent sessions and five figures of assistant messages; deterministic actors doing real verification work at cost zero; and a defect ledger in which the fleet's own failures become named classes with structural cures — the corrective-action chains an auditor recognizes on sight.
Security, enterprise and cost, in brief
The three summaries, each pointing at the section that carries the detail.
What "shipped" means on this site
The word is used in one sense here, and this page is that sense: present tense means shipped and exercised, and a control that ships opt-in is never described as on.