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

Supported deployment models

Four shapes the platform is built for, and what each one implies for runtime and database.

ConceptAdministratorOperator

Key points

  • Docker Compose — development, demos, evaluation, and small single-host installs. Docker runner, bundled PostgreSQL 15.
  • Release bundle — version-pinned single-host deployment. Docker runner, deployment-managed PostgreSQL.
  • Helm / Kubernetes — cluster production deployment. Kubernetes runner, bundled or external PostgreSQL.
  • Hybrid runners — one central control plane with remote Docker or Kubernetes runners. Control-plane PostgreSQL.
  • The Helm chart deploys PostgreSQL, API, AAA, dispatcher, git-bot, UI, Gotenberg, and the Kubernetes runner.

How it works

Install the CLI from https://github.com/nopsai/nopsai/releases/latest, extract the binary onto PATH, and remove the archive before running install commands. nopsai install kubernetes generates non-secret Helm values, an installation.md, and a separate Secret manifest for new installations. Values and locks are GitOps-friendly; apply the Secret manifest directly for a first install, or seal and encrypt it before it enters GitOps.

Managed PostgreSQL is supported by disabling the bundled StatefulSet and replacing the generated database URL.

topology.dispatcherGRPCAddress controls the dispatcher endpoint injected into API and Kubernetes runner pods, and the same topology block carries the internal NopsAI, AAA, git-bot, and Gotenberg service URLs for custom DNS or split-service deployments.

Examples

Identify what an install actually isbash
curl -s "$NOPSAI_URL/version" | jq '{product_version, api_version, runner_protocol_version}'
curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/system/dispatcher" | jq '.runners | length'
Result

Build identity plus the number of registered runners: enough to tell a single-host evaluation from a deployment with a separate execution plane.

Limits

Current behavior
  • There are no Terraform modules and no AWS-, Azure-, or Google-specific deployment automation in this repository.
  • Raising every replica count does not by itself produce a highly available deployment.

Implementation evidence

  • deploy/helm/nopsai/values.yaml

    Chart topology and component values.

  • doc/release-bundles.md

    Versioned release assets and generated install files.