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

All environment variables

Every documented environment variable with its owning service, default, and security note.

ReferenceAdministratorOperatorSecurity

Key points

  • Grouped by owning service so you can see what one component actually needs.
  • Required values are the ones a deployment cannot start without.
  • Security notes call out the values that must be rotated together or must never be reused across environments.

How it works

Bootstrap values are deliberately not the long-term source of truth. Once GitOps is loaded, most product settings move to configuration files under setting/system/.

Implementation evidence

  • config/config.go

    Config struct with yaml and env tags.

  • docker-compose.yaml

    Local defaults and required-value enforcement.