# What is Diakrin

> A governed way to build company apps with AI coding agents and run them in your own cloud (BYOC).

Source: https://diakrin.com/docs/

Diakrin lets people across your company build internal apps with AI coding agents and run them in your own cloud (BYOC, bring your own cloud), while IT stays in control of who builds, what each app can reach and what it costs.

Business teams describe the app they need and build it with the coding tool they already use, such as Claude Code, Cursor or Codex. Diakrin handles the work that turns a prototype into a real company app: sign-in, access, source, builds, checks, approvals, deployment, budgets and audit.

```cards
Get started | /docs/get-started | The onboarding checklist for IT, identity and builders. | rocket
How it works | /docs/how-it-works | The path from an idea to a governed production app. | flow
Connect your coding tool | /docs/builders | Claude Code, Cursor, Codex and other MCP tools. | terminal
Set up your company cloud | /docs/company-cloud | AWS and Google Cloud today, with Azure coming soon. | cloud
Connect your company SSO | /docs/sso | Okta, Entra ID, Google Workspace or any SAML provider. | key
Manage access and security | /docs/security | Identity, roles, app access and what happens to app data. | shield
```

```diagram platform-map
Diakrin coordinates and your cloud executes. Builds, app data, secrets and credentials stay in your account; Diakrin receives metadata and evidence, not business data.
```

## What Diakrin does

### Runs AI-built apps in your cloud

Each app gets its own service, database, file storage and secrets inside a company cloud setup that IT creates from a reviewed template. Apps are built, checked and run in your account, next to the data they are allowed to use. See [what each cloud provides today](/docs/company-cloud#what-each-cloud-provides-today).

### Puts IT in the approval path

Every capability an app requests, every data source it reads and every production release goes through company policy and, where your policy requires it, an independent reviewer. Budgets are enforced before a deployment is admitted.

### Gives employees one sign-in

Employees open company apps with your existing company sign-in. Diakrin brokers the sign-in and checks membership and each app's audience, so IT does not register every app with the identity provider. On Google Cloud, apps stay on your private network behind Identity-Aware Proxy, which admits only each app's audience.

## Choose how you run it

| | 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; ask us about other clouds |
| **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 |
| **Start with** | [Get started](/docs/get-started) | [Self-hosted overview](/docs/self-hosted/overview) |

Most companies start with BYOC. Pages and notes marked **Self-hosted** apply only to a self-hosted installation.

## Who uses Diakrin

| Who | What they do | Start with |
| --- | --- | --- |
| Builder | Describes an app and builds it with a coding agent, within approved access | [Create your first app](/docs/first-project) |
| IT administrator | Invites people, sets budgets and policy, reviews access and releases | [Get started](/docs/get-started) |
| Identity administrator | Connects company SSO and automatic provisioning | [Connect your company SSO](/docs/sso) |
| Technical administrator or cloud administrator | Connects the cloud account and verifies the infrastructure | [Set up your company cloud](/docs/company-cloud) |
| Coding agent | Works through MCP or the CLI with the builder's own permissions | [Connect your coding tool](/docs/builders) |
| Employee | Signs in and uses the apps they have been given | [Sign in to company apps](/docs/app-signin) |

## What you bring, what Diakrin provides

| You bring | Diakrin provides |
| --- | --- |
| An identity provider that supports SAML 2.0, such as Okta, Entra ID or Google Workspace | The console, an app sign-in broker and role-based access |
| Your cloud account: AWS or Google Cloud today, with Azure coming soon | Reviewed infrastructure templates and a runner that builds and deploys inside your account |
| The coding tools your builders already use | An MCP server, a CLI and guided briefs that keep agents inside approved access |
| The company systems your apps need to read | Access requests that IT approves as named, scoped grants |
| Your rules: who may build, who approves, what apps may cost | Approval workflows, budgets, cost estimates, a data inventory and an audit trail |

## Questions people ask first

### Is this vibe coding in production?

No. A saved idea, a build, a preview and a live deployment are separate states, and each one needs its own evidence. Builds run and are checked in your cloud, production releases need an approved plan, and the console does not show an app as live without fresh, server-verified evidence.

### Does our data leave our cloud?

App databases, files, secrets, builds and execution stay in your account. Diakrin stores metadata such as app definitions, policies, approvals and cost accounting. Its data view reports sizes and names, never row values, file contents or secret values. See [Your apps' data](/docs/security#your-apps-data).

### What stops an agent from doing too much?

The agent acts as the person who connected it. Every call is checked against that person's current role and app access, so it can never do more than they can. Asking for a capability is not the same as being granted it.

### Do we lose control of what gets built?

IT decides who can create apps, which data each one may read, who can open it and what it may cost. Removing a person from Diakrin ends their app access and their coding-tool tokens.

## Next steps

- [How it works](/docs/how-it-works): the path from an idea to production, step by step.
- [Key concepts](/docs/concepts): the words used across the console.
- [Get started](/docs/get-started): the onboarding checklist for your company.
