Read-only, least-privilege access
We authenticate through your systems' own APIs with scoped, read-only credentials — typically a service account limited to the layers and record types you approve. No write access, no admin rights.
Integrations
Works With the Systems You Already Run
OpenCivic layers on top of your existing stack — no rip-and-replace. We connect to your permitting, GIS, code, and identity systems through their published APIs.
Permitting & Licensing
Tyler EnerGovAccela Civic PlatformOpenGov PermittingCityViewCivicPlus
GIS & Mapping
Esri ArcGISArcGIS REST / FeatureServerCounty parcel layersFEMA & CAL FIRE data
Code & Records
MunicodeAmerican Legal PublishingGeneral Code / eCode360Laserfiche
Identity & SSO
Google WorkspaceMicrosoft Entra IDOktaSAML / OIDC
Don't see your vendor? We add connectors on request — tell us what you run.
How the connection works
Read-Only, Least-Privilege, No Migration
Connecting OpenCivic doesn't mean moving your data or handing over write access. We read what we need, when we need it — and your systems stay the source of truth.
No data migration
Your records never move. Parcel data, permit history, and code sections are queried live at the moment a question is asked, so answers reflect your current system of record — not a stale nightly copy.
Live in about two weeks
A standard connector — permitting, GIS, code, or SSO — is wired and validated inside the two-week rollout. Custom or on-request vendors take a little longer; we scope the timeline up front.
Security and data-residency questions? See how we handle your data.