What WorldView Actually Does
WorldView by kevtoe is a free, open-source tactical intelligence platform that replicates the core function of Palantir's Gotham and Foundry products: aggregating heterogeneous real-time data sources into a single unified operational picture. It runs on a CesiumJS 3D globe and tracks 27,000+ live aircraft, orbital satellites, global vessel traffic, seismic events, road networks, and live CCTV feeds — simultaneously, at 60 fps. The GitHub repo is at github.com/kevtoe/worldview. A live demo runs at worldview.kt-o.com.
Why does this matter for founders and builders?
Palantir charged the US government hundreds of millions of dollars for essentially this: a system that pulls intelligence feeds from disparate sources, normalizes them, and renders them on a geospatial interface for operators to act on. WorldView proves the underlying architecture is not proprietary — it's a software problem, and the software is now free. The commercial moat was never the technology; it was the government contracts and data access. What kevtoe built in a single repo would have cost a defense contractor eight figures a decade ago.
What data sources does WorldView aggregate?
Each layer pulls from a different public API or data standard — this is precisely the hard part Palantir built a company around solving, and WorldView does it for free:
- Flights: FlightRadar24 and adsb.fi, merged for coverage — 27,000+ aircraft globally
- Satellites: TLE orbital data with SGP4/SDP4 propagation via satellite.js — positions computed client-side
- Vessels: AISStream.io WebSocket — 2,000–4,000 ships per 20-second burst, cached 60 seconds
- Seismic: USGS API — past 24 hours of earthquake activity worldwide
- Road networks: OpenStreetMap Overpass API
- CCTV: Live public camera feeds from London, Austin, and Sydney
How does WorldView handle 27,000 entities at 60 fps?
This is where the engineering gets interesting. React rendering 27,000 components is unusable. WorldView bypasses React's reconciler entirely for entity rendering — it uses imperative Cesium primitives directly, updating position data without touching the component tree. Aircraft positions are dead-reckoned between API update cycles: the last known velocity and heading extrapolate the current position at frame rate. The result is smooth 60 fps movement even when the underlying data refreshes every 10–30 seconds.
The AIS burst pattern
Vessel tracking uses a deliberate burst-and-cache pattern: connect to AISStream.io for 20 seconds, collect 2,000–4,000 vessel positions, disconnect, cache for 60 seconds, repeat. This solves the serverless timeout problem — a persistent WebSocket connection would exceed Vercel's function limits. The pattern trades slight data staleness for deployment simplicity, which is the correct tradeoff for a solo-built tool.
How does WorldView compare to Palantir Gotham?
| Feature | WorldView (kevtoe) | Palantir Gotham |
|---|---|---|
| 3D geospatial globe | CesiumJS (open source) | Custom / Cesium-based |
| Real-time flight tracking | 27,000+ aircraft via public APIs | Government/military feeds |
| Satellite tracking | SGP4 orbital propagation | Classified + commercial TLE |
| Vessel AIS tracking | AISStream.io (public) | Maritime authority feeds |
| Post-processing effects | GLSL: night-vision, thermal, CRT | Proprietary visualization |
| Deployment | Vercel, self-hostable, free | On-prem / classified cloud |
| Cost | $0 (open source) | $100M+ government contracts |
What tech stack does WorldView use?
The frontend is React 19 + TypeScript 5.9 with CesiumJS 1.138 via Resium, Tailwind CSS v4, and Vite 7. The backend is Express 5 with node-cache for API response caching and WebSocket support for the AIS stream. GLSL shaders handle the post-processing: CRT scanlines, green-phosphor night-vision, and FLIR thermal imaging. The whole thing deploys to Vercel as a full-stack application. API keys required: Google Maps 3D tiles, Cesium Ion, Transport NSW for Sydney traffic, and AISStream.io for vessels. Every layer degrades gracefully without credentials.
Can you self-host WorldView?
Yes. The repo is MIT-licensed and deploys to any Node-capable host. Vercel is the zero-config path — the project structure is already wired for it. You'll need to set environment variables for each API key. All layers are optional; the globe renders with just CesiumJS ion credentials, and you add data layers as you configure each API source. A self-hosted instance costs whatever your hosting plan costs — Vercel's free tier handles light traffic without issue.
Related: How I Use Claude Code as an AEO and SEO Tool
Verdict
WorldView is one of the more technically impressive solo GitHub projects I've seen. It's not a toy — it's a genuine geospatial intelligence dashboard that solves real engineering problems: multi-source data fusion, high-entity-count rendering at frame rate, graceful degradation, and production-ready deployment. The comparison to Palantir isn't hyperbole. The core value proposition of a billion-dollar defense contractor was: we can build the software to unify your intelligence feeds. That software now exists on GitHub for free. What Palantir sells is the contract, the compliance posture, and the classified data access — not the code.
Frequently Asked Questions
What is WorldView by kevtoe?
WorldView is a free, open-source real-time tactical intelligence dashboard built by a developer named kevtoe and published on GitHub. It renders live flights, satellites, ships, earthquakes, traffic, and CCTV feeds on an interactive 3D CesiumJS globe. It is functionally comparable to the geospatial intelligence interfaces built by companies like Palantir, using entirely public APIs and open-source libraries.
Is WorldView really comparable to Palantir?
For the core geospatial tracking and data fusion use case, yes. WorldView does what Palantir's Gotham platform does at a conceptual level: it aggregates heterogeneous real-time data sources into a unified operational picture on a 3D globe. Palantir's commercial advantage lies in classified data access, government compliance certifications, and long-term contracts — not in the underlying software architecture.
How do I run WorldView myself?
Clone the repo from github.com/kevtoe/worldview, add your API keys to the environment variables (Cesium Ion is the minimum requirement), and deploy to Vercel or any Node host. Each data layer — flights, vessels, satellites, seismic — is independently configurable and degrades gracefully if the corresponding API key is absent.
What APIs does WorldView use?
WorldView integrates FlightRadar24 and adsb.fi for flight data, TLE sources for satellite orbital data, AISStream.io for vessel tracking, the USGS API for seismic events, OpenStreetMap Overpass API for road networks, and public CCTV streams from London, Austin, and Sydney. Google Maps 3D tiles and Cesium Ion handle the base globe rendering.
What makes WorldView's rendering fast?
WorldView bypasses React's component reconciler for entity rendering, using imperative CesiumJS primitives directly. Aircraft and vessel positions are dead-reckoned between API updates — velocity and heading extrapolate the current position at 60 fps, producing smooth movement even when the underlying data refreshes on a 10–30 second cycle.
This post is a technical review of an open-source GitHub project. No affiliation with kevtoe or Palantir Technologies.