Start here

Key concepts

The building blocks you will see across the console, CLI and coding tools.

Deployment
BYOC and self-hosted

These are the building blocks you will meet in the console, the CLI and your coding tool. Knowing them makes every other guide quicker to read.

How Diakrin's main objects relateAn organization contains people with roles, optional projects that group apps, and company cloud setups. Each app has requirements, capabilities and grants, an audience, environments, releases and a budget. People are assigned to apps, and apps deploy to a company cloud setup.ORGANIZATION · YOUR COMPANY'S TENANTPEOPLERolesOwner · AdminBuilderTechnical admin · MemberIDENTITYCompany sign-inSSO (SAML)SCIM provisioningDirectory groupsPROJECT · OPTIONAL GROUPINGAPPRequirements & briefCapabilities → grantsAudience (who can open it)Releases & deploymentsMonthly budgetCOMPANY CLOUD SETUPYour cloud accountTemplate + regionNetworkBudget ceilingTechnical owner
An organization holds people, optional projects, apps and company cloud setups. People are assigned to apps, and apps run on a setup.

Structure

TermWhat it means
OrganizationYour company's tenant in Diakrin. Members, apps, setups and policies belong to one organization, and nothing crosses between organizations.
AppThe unit of work: one internal application with its requirements, audience, budget, releases and deployments. Each app has a stable app ID.
ProjectAn optional group of apps that share permissions, budget and policy. Grouping never grants extra access.
Company cloud setupA connected cloud account (an AWS account or Google Cloud project today) plus the shared infrastructure created from a reviewed template. Apps deploy into a setup.
TemplateA reviewed, versioned blueprint for a setup or a starter app. Its version and digest are pinned when you choose it, so it never upgrades silently.
EnvironmentThe exact target a release goes to, such as a preview or production.

People and access

TermWhat it means
RoleWhat a member may do across the organization: Owner, IT administrator (Admin), Technical administrator, Builder or Member. See Invite your team and set roles.
Technical ownerThe owner, admin or Technical administrator responsible for running an app or a setup. The title alone grants no cloud, spending or approval rights.
AudienceWho can open a deployed app: named people, directory groups, access groups or everyone in the organization.
Directory groupA group pushed from your identity provider through SCIM. It is read-only in Diakrin.
Access groupA business group IT manages in Diakrin. It can follow a directory group.
Connection tokenA personal token that lets your coding tool act as you over MCP. It never grants more than your own access.

Building and shipping

TermWhat it means
CapabilitySomething an app needs, such as reading a company data source. A requested capability is not an approved one.
GrantIT's approval for a named operation, with resource and field limits. The app and each employee need their own grants.
ReleaseAn immutable image built in your cloud from an exact source commit. A checked release has passed the customer-side checks.
PreviewA bounded, expiring deployment of a checked release, used to inspect it before production.
PlanThe exact release, target, cost estimate and access implications that a reviewer approves or denies.
OperationA tracked build or deployment with an ID, stages and states. The console, CLI and MCP show the same operation.
DeploymentA release applied to an environment. It counts as live only with fresh, verified evidence.

Saved is not the same as live

Diakrin keeps intent and evidence apart. Each state below proves only what it says, so check the state of the exact app and environment before you rely on it.

  1. Saved

    The app definition is stored. Nothing is built or approved yet.

  2. Requested

    The app asks for a capability. Nothing is granted.

  3. Approved

    Policy or IT permits the capability. It still needs a configured, verified connection.

  4. Built and checked

    An immutable image exists in your cloud and passed its checks. It is not deployed.

  5. Previewed

    A bounded, expiring preview ran. It does not replace production approval.

  6. Deployed

    The approved release was applied to the environment.

  7. Verified live

    Fresh, server-verified evidence matches the promoted image, and an authorized employee can open the app.

Next stepGet started →