Start here

What is Diakrin

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

Deployment
BYOC and self-hosted

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.

Where Diakrin sitsBuilders work through a coding agent and IT works in the console; both reach the Diakrin control plane. Below the customer boundary, a Diakrin runner in your cloud account (AWS or Google Cloud today, Azure coming soon) builds and deploys each app with its own database, files and secrets. Diakrin sends scoped requests down and receives metadata only. Employees sign in through your identity provider to reach the apps.Buildersdescribe the appCoding agentIT & adminsapprove, governConsoleweb appDIAKRIN CONTROL PLANE · HOSTED BY DIAKRINApps & policywhat each app may doReviews & approvalswho said yes, whenAudit, cost & dataone place for ITApp sign-in brokerno per-app IdP setupCUSTOMER BOUNDARYBelow the line: your data, code,builds and credentials.scoped requestsmetadata onlyYOUR CLOUD ACCOUNTSOONDiakrin runnerbuilds · checks · deploys · reportsFinance appDB · files · secretsOps appDB · files · secretsApproved company dataEmployeesuse the appsCompany SSOOkta · Entra · Google
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.

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

BYOCSelf-hosted
Apps, builds, data and secretsYour cloud accountYour cloud account
Console, API and MCP serverRun by DiakrinAlso in your cloud account
CloudsAWS and Google Cloud today, Azure coming soonAWS today; ask us about other clouds
Sign-inSSO through SAML, with optional SCIMLocal accounts or one company OIDC connection
Who operates the platformDiakrinYour team, with the Diakrin CLI
Start withGet startedSelf-hosted overview

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

Who uses Diakrin

WhoWhat they doStart with
BuilderDescribes an app and builds it with a coding agent, within approved accessCreate your first app
IT administratorInvites people, sets budgets and policy, reviews access and releasesGet started
Identity administratorConnects company SSO and automatic provisioningConnect your company SSO
Technical administrator or cloud administratorConnects the cloud account and verifies the infrastructureSet up your company cloud
Coding agentWorks through MCP or the CLI with the builder's own permissionsConnect your coding tool
EmployeeSigns in and uses the apps they have been givenSign in to company apps

What you bring, what Diakrin provides

You bringDiakrin provides
An identity provider that supports SAML 2.0, such as Okta, Entra ID or Google WorkspaceThe console, an app sign-in broker and role-based access
Your cloud account: AWS or Google Cloud today, with Azure coming soonReviewed infrastructure templates and a runner that builds and deploys inside your account
The coding tools your builders already useAn MCP server, a CLI and guided briefs that keep agents inside approved access
The company systems your apps need to readAccess requests that IT approves as named, scoped grants
Your rules: who may build, who approves, what apps may costApproval 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.

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

Next stepHow it works →