Self-hosted (AWS)
Self-hosted overview
What Diakrin installs in your AWS account, how it fits together and which guide to follow.
Self-hosted runs the whole Diakrin platform inside your own AWS account, installed by one person with the Diakrin CLI in about an hour. It is for companies that need the console and API inside their network too. If you only need apps and data in your cloud, including on Google Cloud, use BYOC.
What you install
diakrin self-hosted infra up creates the infrastructure below, and diakrin self-hosted deploy puts Diakrin on it. Everything is tagged with your installation id, and destroy removes it again.
| Part | What it is for |
|---|---|
| VPC | A private network with two Availability Zones, a NAT gateway and VPC endpoints for AWS services |
| Internal ALB | The load balancer for the console, API and webhooks. It has no public address |
| ECS Fargate | Runs the api, worker and console services and one-off tasks such as migrations |
| RDS PostgreSQL | The Diakrin database, encrypted, with deletion protection and a final snapshot on destroy |
| ECR | Your own image registry. deploy copies the signed images in by digest |
| KMS and Secrets Manager | Encryption keys and generated secrets. Nothing secret is written to a file |
| ACM certificates | HTTPS for the load balancer and for CloudFront |
| Audit bucket | S3 with Object Lock. Retention is your choice and cannot be shortened later |
| CloudFront and WAF | The public front door by default: a VPC origin to the internal ALB, protected by AWS WAF |
How it fits together
people and GitHub
│ https://<host>
▼
CloudFront + AWS WAF (DIAKRIN_EXPOSE=cloudfront, the default)
│ VPC origin
▼
internal ALB ──► ECS Fargate: console · api · worker
│
├──► RDS PostgreSQL
├──► Secrets Manager · KMS
└──► audit bucket (Object Lock)- Every release is signed by Diakrin. The CLI refuses anything it cannot verify.
- Diakrin cannot sign in to your installation. Outbound traffic goes only to GitHub, the signed image registry and Diakrin license checks.
- With
DIAKRIN_EXPOSE=nonethere is no CloudFront. People reach the console over VPN, peering or PrivateLink. See Existing infrastructure and exposure.
Choose your path
New installationCreate the infrastructure and deploy Diakrin with the CLI.Check the requirementsWhat you need before the first command.Reuse your own VPC or databaseBring an existing VPC, database, cluster, certificate or DNS.Add your license fileOptional at install, and can be added after deploy.Run it day to dayStatus, doctor, upgrade, rollback and destroy.Use a coding agentLet Claude Code, Codex or Cursor run the install.
Next
Check the prerequisites, then follow the install steps.