In-region data
The tenant’s region is fixed when its workspace is created. Code, evidence and inference stay in it; only receipt hashes leave.
AEGIS keeps code, evidence and inference in the customer’s region, isolates every tenancy, and enforces governance in deterministic code outside the models.
Deployment
Choose where it runs.
| Option | What runs where | Availability |
|---|---|---|
| Hosted | Forge Studio, Conductor and Stele in a NeuroFabric-operated Helix tenancy; models on NeuroFabric GPUs with Reflex | UAE region |
| Sovereign tenancy | A dedicated tenancy with in-region inference | UAE; EU-resident tenancy by arrangement |
| Customer-hosted models | AEGIS Models on your own GPUs with Dynamis and encrypted weights, without Reflex | By licence |
Forge Studio, Conductor and Stele are offered as a cloud service. Talk to us if your policy requires on-premise delivery.
Controls
What stays inside the line.
Isolated tenancies
One Helix tenancy per customer, with per-tenant keys and agent identities scoped to the tenancy.
No third-party models
Agents call AEGIS Models only, through Dynamis. Prompts and code are not sent to an outside model provider.
Code off the endpoint
Forge Studio edits code in remote workspaces by default, so source does not sit on laptops.
Encrypted weights
AEGIS Model weights are encrypted and released only to machines that pass attestation.
Deterministic governance
Gates are evaluated by code, not by a model. Every decision leaves a signed receipt.
Posture
Evidence before claims.
We describe what AEGIS is built to do and link to evidence where it exists. We do not claim a certification until it has been awarded.
To report a security issue, use the contact form and choose “Security report”. Please do not include exploit details until we reply with a secure channel.
Talk to us about your deployment.
Tell us what you need to build and where it must run. A member of the team replies within two business days.