Contact us for a demo
Tell us the county, the parcels and the workflow you care about, and we will walk the portfolio through your data rather than ours. If you are evaluating the SDK, say so — we will bring an engineer to the first call instead of the second.
Tell us what you're working on
Fields marked with an asterisk are required. Everything else just makes the first call more useful.
Questions we get most
Can you demo on our county?
Yes — that is the point. Give us the counties or states in the form and we will point the federation registry and the analysis layers at those upstreams before the call. If a jurisdiction has no public parcel service, we will tell you that instead of working around it quietly.
Is the source code really available?
Yes. Source-code licensing covers the repository — backend, frontend, migrations and deployment configuration — not just a compiled bundle. Terms depend on which solutions and how you intend to redistribute; ask on the first call.
Do we need ArcGIS or ATTOM accounts?
For the parts that use them, yes — ArcGIS, ATTOM, Regrid, MapTiler and Google keys are billed by those providers and are not included with the SDK. Plenty of the platform runs on public services and your own files with no third-party key at all.
Where does our data go?
The DuckDB WASM processing layer runs entirely in the browser — files you load, filters you run and spatial joins you compute never leave the device. Self-hosted and air-gapped deployments are supported for everything else.