Compare
Compare what cities can verify.
Cities buy in modules, not monoliths, so compare verifiable capabilities, not brand names. Put the same questions to every vendor — including us; here are ours, line by line.
Read the checklistThe capability checklist
Nine lines a vendor should prove
Ask every provider to demonstrate the claims that matter to your city. We show ours in an illustrative demo, then validate your selected workflows with your data during the pilot.
| Capability | What we show | What to ask any vendor |
|---|---|---|
| Unified resident & parcel record | One history per resident and parcel, linked across modules when identifiers are available — not per-department silos. | Trace a resident and a parcel across departments in one view; ask how duplicates are handled. |
| Modularity & fail-closed entitlements | 108 modules; nothing is reachable unless a valid, current entitlement explicitly enables it. Turning a module off hides its surfaces without deleting records. | Show a missing, expired and malformed entitlement. Is access fail-closed? Can a module return with data intact? |
| AI, included | Included at no software charge, grounded in your city's records, read-only and drafts only — it cites its sources, and a person approves. | Inspect an answer's sources and a no-answer case; ask how AI is audited and whether it is metered. |
| Data & APIs | Open API, full export on demand in open formats, no per-record export fees; at-cost managed hosting, or self-hosted. | Request a sample export and an API walkthrough; ask what leaving would cost. |
| Records & verification | Selected official milestones mint signed civic receipts, Merkle-sealed nightly and independently checkable. | Verify a sample record — and a tampered copy — yourself. |
| Payments | Card fields are hosted by the processor; card numbers never enter our infrastructure. Charges reconcile against a durable ledger. | Ask where card data is entered and stored, and who carries the card-data obligations. |
| Security & isolation | One city, one tenant, isolated at the database layer — cross-tenant reads are blocked in the database, not only in code. Deny-by-default everywhere. | Ask how cross-tenant access is blocked and how that is tested before every release. |
| Transparency | Open data and budget transparency are published by default — public without a records request. | Ask what is published by default versus on request, and in which formats. |
| Implementation & migration | Agreed pilot-scope records imported at no charge; an isolated, resettable sandbox; a timed setup and a confirmed rollout plan. | Review field mapping and an import preview; run a workflow, then reset it; request the rollout plan. |
A fair comparison
Where incumbents are strong
A credible comparison says where others are better. Here is what long-established providers genuinely do well — and what to verify when you weigh them.
| Where incumbents are strong | What to ask for |
|---|---|
| Integration ecosystems | Years of connectors to third-party systems and legacy databases — ask for a live list of the interfaces you need and reference sites. |
| Local partnerships | Regional consultants who know local workflows and funding — ask who will implement, where they have done it, and for reference calls. |
| Mature service contracts | Long-standing SLAs, support processes and maintenance agreements — ask for the actual SLA text, response targets and the named escalation path. |
| Deployment scale | Many comparable jurisdictions already in production — ask for reference calls at your size and scope, not just logos. |
| Category depth | Specialized products with deep features after years in service — ask for a live demo on your hardest cases, not slides. |
No provider is named here. The strongest vendors will welcome a line-by-line scorecard — so will we.
Bring your scorecard — we'll answer line by line.
Send your questionnaire or scorecard. We'll answer in detail, then pilot the workflows you choose with your data, in a resettable sandbox.
Request a pilot Send your scorecard