Preview only. Not a live product
The software infrastructure for state and local government.
Northgrid is the substrate for civic operations: intake, classification, policy-aware routing, and auditable action. It sits across your existing systems, captures how your agency actually works, and helps your staff work smarter with every decision.
SOC 2 Type II
StateRAMP authorized
Records-retention native
~
$
B
–
mo
.
M
The system
One substrate. Five components. Everything else is a workflow.
Northgrid is not a portal, a CRM, or an inbox. It is the layer beneath them: the place where civic work is described, routed, executed, and made permanent. Each component is independently deployable; together they form a single, auditable record.
01
Intake
Channel-agnostic capture
What enters the substrate. Forms, email, phone, walk-ins, and partner feeds enter through one normalized pipeline as typed records.
Every channel · one stream
03
Action
Policy-aware routing
Ordinances compiled into typed, versioned rules, dry-run testable and counsel-reviewable. The substrate drafts; humans decide.
Drafts prepared · humans decide
04
Knowledge
Operational memory
Every approval, condition, and override is observed and indexed. Institutional memory becomes searchable infrastructure the whole agency can draw from.
Tribal memory · made permanent
05
Visibility
Auditable by default
Every event hash-chained (SHA-256 / ED25519) into an append-only log. Open-records exports read directly from the audit log with cryptographic verification.
Chain verified · FOIA-ready
Why we are building this
The work is too important to keep running on inboxes and tribal memory.
Government work is being done by extraordinary people on infrastructure that does not match the importance of what they are deciding. Permits stall in someone's email. Policy interpretations live in one senior planner's head.
Records requests trigger forensic projects through three different systems. Northgrid does not replace what works. It captures the thinking that gets lost between systems, encodes the policies that already exist, and gives every staff member access to the institutional memory that retirements and turnover otherwise erase.
The work is too important to keep running on inboxes and tribal memory.
Northgrid
Founder
Built by an operator who has lived inside it.
Edward
Founder & CEO
Edward has spent his career inside local governments, working alongside the operators Northgrid is built to support. He has seen firsthand how institutional knowledge gets lost, how decisions queue up in inboxes, and how capacity erodes when the operational substrate is missing. He is bilingual in English and French and holds an MBA and a Master of Science in Information Systems.
Local government operator
MBA
MS · Information Systems
Bilingual EN/FR
Capabilities
Built like infrastructure. Operated like one.
The primitives below are not features. They are the load-bearing surfaces every civic workflow eventually needs.
Auditable by default
Every action is hash-chained. Open-records requests are a query, not a forensics project.
Connector substrate
One typed interface for legacy systems of record: permitting suites, GIS, financial systems, document archives. No vendor names, just standards.
Who we serve
For the institutions that cannot fail.
A missed record is not measured in churn. We work with jurisdictions that know this. Counties that run their own permitting. Cities consolidating fragmented intake. State agencies modernizing without rip-and-replace.
We are selective in who we serve. We work with the institutions that treat operations as infrastructure.
Engagement
How we begin. In weeks, not quarters
Northgrid is a substrate, not a replacement platform. A proof-of-value runs in 4–8 weeks: mapped, deployed alongside, and cut over by domain.
Then we operate in the open. No multi-quarter implementation. No legacy-vendor timelines.
Proof-of-value to live
4–8 weeks
01
Week 01
Phase 01 · Diagnostic
Map the work
One week. We sit with operators, read your ordinances, and document the actual flow, not the org chart.
02
Wks 02–05
Phase 02 · Shadow run
Deploy alongside
Northgrid runs in shadow against your existing system. Same inputs, parallel outputs. No citizen sees a change.
03
Wks 06–08
Phase 03 · Cutover
Cut over by domain
One workflow at a time, with full reversibility. Proof-of-value signed and live within 4–8 weeks of kickoff.
04
Ongoing
Phase 04 · Operations
Operate in the open
Quarterly system reviews with your counsel and IT. Every rule change reviewed. Every export traceable.
Pricing
Priced by jurisdiction.
Tiers 01 to 03 are published, fixed, and final. Tiers 04 and 05 are scoped against operational footprint. Switch the toggle to see each set.
Every engagement begins with a real conversation. Substrate, policy engine, and audit log included in every tier.
Common questions
Everything you need to know.
Cannot find what you are looking for? Our team is one message away.
Does Northgrid replace our system of record?
No. Northgrid sits alongside your existing systems and becomes authoritative for the workflows you choose, in the order you choose. Cutover is per-domain and reversible
How does this differ from a workflow tool or low-code platform?
Workflow tools express process. Northgrid expresses policy: typed, versioned, and reviewable by counsel. The audit log is not a feature; it is the substrate.
What about records retention and FOIA?
+ Retention schedules are applied at write, not after the fact. Open-records exports read directly from the audit log, with cryptographic verification of the chain.
Where is data hosted, and under what controls?
Single-tenant deployments in StateRAMP-authorized environments, with optional in-state residency. SOC 2 Type II controls apply across all tenants; jurisdiction-specific controls are negotiated in the brief.
Can our counsel review the policy engine?
Yes, and they should. Every rule renders to a plain-language preview alongside its typed definition. Counsel sign-off is a first-class step in our deployment process.
What happens if we want to leave?
A signed export of the full audit log, the rule sets in their typed form, and a documented schema is produced on request. No proprietary lock on the public record. Ever.