Security & Billing
Security model
How tenants are isolated, secrets protected, egress controlled, and access authenticated.
Enkeon Cloud's security rests on four pillars. Each has its own page.
Tenant isolationOne engine container, volume, and graph per project — isolation at the container boundary.
Secrets encryptionSealed boxes: the gateway can encrypt, only the provisioner can decrypt.
Egress allowlistDefault-deny outbound; the engine can only reach domains you permit.
Billing & plansPlans, quotas, metering, and invoices.
At a glance
- Two credential types, routed by prefix at the gateway:
tr_sk_…project keys (machines) and session JWTs (humans, scoped by org membership). See Authentication. - No engine is exposed to the internet — clients only ever reach the gateway, which authenticates and proxies to a loopback engine.
- Plaintext secrets never persist in the control plane and are never returned by the API.
For data locations and providers, read the subprocessor register. These controls are not a claim of independent security certification. For data locations and providers, read the subprocessor register. These controls are not a claim of independent security certification.