Archigov · docs

Archigov Documentation

Coordinated, systematic architecture decision-making — argued, linked to your standards, decided by the right board on the record, and kept true against your real estate.

Archigov is an open-source architecture governance platform. It runs as one container with one SQLite file, and it is useful within minutes of starting with an empty database. These pages cover running it, the ideas it is built on, and the exact behaviour of every part you can configure or call.

The Archigov Overview page as a decision maker, opening on the work waiting for her
The Overview as Mia Hughes, a decision maker: what waits on her first, then the governance pipeline and the state of the estate.
Start hereQuickstartRun Archigov with Docker, load the demo estate, and switch between personas to see each role's view in five minutes. TutorialYour First DecisionDraft an architecture decision, test its argument, submit it, record positions by area, and declare the outcome. ConceptsHow It Fits TogetherDecisions, the governance catalogue, boards, the derived model and evidence — and the lifecycle that connects them. GuidesRun It in ProductionSelf-host with Docker Compose, sign in with Microsoft Entra ID, connect Azure and Azure DevOps, replicate with Litestream. ReferenceRule DSLMake standards, policies and decisions machine-checkable: scopes, matchers, operators and evidence assertions. ReferenceHTTP APIEvery endpoint the UI uses is available to you, gated by the same capabilities, with a signed evidence pack to take away.

#What Archigov Does

  • Decisions are argued in three parts — a recommended option, the justification the board will test, and the consequences including the risks explicitly accepted — and can be checked before they reach a board.
  • Decisions link to what they rest on: standards, principles, patterns and policies in one governance catalogue, each carrying control references (ISO 27001, DORA, DSPT, the EU AI Act, NIST and others) and, where possible, a machine-checkable rule.
  • Boards decide on the record. Reviews are routed to the right board; decision makers record their own positions on the areas they own; the chair moderates and declares the outcome the positions allow. Sessions derive their agenda and their minutes from the records.
  • Decisions stay true. The as-is architecture is derived from your cloud estate rather than drawn, so every adopted rule and every decision constraint is evaluated continuously. Drift becomes a finding that cites the decision it contradicts.
  • Evidence, not assurance. The audit log is a hash chain; the evidence pack is signed with Ed25519 and can be verified by a third party. Nothing in the product asserts that you are compliant.

#Find Your Way

If you want to…Read
Try it on your laptopQuickstart
Understand the governance modelHow it fits together, then Boards and reviews
Deploy it for your organisationSelf-host in production and Configuration
Connect your estateConnect Azure and Azure DevOps
Turn a standard into a checkWriting rules and the Rule DSL
Give an auditor what they needEvidence and audit and Exports
Decide who can do whatRoles and capabilities

Note

This documentation describes Archigov 0.1. The source, the changelog and the issue tracker are on GitHub. Archigov is licensed under AGPL-3.0; see Licensing.