Mariwave

Your operations, live on one globe.

If you run fleets, networks or sites, Mariwave puts your feeds, files and agents on one globe drawn on your own computer, and we build the deployment around your data with you.

mari-atlas

Your feeds, on the live globe.

Every layer you need is drawn on your own graphics card, in the browser you already use.

  • mari-atlas draws the whole globe, with one engine written in Rust, compiled to WebAssembly and drawn through WebGPU on the computer in front of you, so the picture never waits on our servers.
  • Close up, it becomes a street map, with OpenStreetMap’s tiles and their credit on the map, and NASA’s satellite imagery with the clouds it observed that day.
  • Click anywhere to name the place, because 171,939 cities are searched on your own computer, and the exact point you clicked is what gets saved.
  • Your records stay with you, in the browser’s own database or in your agent’s database on your Mac, never in a vendor’s cloud.
The Earth from space as mari-atlas draws it, the Americas and the Atlantic in daylight, with country outlines and city lights on the night side
The globe behind this window is the same engine, running on your computer now.

Live Layers

Every feed carries its time.

You see what each source said and when it said it, side by side on one globe.

  • Weather comes from the forecast models themselves, NOAA’s GFS and ECMWF’s IFS, decoded on your own computer into wind, temperature and pressure at a quarter of a degree.
  • Events keep their own clocks, so earthquakes from USGS, tropical cyclones from NOAA and radar each show the time their source published.
  • A source that fails says so, in one Source status window, while every other layer keeps drawing.
  • You set the threshold and the units, US or metric, saved on your device, and the layer and its legend change together.
The live layers and their sources
Shown with it
Wind, temperature, pressureNOAA GFS, ECMWF IFSModel run and valid time
Satellite imageryNASA GIBS (VIIRS)Observation date
RadarRainViewerFrame time
EarthquakesUSGSEvent time, magnitude
Tropical cyclonesNOAAPosition time, class
AircraftOpenSky, adsb.lolObservation age, coverage
Satellites in orbitCelesTrakElement epoch
NewsYour RSS feedsPublisher, publish time

Traffic Corridors

Air traffic, drawn as it was seen.

Corridors come from aircraft that were actually observed, counted aircraft by aircraft.

  • Movement needs two sightings, so a corridor appears only where an aircraft was observed twice, from OpenSky with adsb.lol as the fallback.
  • Every aircraft is counted once, as distinct aircraft in the past 30 minutes, and you choose how many make a corridor worth drawing.
  • The US and the rest of the world are separate layers, each with its own threshold and its own collection delay shown beside it.
  • Satellites and launches share the globe, with orbits from CelesTrak computed on your computer and launch sites marked where they are.
How a corridor is drawn
  1. ObserveAircraft positions from OpenSky, or adsb.lol when it is unavailable
  2. PairTwo sightings of one aircraft give its movement
  3. GroupRust gathers movements along observed links
  4. CountThe database counts distinct aircraft in 30 minutes
  5. DrawDotted corridors on the GPU, above your threshold

Memory

Files you choose, read for people.

Your team finds who said what in every file, and the files stay where they are.

  • It reads the files your company runs on, Word, PowerPoint, Excel, PDF, email, CSV, HTML and RTF, in the folders you turn on and no others.
  • People, companies and decisions are pulled out, with spaCy’s language models, so a search finds who agreed to what and in which file.
  • Nothing is kept in our cloud, because each file is read in memory and only what it found comes back to your Mac.
  • It reads up to 20,000 pages a day on every plan, and a password-protected or macro-enabled file is turned away unread.
The files Memory reads, and how
Read as
PDFText page by page, with each page’s printed number
WordHeadings, paragraphs, tables and comments
PowerPointOne page a slide, with its notes
ExcelOne page a sheet, saved values only
EmailSubject and body, quoted replies taken out
CSV, Markdown, textThe text itself
HTML, RTFThe text, without scripts or styles

Client Vault

Each agent gets its own machine.

Your keys stay on your Mac, and each agent works on your data inside a boundary you set.

  • Each agent runs in its own Linux machine on your Mac, which sees only the folders you chose and reaches only the websites you allow by name.
  • Your keys stay outside it, since the agent holds a stand-in and your Mac adds the real key as each request leaves.
  • A key you mark high-value asks for Touch ID every time it is used, and every connection a machine makes is written to its own log.
  • You choose the agent, Mariwave’s own or one of five coding agents, and nothing goes to a client until you send it.
Where an agent works
  1. Your MacHolds your keysAdds the real key as each request leaves, and asks for Touch ID for a high-value key
  2. The agent’s machineA Linux machine of its ownSees only the folders you chose
  3. The websites you allowNamed one by oneEvery connection written to the machine’s log

Model Choice

Your models, on your own key.

The best-value model is picked for each job, on your Mac or in the cloud.

  • Models run on your Mac, on Apple silicon, for work that should stay in the building.
  • Cloud models bill your own OpenRouter key, so your spend and your providers are on your account, not ours.
  • Cloud requests go only to providers that keep nothing, because every request asks OpenRouter for providers that neither store prompts nor train on them.
  • Another model is one menu away, when a job needs a larger model or a different agent.
Where each model runs
HowBilled to
Your MacApple silicon, MLXYour plan
The cloudOpenRouter, providers that keep no promptsYour own OpenRouter key

Templates

A template built around your feeds.

We build the app your team opens each morning on mari-atlas, around your own data.

  • It starts from your feeds and files, your fleet, sites, sensors or orders, drawn as layers on the same globe.
  • Its words and data are checked files, each held to a schema we publish, so a change is a reviewed edit rather than new code.
  • Your Macs run it only as signed, because a template runs only when its files match a commit signed by Mariwave or by your own key.
  • It runs where your people work, in an agent’s machine on each Mac, with that machine’s folders, websites and keys as you set them.
How a custom deployment goes
  1. Your dataThe feeds and files your team works from
  2. A template on mari-atlasBuilt with you, its words and data in checked files
  3. SignedBy Mariwave, or by your own signing key
  4. On your MacsIn an agent’s machine, with the folders, websites and keys you set

Tell us what you run.

Tell us what your team runs and where it runs, and we’ll show you that data on the globe in a deployment built for you.

Ask for an invitation

Drag this handle or use the arrow keys to move the window. Shift moves farther. Escape cancels a drag.Download formacOS

Map: Natural Earth