This website uses cookies

Read our Privacy policy and Terms of use for more information.

GuideGDE-054
TopicOsiris OSINT
DomainReal-time situational awareness
Last updatedSeptember 2026

Short answer: Deploy your own Osiris instance, enable only the data layers your case needs and use the RECON toolkit only against authorised targets. Record the fork, commit and enabled layers whenever you cite a finding.

What it isWhat is Osiris?
How to run itHow do you deploy Osiris for OSINT?
What goes wrongWhat are the pitfalls of a live dashboard like Osiris?
Go deeperRelated guides
What it is

What is Osiris?

Osiris is the practice of self-hosting the open-source Osiris dashboard, a real-time global intelligence map that fuses live flight tracking, CCTV feeds, earthquake and wildfire monitoring, conflict-zone data and network-reconnaissance tools into a single browser interface, to build situational awareness from public data sources rather than from a single lookup.

Osiris is an MIT-licensed, open-source project built by GitHub developer simplifaisoul and covered in independent tech press as a low-infrastructure alternative to commercial platforms such as Palantir. It runs client-side using WebGL and MapLibre GL, deploys free to Vercel in one click or self-hosts locally via Docker, and aggregates more than 15 public data layers, including OpenSky flight data, AIS maritime traffic, USGS earthquakes, NASA FIRMS wildfire detections, NOAA space weather and live news feeds.

It also ships a RECON toolkit built into the same interface: a TCP port scanner, DNS and WHOIS resolution, SSL inspection and a vulnerability scanner. Because it is an actively developed open-source project, several independent community forks exist with different feature sets, and there is no single official hosted instance; every deployment is self-run.

When to use this guide
•Building a live situational-awareness view of a region during a breaking event
•Cross-referencing flight, maritime or CCTV data with other case evidence in real time
•Monitoring conflict zones, seismic activity or wildfire spread as they develop
•Running basic network reconnaissance from the same interface as the map, against your own infrastructure
•Evaluating whether a self-hosted live-dashboard workflow fits before committing engineering time to it
How to run it

How do you deploy Osiris for OSINT?

Six steps from choosing which instance to run through to citing a live finding defensibly.

The tools

The following resources are used across the steps below.

Osiris: Free, open-source (MIT licence). The canonical repository, self-hosted via Docker or Node, or deployed to Vercel in one click.

Vercel: Free tier. The recommended one-click hosting target for a self-run Osiris instance.

OpenSky Network: Free, public flight-tracking API. The underlying data source Osiris's aviation layer depends on.

Before you begin
Stop at the login. Osiris's map view itself requires no login. Any credentials involved are your own, for an optional data-source API key or your own hosting account; nothing in this workflow logs into a service on a subject's behalf.
Legal considerations. Osiris is explicitly dual-use: its RECON toolkit, including the port scanner and vulnerability scanner, is legitimate for defensive research against your own infrastructure and can violate computer-misuse law if run against a system you do not own or have not been explicitly authorised to test. Independent press coverage of the project has noted this risk directly. The CCTV layer draws only from public feeds transit authorities already publish, not a private surveillance network; represent it as such and nothing more.

Subscribe to keep reading

This content is free, but you must be subscribed to Signal & Shadow to continue reading.

I consent to receive newsletters via email. Terms of use and Privacy policy.

Already a subscriber?Sign in.Not now