Akashic
Live public-source geospatial intelligence in one operational workspace requiring NO API keys.
Akashic is a self-hosted intelligence workspace that brings aircraft, satellites, earthquakes, weather, public radio, infrastructure, country intelligence, public cameras, and open-source reconnaissance onto a single interactive map.
it is built for exploration and correlation, not passive dashboard watching. layers can be combined, entities can be inspected in place, and the intelligence deck keeps live events and strategic context visible without replacing the map.
Important
Akashic consumes public and third-party data that can be delayed, incomplete, inaccurate, unavailable, or subject to separate terms. it is not an authoritative source and must not be used as the sole basis for safety, navigation, emergency, military, legal, or financial decisions.
why Akashic
one map for live and strategic geospatial data
key-free default setup with no required .env values
flat map, globe, satellite, terrain, street, night, weather, and photorealistic views
dense entity details instead of shallow map markers
streamed username and email reconnaissance with structured findings
live public radio discovery with station metadata and resilient playback
country, city, building, airport, aircraft, satellite, seismic, and camera inspection
an intelligence deck for events, indicators, infrastructure, markets, and regional context
server-side upstream adapters that keep browser integrations small
Workspace
Map Experience
Akashic keeps the map as the primary interface. the surrounding controls expose:
independent data-layer switches with live counts and source state
standard, crt, night-vision, thermal, radar, satcom, and noir treatments
aerial, satellite, street, light, dark, topographic, national geographic, night-lights, hybrid, and 3d imagery modes
map and globe projection switching
entity search, camera controls, zoom, coordinate readout, scale, and camera altitude
draggable detail surfaces that preserve spatial context
Intelligence layers
the Geo-Intelligence workspace combines live upstreams with curated or derived strategic registries. representative coverage includes:
conflicts, unrest, displacement, sanctions, and military activity
airports, aircraft, satellites, spaceports, and gps interference
ports, shipping lanes, waterways, chokepoints, cables, and pipelines
nuclear facilities, radiation, thermal anomalies, and seismic activity
internet infrastructure, air quality, health, weather, and natural hazards
markets, trade, consumer prices, economic centers, and infrastructure pressure
public news, live streams, country summaries, and positive events
each layer should be interpreted according to its source label. a rendered point is not automatically a verified live incident.
Recon mode
Recon mode performs a concurrent public-profile sweep using the source definitions in data/recon-sources/.
checks are streamed into the ui as each request finishes
found, missing, blocked, timeout, and error states remain distinct
common block pages and false-positive responses are rejected
metadata is normalized into titles, bios, profile images, links, and location hints
favicons provide source identity without maintaining a separate logo bundle
email sources can use a browser fallback when a normal request times out
extracted locations can be geocoded and plotted on the map
Warning
only investigate identifiers you are legally authorized to process. requests are sent to third-party services and may be logged by those services. respect privacy law, site terms, rate limits, and consent requirements.
Live radio
the radio layer merges two complementary catalogs:
radio garden supplies place and channel context
radio-browser supplies broad station coverage, codecs, bitrates, tags, votes, and health signals
playback uses a guarded server proxy first, retries transient dns and redirect failures, then falls back to the resolved media url when the browser can connect directly. now-playing metadata is probed separately so icy metadata bytes never corrupt the audio stream.
Quick start
Requirements
node.js 20 or newer
npm 10 or newer
a modern browser with webgl enabled
network access to the public upstreams used by enabled layers
Install and run
open http://localhost:3000.
NO API key or environment variable is required by the current application. ignored .env files remain available for local extensions.
Production
Verification
Architecture
Repository Layout
API Groups
Source Model
Akashic does not own its upstream data. representative providers and registries include:
upstream availability and usage rights can change. operators are responsible for reviewing each provider's current terms, attribution rules, caching limits, and redistribution conditions before public deployment.
security
secrets and local environment files are ignored
radio urls are limited to public http and https targets
private, loopback, link-local, and internal dns results are blocked
every server-side radio redirect is revalidated
architecture deep scans are restricted to approved public hosts
recon requests are generated from repository-controlled source definitions
production dependencies are audited with npm audit
public deployment still requires normal perimeter controls such as rate limiting, request-size limits, observability, abuse handling, and a reverse proxy appropriate to the deployment environment.
Data and Performance
some static geographic datasets are intentionally committed because the browser or server reads them at runtime. large transient exports, build output, local caches, ai working memory, browser artifacts, and dependency directories are ignored.
live layers load independently. enabling every layer at once increases network traffic, map memory, and upstream pressure; use the layer controls to keep the workspace scoped to the investigation.
limitations
public feeds can disappear, rate-limit, redirect, or change schema without notice
radio stations can be offline even when a directory reports them as healthy
satellite and aircraft positions are estimates between source updates
3d coverage depends on the selected provider and location
building details vary sharply by open-data coverage
recon results can contain false positives and require human verification
curated strategic registries are context, not proof of current activity
the current lint baseline contains legacy findings even though type checking and production builds pass
contributing
keep integrations key-free when a reliable public source exists
preserve source attribution and terms metadata
distinguish live, cached, curated, simulated, and derived records in the ui
normalize upstream data at the server boundary
add focused verification for shared parsers, scoring, and source adapters
run npx tsc --noEmit, npm audit, and npm run build before opening a change
responsible use
Akashic is intended for lawful research, journalism, education, situational awareness, and development with public data. do not use it to harass, stalk, discriminate, bypass access controls, invade privacy, or target individuals or infrastructure.
license and attribution
Akashic is distributed under the gnu affero general public license version 3 or later.
gnu affero general public license version 3 or later
Parts of the strategic layer model, geographic registries, and related implementation were adapted from world monitor, copyright 2024-2026 elie habib, also licensed under the gnu affero general public license. the original copyright and license notice are retained in license.
third-party datasets, map tiles, feeds, and media remain subject to their respective licenses and terms.