DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

Complete the first-install wizard

Run the one-time bootstrap that unlocks the platform, creates the first administrator, and seeds GitOps.

TutorialNew userAdministrator

What you will do

  • Normal authenticated routes and APIs stay locked until setup completes once.
  • GET /v1/setup/preflight reports exactly what still blocks setup, including a database that is still starting.
  • The bootstrap administrator must rotate the provisioned password at first login by default.
  • The wizard can seed starter profiles, generate secrets, and create the initial GitOps layout and repository teams.

Before you start

Stack
A running control planecurl -s localhost:8080/healthz
Bootstrap admin
NOPSAI_BOOTSTRAP_ADMIN_EMAIL and NOPSAI_BOOTSTRAP_ADMIN_PASSWORD set
Database
PostgreSQL reachable from the API
Browser access
http://localhost/ reachable from your workstation

Steps

  1. 01

    Check preflight

    Preflight tells you whether the platform can be set up right now and, if not, why.

    Read preflightbash
    curl -s localhost:8080/v1/setup/preflight | jq
    Expected result
    • A JSON document listing outstanding blockers. An empty blocker list means setup can proceed.
  2. 02

    Run the wizard

    Open the UI and work through the setup steps: readiness, runtime, GitHub, GitOps, teams, AI, and users. Optional steps can be skipped and configured later. The GitHub step is a single button that creates the App and hands you to GitHub to choose repositories; it asks for no App ID, key, or secret.

    Important
    • Setup apply errors include the actionable write or configuration reason. Read the message rather than retrying blindly.
    Verify
    • GET /v1/setup/status reports that setup has completed.
  3. 03

    Rotate the bootstrap password

    Log in as the bootstrap administrator. The forced rotation runs before you reach the application.

    Verify
    • You can log in with the new password and reach the dashboard.
  4. 04

    Confirm the runner registered

    Open System, then the dispatcher workspace, and confirm at least one runner is connected and dispatchable.

    Verify
    • The runner appears in the fleet table with a reachable, dispatch-enabled status.

How it works

Setup preflight is deliberately available before authentication so an operator can diagnose a stuck install without a token.

First-install setup does not force an env-file write for dispatcher TLS when a valid effective service JWT fallback is already configured.

Implementation evidence

  • doc/first-install-wizard.md

    The bootstrap flow, starter profiles, and production guardrails.

  • services/nopsai/setup_preflight.go

    Preflight behavior during cold starts.