Your models, your hardware, your audit trail.

If your data cannot leave your network, on premises. If most of it cannot but some work is worth sending out, hybrid. If none of that applies and you want a key today, Cloud. The modes are one spectrum rather than three products, and moving along it later is a licence change, not a migration.

The orchestrator, the router, and the console, as containers you run in your own environment: your servers, your cloud account, or an air gapped rack. There is no call home required for it to serve traffic, and no component of it we operate.

Yes. The heartbeat that reports version and licence state carries metadata only, and it can be switched off; releases and model weights are then delivered as artefacts you bring in yourself. Nothing about a request is in that channel whether it is on or off.

Policy you write, evaluated before inference rather than after. Rules read on the class of work, the data label carried with the request, the destination, and the spend ceiling for the period. A request that no rule admits is answered inside your estate or refused. It is never quietly sent out.

Only the base URL. All three modes are drop in compatible with the OpenAI API, so the official SDKs work unchanged. The extra ModelBeat returns (which model ran, on which provider, whether a fallback fired, what it cost) rides in the response alongside the fields you already read.

Yes, and in either direction. The engine is the same binary in all three; what differs is where it runs and what policy permits. Cloud to hybrid is an install, hybrid to on premises is a policy change, and your audit history comes with you.

No, in any mode, and there is no setting that turns it on. In the licensed modes the question is largely moot. The traffic never reaches us.

Every privileged change on the tenant: who acted, on which key, and whether it went through. It is append only, and in the licensed modes it is written to your storage rather than ours.

Certification is in progress and we do not claim what we do not yet hold. What we can put in front of you today is the architecture, the audit trail, and a deployment mode where the data never leaves your control, which is usually the question the certificate is being asked to answer.

Provider keys stay where they are issued; in the licensed modes we never see them. Keys you issue through ModelBeat are virtual, scoped, and capped by request and token count, and revoking one takes effect on the next request rather than the next billing period.