Solutions
A self-hosted internal tools platform for AI-built apps
A self-hosted internal tools platform runs entirely inside infrastructure the company controls, including the console and API, not only the apps. Self-hosted Diakrin installs the whole platform in your own AWS account with the Diakrin CLI, so employees can build internal apps with AI coding agents while sign-in, builds, approvals, audit and app data stay inside your account and network.
Last reviewed
A self-hosted internal tools platform runs entirely inside infrastructure your company controls: the console, the API and the apps. Self-hosted Diakrin installs the whole platform in your own AWS account with the Diakrin CLI. Employees still build internal apps with Claude Code, Codex or OpenCode, and IT still approves access and releases, but nothing depends on a vendor-hosted console.
When do you need a self-hosted internal tools platform?
Most companies are well served by BYOC, where apps and their data run in your cloud and Diakrin runs the control plane. Self-hosted is for companies that need the console and API inside their own network as well, for example because policy does not allow a hosted control plane, or because the console must not be reachable from the internet.
| BYOC | Self-hosted | |
|---|---|---|
| Apps, builds, data and secrets | Your cloud account | Your cloud account |
| Console, API and MCP server | Run by Diakrin | Also in your cloud account |
| Clouds | AWS and Google Cloud today, Azure coming soon | AWS today |
| Sign-in | SSO through SAML, with optional SCIM | Local accounts or one company OIDC connection |
| Who operates the platform | Diakrin | Your team, with the Diakrin CLI |
See What is Diakrin.
What gets installed in your AWS account?
diakrin self-hosted infra up creates the infrastructure and diakrin self-hosted deploy puts Diakrin on it. Everything is tagged with your installation id.
| Part | What it is for |
|---|---|
| VPC | A private network across two Availability Zones, with a NAT gateway and VPC endpoints |
| Internal load balancer | The console, API and webhooks, with no public address |
| ECS on Fargate | The API, worker and console services |
| Amazon RDS PostgreSQL | The Diakrin database, encrypted and deletion-protected |
| Amazon ECR | Your own registry; signed images are copied in by digest |
| AWS KMS and Secrets Manager | Encryption keys and generated secrets |
| Audit bucket | Amazon S3 with Object Lock; retention cannot be shortened later |
| CloudFront and AWS WAF | The default public front door, which you can turn off |
How is a self-hosted installation kept secure?
- Signed releases. Every release is signed by Diakrin, and the CLI refuses anything it cannot verify.
- No vendor sign-in. Diakrin cannot sign in to your installation.
- Limited outbound traffic. Only GitHub, the signed image registry and Diakrin license checks.
- Private builds. Builds run on your company's own GitHub Actions runner, labelled
diakrin-customer, never on GitHub-hosted runners or Diakrin's hosted service. - Checks at the moment of change. Every build, deployment and publish is checked again when it would change your cloud. A refusal changes nothing and names the rule and the next step. See Review capabilities and deployment.
- Audit first. Apps cannot be created, and builds and deploys stay blocked, until IT configures the audit archive.
Can the platform stay completely private?
The console can stay off the public internet. With DIAKRIN_EXPOSE=none there is no CloudFront: people reach the console over VPN, VPC peering or PrivateLink, and GitHub reaches one webhook endpoint. Outbound traffic is limited to GitHub, the signed image registry and Diakrin license checks, and can go through your own firewall. You can also reuse an existing VPC, database, ECS cluster, certificates and DNS. See Self-hosted overview.
How it works with Diakrin
- Check the prerequisites. One AWS administrator, an AWS account and region, a host name you control, a GitHub organization admin and an audit retention period. See Self-hosted overview.
- Install the CLI and write the settings. Settings go in
diakrin.env; secrets never do. - Create the infrastructure. Run
diakrin self-hosted infra upwith--plan-onlyfirst, read the plan, then apply it. The CLI refuses a plan that deletes or replaces stateful resources unless a person allows it. - Add DNS and deploy. Add the printed DNS records, run
diakrin self-hosted deployand finish setup in the browser. See Install self-hosted Diakrin. - Approve spending limits and audit. The owner confirms deployment prerequisites, including the audit archive, scanner and organization spending limits.
- Builders connect their tools.
diakrin mcp configprints the connection for Claude Code or Codex, which sign in to your installation directly. See Connect your coding tool.
What is different from BYOC today?
Self-hosted apps use the installation's reviewed private ingress rather than the company sign-in gateway. The app data inventory shows Unavailable, because no data collector runs on self-hosted AWS yet. Day-to-day operation (status, health checks, upgrade, rollback and removal) is done with the CLI by your team.
If apps in your cloud are enough and the control plane can be hosted, read deploy internal apps in your AWS account.
Frequently asked questions
What is the difference between BYOC and self-hosted Diakrin?
With BYOC, apps, builds, data and secrets run in your cloud and Diakrin runs the console, API and MCP server. With self-hosted, the console, API and MCP server also run in your AWS account, and your team operates the platform with the Diakrin CLI.
Which clouds does self-hosted support?
AWS today. If you only need apps and data in your cloud, including on Google Cloud, BYOC is the better fit.
Can Diakrin sign in to our self-hosted installation?
No. Diakrin cannot sign in to your installation. Outbound traffic goes only to GitHub, the signed image registry and Diakrin license checks.
Can the console stay off the public internet?
Yes. With the setting DIAKRIN_EXPOSE=none there is no CloudFront, and people reach the console over VPN, VPC peering or PrivateLink. The load balancer is always internal.
How do people sign in on a self-hosted installation?
With local accounts on the installation or one company OIDC connection. Owners and admins who sign in with a password also use an authenticator app.
Can we reuse our existing VPC and database?
Yes. You can bring an existing VPC and subnets, security groups, ECS cluster, load balancer listener, certificates, KMS key, ECR registry, audit bucket, PostgreSQL database and DNS zone.
Can a coding agent run the install?
Yes. Claude Code, Codex or Cursor can run the install from the install guide. A person still reads and approves the plan, confirms DNS records and enters the owner setup code in the browser.
See Diakrin with your own cloud
Let your team build internal apps with the AI tools they already use, while IT keeps control of identity, data, approvals and spend.