• GitLab Checking…
• Telegram Checking…
• Jira Checking…

What's here

Built one piece at a time. Greyed items are not implemented yet.

• Settings Connections the portal uses.
• Service catalog What exists, who owns it, what it depends on.
• Deployments Repositories and their open merge requests.
• Runbooks Procedures and incident write-ups.
• Self-service Crossplane claims, via merge request.

Last updated

—

By

—

Last updated

—

By

—

Optional. When connected, deploying to staging checks every Jira issue linked from the merge request's description and blocks the deploy unless all of them are Release Approved — or Ready For Staging Test on a re-deploy, once the MR already carries the For Release label. Not connected just skips that one check, with a warning.

Last updated

—

By

—

Accounts sign in with a code from an authenticator app after claiming an invite and setting up TOTP. Deactivating removes access without deleting the account's history.

No accounts exist yet. Sign in with the bootstrap token to create the first account.

Find the bootstrap token in .bootstrap-data/bootstrap-token next to compose.yaml (or in the mounted Secret, in Kubernetes).

Signed in as root. Create the first account — it becomes an admin.

Setup is already complete. Use Settings → Users to manage accounts.

Sign in as root instead

Checking your invite…

Loading…

Manual entry key

—