GeoPulse
ActiveExplainable geospatial analysis as a provider-neutral service — boundaries, arrival and geofence detection, travel-time prediction, and coverage analysis behind a versioned API.
Last updated Jul 29, 2026
The problem
Geospatial answers usually arrive as a black box: a number with no way to see which model produced it, what data quality sat behind it, or why it changed since last week. Teams that need to defend a result — or move off a provider without rewriting everything — have very few options.
What’s being built
A multi-domain geospatial platform exposing a versioned HTTP API and shipping its own React console: boundary management, scenario and trajectory processing, arrival and geofence detection, travel-time and arrival-time prediction, coverage and service-area analysis, briefings, data-quality tracking, methodology and model registries, audit logging, and reporting. Recently detached from Replit and now independently deployable with provider-neutral configuration, authentication, and infrastructure.
Latest update
GeoPulse was detached from Replit and is now independently deployable with provider-neutral config, auth, and infrastructure. It is the service layer; client applications consume it over the versioned API.
Current milestone
Replit detachment complete; Curvio is the first external client consuming the versioned API
Tech stack
Get it
Follow this project
Get notified when there's a meaningful update — no noise, no marketing.
Confirm via email. Unsubscribe any time. No spam — ever.