Finance, utilities, permits, payroll, and payments. Running today in 2,800+ agencies. Processing $4.1B in citizen payments a year. Built for the technical buyer who wants to read the whitepaper.
Every module ships with the same architecture, the same permissions model, the same audit trail, and the same API. What changes is the shape of the data.
Cirrus Intelligence reads a building-permit submittal against local code and flags the five things the reviewer actually needs to look at. Reviewers see a live queue, prioritized by risk and submitter history.
| ID | Address | Type | Risk | Status |
|---|---|---|---|---|
| P-2089 | 412 Oak St. | SFR addition | Low | ● OK |
| P-2088 | 19 Mill Lane | Deck | Low | ✦ AI review |
| P-2087 | 221 Baker | Commercial TI | Med | ⚑ Setback |
| P-2086 | 9 Spruce Ct. | Re-roof | Low | ● Auto-issue |
| P-2085 | 844 Laurel | Accessory | Low | ● OK |
| P-2084 | 77 Front St. | SFR new | High | ⚑ 3 flags |
Exceptions surface the moment the AMI feed lands. Cirrus Intelligence re-reads failed meters against six months of seasonal history and flags what a human actually needs to review.
Not a chatbot grafted on top. A first-class system element trained on 35 years of government workflow patterns, grounded in each agency's own data, auditable every step.
Route incoming vendor invoices to the right PO and GL code automatically. Reversible, auditable, 94.2% accurate in production.
Read a permit submittal against local code. Flag only what needs reviewer judgment. Cut queues from weeks to days.
Draft budget narratives, variance explanations, and council summaries in the agency's voice. Grounded in the book.
Every module inherits Cirrus's identity, permissions, audit, and reporting systems. AI features are built into each, not bolted on.
Every customer on this page is named. Every metric was reviewed with the agency that reported it.
Every Cirrus module ships with a REST and GraphQL surface, an event bus, and a documented schema. Data isn't locked in the finance system's basement. Queries return in the same JSON your CIO's data warehouse already drinks.
SOC 2 Type II. StateRAMP-ready. MFA on every tenant. Tenant-level encryption keys. Open OIDC for SSO.
Read the docs →# Fetch current-period GL balance, variance-flagged curl -H "Authorization: Bearer $CIRRUS_TOKEN" \ "https://api.springbrook.com/v1/finance/gl?agency=red-wing-mn&period=2026-03&flags=variance" # response { "agency": "red-wing-mn", "period": "2026-03", "general_fund": 24118744.22, "variance_flags": [ { "account": "01-410-4200", "delta": -0.062, "ai_note": "Street maintenance trending 6% under budget..." } ], "reconciled_at": "2026-04-19T14:02:14Z" }
A 30-minute working demo on your own general fund. No slides, no choreography. Bring your schema.