ArcGIS GeoEvent and Velocity alternative planning.
Real-time GIS migrations should start with event ownership, latency needs, alert rules, retention, and who acts on the stream. The map is only one view into a location event pipeline.
Buyer problem
The issue is workflow ownership, not just software choice.
The pain appears as expensive streaming infrastructure, black-box feeds, unreliable alerts, dashboards that lag operations, and telemetry data that is hard to reuse outside one ArcGIS workflow.
Modern stack options
Build the replacement around the output buyers need.
Kafka, Redpanda, MQTT, or cloud pub/sub for event ingestion and fan-out.
PostGIS, TimescaleDB, object storage, or warehouse tables for current state and history.
Custom APIs and WebSocket/SSE channels for live map and dashboard updates.
Grafana, Superset, or custom operations views for alerting and monitoring.
Rules engines, queues, notifications, and audit logs for action-oriented workflows.
Migration risk
Validate the hidden dependencies before expanding.
Latency, retention, replay, and alert guarantees need explicit service-level expectations.
Telemetry is often noisy; validation and deduplication are part of the product, not a cleanup task.
Maps should show only actionable live state; raw streams can overwhelm operators.
Security, device identity, and feed ownership matter when sensors or field devices are involved.
First pilot
Move one feed into an owned event pipeline with an action view.
Pick one fleet, sensor, work-order, or incident feed; ingest it into a streaming layer; persist state and history; and build a simple operator view with alerts.
Success criteria
The feed has documented latency, validation, retention, and failure behavior.
Operators can see current state and receive actionable alerts.
The same event data can feed reports or downstream automation outside the live map.
FAQ
Questions buyers ask before switching.
Does Kafka replace GeoEvent Server?+
Kafka can replace the event backbone, but not the whole workflow. You still need geospatial state, alert logic, map views, monitoring, and operator actions.
What replaces ArcGIS Velocity?+
A cloud-native stack may combine managed pub/sub, stream processing, PostGIS or warehouse storage, alert services, and custom dashboards. The right design depends on event volume and action requirements.
What is the best first real-time migration?+
Choose one feed where the business action is clear: dispatch, alert, status, threshold breach, exception queue, or daily operational report.
Turn the comparison into a migration plan.
Use the kit to inventory your current ArcGIS footprint, then scope one practical pilot with clear owner, risk, stack, and acceptance criteria.
Related low-profile guides