Open-source municipal infrastructure

Municipal software cities can actually own.

CivicSuite brings everyday city hall work—records, meetings, municipal code, notices, and accessible public information—onto a computer the city controls. No cloud account and no telemetry.

Download Windows Local Explore the product

Public beta. Built for evaluation today; not production-, city-, or procurement-ready.

CITY-CONTROLLED RUNTIME

Staff workflowCivicCoreLocal data + AI
Cloud account
Not required
Telemetry
None by design
Per-seat pricing
None
Decision authority
Human

The default profile keeps documents, audit history, the database, and the AI model on city-controlled hardware.

One Windows installerNo Docker, WSL, or terminal for the clerk path
Six workflow areasShared services plus five municipal modules
Open foundationsApache 2.0 code · CC BY 4.0 docs

Why CivicSuite exists

Public work should not require surrendering public control.

Municipal teams often face cloud lock-in, recurring seat costs, scattered workflows, and AI tools that move sensitive material beyond the city's boundary.

CivicSuite takes a narrower path: local-first software for the high-friction work around public records, meetings, code, notices, and accessibility. It assists staff without pretending to replace their judgment—or the city's systems of record.

The city-core beta

One shared platform. Five focused workflows.

CivicCore supplies the common foundation. Each module stays bounded around a real municipal job.

00 CivicCoreIdentity, audit, retention, ingestion, search, task queue, and local AI contracts. Shared platform 01 CivicRecords AIPublic-records intake, search, and response-drafting support. City core 02 CivicClerkMeetings, agendas, packets, minutes, votes, and public archives. City core 03 CivicCodeSearchable municipal code and ordinance access with source-backed guidance. City core 04 CivicNoticePublic-notice creation and publishing workflow support. City core 05 CivicAccessPlain-language and translation drafts, accessibility review, and records-ready export. City core

How it works

Local by default. Modular by design.

  1. 1
    Install the city-core app

    A single Windows MSI brings the desktop shell, portable database, local services, and model runtime together.

  2. 2
    Set up the city's workspace

    First run covers the city profile, first administrator, backup location, model download, checksum verification, and readiness checks.

  3. 3
    Work inside a human-controlled loop

    Modules organize and draft. Staff review evidence, make decisions, and remain accountable for every public action.

Read the full architecture
Diagram showing the CivicSuite desktop connected to CivicCore, five city-core modules, and local city-controlled infrastructure
Product modules depend on CivicCore. CivicCore never depends on a module.

Operating principles

Guardrails, not slogans.

01

City-held by default

The default runtime avoids vendor cloud dependencies and outbound telemetry.

02

AI drafts. Humans decide.

No auto-release, auto-denial, auto-redaction, auto-enforcement, or legal determination.

03

Evidence over version labels

Clean-machine checks, source pins, checksums, and honest status drive maturity claims.

04

Depth before catalog count

Six city-core workflows ship in the beta. The broader catalog is clearly labeled queued, foundation, or planned.

Current status

A serious beta, described without shortcuts.

CivicSuite Windows Local v1.0.2 is a GA candidate open for public beta. It has passed the project's clean-machine acceptance work and is available for hands-on evaluation.

Adoption boundary

Not production-ready.

Not city-ready, procurement-ready, macOS lifecycle-certified, or a full-suite release. No live municipal deployment is documented.

See module-by-module truth

Documentation

Start with the evidence you need.

The umbrella repository is the canonical source for product status, installation, architecture, security, and release evidence.

For operatorsUser manualInstall, first run, and everyday workflows For evaluatorsProject statusWhat ships, what is queued, and what is planned For technology teamsArchitectureRuntime, boundaries, dependencies, and data flow For security teamsSecurity policyThreat reporting and private advisory routing For trust reviewProvenanceChecksums, code signing, and source pins For contributorsContributingFind the right repository and workflow

Try it responsibly

Put the public beta through real municipal workflows.

Use representative, non-production material. Verify the installer. Test the fit. Tell the project exactly where it falls short.

Download the betaJoin the discussion