Get the weekly radar
One short email with the freshest products, every week.
Grounded in available product and source data
Analysts doing open-source intelligence work often end up with a wall of browser tabs: one site for aircraft, another for vessels, another for GPS interference, and no easy way to see when two of those pictures line up in the same place at the same time. osint-geospatial-console, built as the Velocity project, is a self-hosted osint geospatial dashboard: a 3D globe that fuses live aircraft, vessels, satellites, GPS jamming, earthquakes, internet outages, submarine-cable status, and conflict events into one view instead of leaving that correlation to the analyst's eyes. By its own description, it's meant to be a console analysts can own — position history stays on their own machine and can be replayed for as long as they keep it — and the core feeds run without requiring an API key.
Getting it running doesn't take much. With Docker 24 or newer and the compose plugin, the setup is a clone, an optional copy of the .env file, and a single docker compose up, which brings the API, the web app, and nginx up together — by the project's own account, one command and you're up. Skipping Docker means installing Node 20+, pnpm 9, Python 3.12, and uv for the backend's dependencies instead. Either path, the client needs a browser with WebGL2 support, since the globe is a CesiumJS render that leans on the GPU rather than the backend. The first session opens with traffic already moving — aircraft, vessels, earthquakes — and a short in-app tour you can reopen later from Settings.
Because the backend also runs as an MCP server, a solo analyst can point an AI agent at the same live feeds the globe renders, instead of asking that agent to scrape a dozen separate tracker sites or answer from whatever it learned before its training cutoff. The repository also works as a Claude Code plugin marketplace: installing it wires up the MCP server together with an analyst skill, a set of slash commands, and a dedicated watch-officer agent in one step. That combination is built around a single analyst working with one agent at a time — it extends a personal workflow rather than standing up shared infrastructure for a team.
A few things are worth knowing before you commit time to it. It's built for one analyst, not a team — there's no multi-user account or role system to speak of. Most application state lives in memory, so a backend restart clears saved incidents and the regions you were watching, though a short-lived local buffer keeps position-track history for replay. Vessel coverage isn't uniform either; it's described as densest over Northern Europe and thinner elsewhere, with an optional key filling in some of that gap. And the 3D satellite view will, in the project's own words, eat your VRAM — the lighter 2D dark map is the safer default until you know your hardware can handle the heavier mode.
Running osint-geospatial-console requires either Docker 24 or newer with the compose plugin, or a manual setup with Node 20+, pnpm 9, Python 3.12, and uv for the backend's dependencies. Either route also needs a browser that supports WebGL2 — a recent Chrome, Edge, or Firefox — since the 3D globe is a GPU-bound CesiumJS render. No API key is required to get the core feeds running; keys are optional and only extend coverage.
In osint-geospatial-console, most application state lives in memory, so a backend restart clears saved incidents and the regions you were watching. The position-track replay buffer is the exception: it's kept in a local SQLite store on disk with a roughly 7-day retention window, so recent track history survives a restart even though the rest of your session doesn't.
osint-geospatial-console is documented and built primarily as a self-hosted project that you run yourself, most commonly through the Docker quick start. Different snapshots of the project's own documentation aren't fully consistent about whether a separate hosted endpoint exists alongside that self-hosted setup, so if a managed option matters for your use case, check the repository's current README or releases yourself rather than assuming either way.
osint-geospatial-console is open-source software released under the AGPL-3.0 license that you self-host rather than pay for as a hosted service with a published price. Running it costs whatever compute and GPU you put behind it — Docker and a WebGL2-capable browser are enough to get started — but no official pricing page for a separate managed or hosted tier turned up in the documentation, so don't assume one exists at any particular price point.
