Start here

Get started

The onboarding checklist: who does what, in which order, and what to prepare.

Deployment
BYOC and self-hosted

Onboarding takes a few people, each doing one part. Start with one team and one small app; you can widen access once the first app works end to end.

The onboarding path BYOC only

  1. Connect company sign-inIdentity administrator

    Follow Connect your company SSO: choose your provider, configure a pilot and confirm activation with your Diakrin onboarding contact.

  2. Enter your organizationEveryone

    Your onboarding contact or an administrator assigns your email before signup. Sign in with that email and verify it; an active assignment or invitation attaches automatically. See Invite your team and set roles.

  3. Set organization policyIT administrator

    In Get started, choose Set organization policy to save spending limits and the rules new projects follow.

  4. Connect your cloudOwner, admin or Technical administrator

    Open Infrastructure → New setup, choose AWS or Google Cloud and follow the steps. See Set up your company cloud.

  5. Build the first appBuilder

    In Apps, select New app and explain what it should do, or start from Create example app in Get started. See Create your first app and Connect your coding tool.

  6. Review and launchIT reviewer

    Check capabilities, cost and audience, approve the plan, then confirm the real app works for an authorized employee. See Review capabilities and deployment.

  7. Invite your teamIT administrator

    Add builders and reviewers once the first app works. See Invite your team and set roles.

Builders can start describing their app while a Technical administrator prepares the company cloud; the two paths meet at the first deployment.

Set up a self-hosted installation Self-hosted only

Install Diakrin in your own AWS account with the self-hosted install guide. There is no public registration. The person who installs Diakrin completes a one-time sign-in that creates the first owner and the only organization. Owners and administrators then add an authenticator app and save their recovery codes. The console walks the owner through five steps, each verified by the server from current evidence:

  1. LicenseInstallation operator

    Enroll the license, or import a signed license file; the step verifies the signed grant. A test license is labelled as one and is for disposable test installations only.

  2. WorkspaceOwner

    Verify administrator access and add a second administrator for independent app reviews.

  3. GitHubOwner

    Install the Diakrin GitHub App on your company organization for selected private repositories. Your GitHub Actions runner labelled diakrin-customer checks each save; CodeBuild in your account builds, scans and stores the app image.

  4. Deployment prerequisitesOwner

    Approve organization spending limits. The server checks DNS and TLS, isolation, the audit archive and the scanner.

  5. First appOwner + second administrator

    Deploy the supplied synthetic app through Apps. The second administrator approves its private preview.

The cloud installation itself (the Diakrin CLI, certificates, infrastructure and deploy) is in Install self-hosted Diakrin.

AI assistance is a separate optional card and starts off. Saved settings alone never complete a step.

Who does what

PersonFirst responsibility
Organization ownerCreates the workspace, chooses administrators and arranges onboarding
Identity administrator BYOC onlyConfigures the SSO application, its pilot users and optional SCIM provisioning
IT administratorSets spending limits, invites people, assigns apps and reviews access
Technical administrator or cloud administratorConnects the company cloud and verifies the infrastructure and employee access
BuilderDescribes an app and builds it within the app's approved access
Team memberAccepts an invitation and uses assigned apps

The owner and the identity administrator can be different people. Employees do not need database credentials or cloud administration access to join Diakrin.

Prepare for onboarding

  • The organization name and the person who will own the workspace.
  • Your identity provider and the exact work-email domains you use. BYOC only
  • An identity administrator and two pilot users, including one regular member.
  • A simple first app, its intended users and whether it needs real company data.
  • Your cloud account (AWS or Google Cloud today, Azure coming soon) and the person who can approve access to it.
  • Your Diakrin onboarding contact, who supplies the SSO setup packet and confirms activation. BYOC only

Know what is ready

The console keeps saved app definitions, requested capabilities, approved access and real runtime connections apart. A saved app or a green sign-in does not mean an app is deployed. Key concepts explains what each state proves.

For a blocked step, use Troubleshooting and help.

Next stepConnect your company SSO →