Government Software,
Rebuilt from Scratch
Not a legacy system with a new coat of paint. Not a generic platform configured for government. A purpose-built ERP designed around how municipalities actually operate.
The Problem We Saw
Most municipal software was architected in the early 2000s or earlier. The interfaces look it. The data models show it. And the contracts enforce it — multi-year lock-ins, per-seat pricing, and export fees that make switching prohibitively expensive.
The result: a city clerk tracks permits in one system, finance reconciles in another, utility billing runs on a third, and the citizen-facing portal is a fourth product that sort of syncs with the rest. When something goes wrong, the fix is a 12-to-18-month reimplementation and a vendor who blames your configuration.
Meanwhile, the 19,000+ municipalities under 50,000 residents are underserved entirely. The large vendors chase big contracts. Everyone else gets spreadsheets, or a system designed for a city ten times their size.
What We Built Instead
MuniNow is a single platform — one login, one database, one vendor — that covers 37 modules across every department a municipality runs. Finance, permits, utility billing, public safety, HR, parks, courts, records management, and more.
Staff work inside the platform, not alongside it. A permit application submitted by a citizen lands directly in the review queue. A utility meter reading triggers the billing calculation. A journal entry posts to the general ledger and immediately updates budget-to-actual reports. There is no nightly batch sync, no manual re-entry, no “the systems don't talk to each other.”
Finance gets the same treatment. A four-step year-end close wizard runs the books with a pre-close health monitor. Inter-fund transfers post paired journal entries with multi-level approval. CAFR generation ships 16 GASB 34/44 sections — fund statements, government-wide statements, 12 notes templates, and the statistical section — plus GASB 87 leases, GASB 96 SBITAs, and a GASB 103 MD&A template. Your auditor logs into a dedicated portal with PBC checklists and adjustment posting. Year-end stops being a six-week scramble.
The citizen portal is not a separate product — it's built into every module. Residents apply for permits, pay utility bills, submit service requests, and check case status without calling city hall. Staff see the same data, in real time, from their side of the platform.
37 Modules Across Every Department
Finance & Accounting
GL, AP, AR, budgeting, cashiering, bank reconciliation, property tax, purchasing
Community Development
Permits, licenses, code enforcement, planning & zoning
Public Works & Utilities
Utility billing, work orders, asset management, fleet, facilities, service requests
Public Safety
Police records, fire & EMS, animal control, court & citations
Community Services
Parks & rec, elections, meetings & agendas, engagement, mass communications
Records & Intelligence
Documents, contracts, retention, e-signatures, reporting, GIS, AI review, data warehouse
How We Think About the Work
Built for the 19,000
There are roughly 19,000 municipalities in the U.S. with populations under 50,000. Legacy vendors chase the largest contracts and ignore the rest. MuniNow is built for every city, village, and township — regardless of size or budget.
Auditable by Default
Every mutation is logged with user, timestamp, and before/after values. Row-level security is enforced at the database. 14 granular RBAC roles — including a dedicated auditor role for PBC checklists and adjustment posting, and a read-only viewer role for oversight access. This isn't a feature; it's the architecture.
Your Data, No Exceptions
Every record in MuniNow can be exported at any time — CSV, JSON, or PDF. 900+ API endpoints are included with every subscription. There are no export fees, no data hostage situations, and no proprietary formats.
Staff and Residents in One System
The citizen portal isn't a separate product. When a resident applies for a permit online, it lands directly in the staff review queue. When staff issues a license, the resident sees it in their portal. One system, two audiences, zero data sync issues.
The Stack
TypeScript end-to-end. Type-safe from the database schema through the API layer to the React components your staff interact with.
Next.js 14
Frontend
Server-side rendering, static generation, and React 18. Every page loads fast, renders on any device, and is indexable by search engines.
NestJS + tRPC
Backend API
Type-safe API layer with 900+ endpoints. Every procedure is validated with Zod schemas shared between client and server. No runtime type mismatches.
PostgreSQL + PostGIS
Database
Row-level security, JSONB for flexible schemas, PostGIS for spatial queries. Fund accounting, parcel data, and GIS layers all in one database.
Redis + Upstash
Cache & Queues
Rate limiting, session caching, and background job queues for payroll runs, bill generation, and report scheduling.
See It for Yourself
We demo with your use cases, not slides. Pick the departments that matter most to you and we'll walk through them live.