Runs where your data already is.
Deploy Alexein single-tenant in your own cloud, on your own model keys. Twins, graph, and memory — all inside your security boundary.
Paste to your agentRun in terminal
Install Alexein in your own cloud: in the terminal, run
See it in action ↓npx alexein deploy with the flag for your cloud — --aws, --gcp, or --azure — plus --byok for your model keys. It provisions the single-tenant graph, wires your keys, and turns the audit log on. Nothing leaves your boundary.See it in action
One command. Your whole boundary.
Pick a stage. Watch the deploy run end-to-end — in your account, on your keys.
ProvisionConnectEnrollGovern
Provision the tenancyVPC, private subnets, and the org graph — created in your cloud account, owned by you.
Connect the sourcesGitHub, Slack, Jira, Drive — least-privilege, read-only connectors.
Enroll the twinsOne twin per employee, built from their real commits, reviews, and decisions.
Govern the graphAutonomy earned task by task. Write access scoped team ← personal.
$ alexein deploy --byok --aws
✓ vpc single-tenant · private subnets
✓ graph provisioned — personal · team · dept · org
✓ model keys yours — bedrock / anthropic
✓ audit on — who · what · when · based-on
● twins enrolling 42 employees…
✓ vpc single-tenant · private subnets
✓ graph provisioned — personal · team · dept · org
✓ model keys yours — bedrock / anthropic
✓ audit on — who · what · when · based-on
● twins enrolling 42 employees…
◆ Single-tenant◆ Your model keys◆ Audit on everything◆ Guardrails between graphs
SOC 2-friendly posture · SSO / SAML · least-privilege connectors