Dedicated VM. Hardware-level isolation. Per-customer keys.

01Why dedicated VMs.

Multi-tenant inference is cheaper to operate. That’s why almost every AI vendor uses it — one shared model, thousands of customers, brilliant unit economics. It’s also the reason their security pages dance around the question. When prompts cross customer boundaries inside the same model context, “your data” becomes fuzzy.

Aliens picked the harder model on purpose. One Cyborg · one VM · one customer. Worse for our gross margin; unambiguous for your data story.

02What runs on the VM.

• Cyborg runtime. Aliens-built process supervisor that orchestrates the role-specific Cyborg.
• Memory store. Customer-specific embeddings, document indexes, decision logs. Lives only on this VM.
• Working filesystem. Where the Cyborg checks out repos, downloads briefs, writes drafts.
• Audit emitter. Streams every Cyborg action to your customer-side log sink in real time.
• Out-bound proxy. All API calls the Cyborg makes go through a vetted egress proxy — logged + filterable.

03What does not run on the VM.

• Inference itself happens on a stateless GPU pool that retains nothing per request. The pool sees the prompt for milliseconds, returns the completion, drops the context.
• No shared model fine-tune state. Each customer’s preferences are encoded in their VM’s prompts/memory, not baked into a shared model.
• No Aliens-side analytics on customer content. We measure infra metrics (CPU, latency); we don’t aggregate prompts, outputs, or interactions across customers.

04Keys, on first boot.

When your VM is provisioned, it generates a unique 256-bit Key Encryption Key (KEK) inside its own vTPM-backed key store. That KEK never leaves the VM. Disk encryption Data Encryption Keys (DEKs) are wrapped under it.

Aliens engineers do not have this KEK. Even with full data-centre access, an Aliens engineer cannot decrypt your VM’s disk without first using the customer-side break-glass approval workflow (clause 07 of the contract) — which is fully logged and visible to you.

05What happens at termination.

On contract end: 7-day cooling-off period → structured export of your data (if requested) → KEK destruction → cryptographic wipe of the VM disk to NIST 800-88 Rev. 1 standards → certificate of destruction issued.

Backups age out within 12 months and are wiped at retention end. Audit logs and transaction records are retained per legal minimums (typically 7 years for India / EU / UK), but no Customer-confidential business content remains.

06FAQ.