Your cloud (BYOC)

App runtime and technical ownership

Configure company settings for an app, enroll its runtime and stop it safely.

Deployment
BYOC and self-hosted

A company cloud setup provides shared infrastructure. Before an app can run there, IT records the app's company configuration and a technical owner enrolls its runtime. This guide is for IT administrators and technical owners.

  1. Configure the appIT administrator

    Region and profile, private access route, identity issuer and audience, named sources, quotas and reviewers.

  2. Enroll the runtimeTechnical owner

    Bind the exact organization, project, app and environment to a validated connection, with fresh approval.

  3. Watch runtime statusTechnical owner

    Fresh, stale, blocked or unknown, with the last observation and next check.

  4. Disable or revokeTechnical owner

    Stop later effects safely. Revoking an installation is permanent.

Company configuration

In Settings → Organization administration, select a project and reviewed app to configure the region and profile, private company access route, company identity issuer and audience, named source metadata and quotas, and eligible independent reviewers. Each reviewer must already hold delegated plan-review authority.

Saving configuration neither grants source access nor verifies sign-in, network enforcement or runtime readiness.

The read-only starter uses synthetic data at first. Selecting a data source IT has reviewed records a read-only requirement for that one named operation. It does not change the template or grant access: the app and each employee still need their own grants.

Who is the technical owner

An owner, admin or Technical administrator can be an app's technical owner. The technical owner manages the app's users alongside the builder and holds the runtime controls below. The role is a responsibility, not a permission: it grants no cloud, spending or approval rights by itself.

Enroll the runtime

IT supplies the reviewed identity and data-source settings. The technical owner then enrolls the runtime, which needs current runtime-management authority.

Enrollment ties the exact organization, project, app and environment to a validated connection, with a fresh approval. If your cloud provider has an outage, you can still disable or revoke an enrolled runtime, but you cannot enroll or start new work.

Disable or revoke

Disable app runtime lets work already in progress finish, then blocks anything new, including access to data. Cloud work that was already submitted is not cancelled instantly, and any uncertain result stays visible.

Resuming needs a fresh, approved enrollment. Revoke installation authority is permanent for that installation.

Read runtime status

StatusMeaning
Fresh runtime observationDiakrin observed the runtime recently and the evidence is current
Stale observationThe last observation is older than its evidence window
Runtime blockedA named blocker prevents execution
Runtime unknownDiakrin cannot currently observe the runtime

Each status reports the last observation, when that evidence expires, the next check and anything blocking the app. A saved setup or a passing local test does not prove the runtime is ready.

Infrastructure status

Use Review infrastructure for your company's cloud installation and foundation status when your role permits it. Foundation readiness does not prove that an app has built, deployed or passed employee access checks.

Next stepCreate your first app →