Private has a boundary.
Inference and contribution are separate paths, with separate permissions and storage.
Built small.
Designed to grow.
A gateway should scale without losing sight of who owns a decision. Our blueprint starts with one clear authority, deliberate boundaries, and a complete path through failure.
Researched design · Integration and production validation are separate release gates.
Every effect has an owner.
Usage, money and consent resolve through an auditable authority, even when delivery repeats.
Recovery is part of the design.
Unknown outcomes stay visible. Retries, stale workers and partitions have explicit rules.
ONE ARCHITECTURE, SEVERAL PROFILESChange the placement.
Change the placement.
Keep the contract.
Explore the planned deployment profiles. These describe the engineering path; each becomes supported after its conformance tests pass.
A deliberate starting point
One VM
Colocate the process roles on a small VM. Prove the request, accounting and consent loop before adding operational complexity.
Pilot capacity is established through measured load and recovery tests.
DEPLOYMENT BLUEPRINT
COMPUTEAPI, gateway & workers
OPERATIONSExternal backups. Explicit limits.
CLEAR INTEGRATION BOUNDARIESChoose the foundation.
Choose the foundation.
Define the responsibility.
The platform’s integration choices are fixed. Production connections are enabled through the release gates documented in the specification.
Our own auth
A defined issuer contract, scoped access and current organization authorization.
Stripe
Hosted Checkout and verified payment events, with an independent allowance ledger.
Resend
Durable notification intents, deduplication and explicit delivery states.
PostgreSQL
Ordered writes, immutable accounting and a deliberate recovery procedure.
A FOCUSED FIRST RELEASE
Prove the complete loop.
An invite-only pilot brings developers, model suppliers and buyer design partners through a product they can inspect.
See the v1 release gatesConnect a client that passes conformance and make a Private request.
See the route, usage, allowance and settlement.
Review a contribution independently, with defined rights.
Inspect supplier conformance and an approved buyer sample.
Rehearse recovery before broadening the rollout.
300 invitees and a 32-stream baseline are planning targets, subject to real testing.HELP THAT KNOWS ITS BOUNDARY
A clearer way to get started.
Explore configuration previews and curated product answers in Setup studio. The website AI guide uses approved public information; the planned tenant setup and operator assistants have separate permissions and release gates.
Make the evidence visible.
The technical package connects decisions to contracts, failure cases and release gates. It distinguishes executable reference checks from the production validation still required.
Service & data boundaries
Threat model & control tests
API, events & consistency models
Deployment & recovery profiles