Live, shared wormhole maps
Map the chain
together.
One live map for the whole corp. Signatures, mass, lifetime and everyone's position, in step for everybody looking at it. Run it on your own machine.
ESI-secure · No client install · Your database
home.map · Turnur
What this copy knows
Seeded from CCP's static data export on the first boot, and re-seeded when they publish a new one.
01 · Signatures
Scanning is copy and paste
Drop probe-scanner output in and the panel diffs it: new signatures appear, renamed ones keep their link, and a wormhole you have flown ties itself to the connection it opened. Nobody re-scans what the group already worked out.
Signatures 4
02 · Connections
Mass and lifetime that add up
Every jump is recorded against the hole it went through, with the ship that made it, so a connection knows what it has actually taken rather than what somebody remembered. Critical ones surface before anyone rolls into them.
Open source · Self-hosted
Run it yourself.
It is one command.
Not a trial of a hosted thing. The whole application, on your own machine, with your corp's chain in a database only you can reach.
The installer puts wsctl on the machine and offers to run the setup right away. Postgres, the API, the web server and TLS come up together under Docker. Certificates are issued on the first boot and the static data seeds itself. It asks for your domain and your EVE application, and works the rest out.
Your machine
One box, four containers, no account with anybody.
Your database
The chain lives in your Postgres. Nothing phones home.
Your keys
Your own EVE application, so ESI tokens never leave the host.
Checked before it asks for anything
- Docker is installed and running, on Compose v2
- there is disk for the static data
- the domain actually resolves to this machine
- ports 80 and 443 are free
- the checkout is not behind origin
And afterwards
- wsctl setup
- Checks the machine, asks for what it needs, brings the stack up.
- wsctl update
- Pulls, rebuilds, restarts, and takes newer static data when CCP has one.
- wsctl status
- What is running, which SDE build is loaded, whether the URL answers.
- wsctl doctor
- Checks Docker, disk, ports and DNS without changing anything.
- wsctl discord-register
- Uploads the slash command to your Discord application.
03 · Access
Decide exactly who sees what
Grant a character, a corporation or a whole alliance, at four levels, with an expiry if you want one. Or hand out a share link for somebody outside the map entirely, and withdraw it without touching anyone else.
Access · home.map
| Who | Kind | Role | Ends | |
|---|---|---|---|---|
 Nicolas Kion | character | Owner | — | |
 Strix Ridens. | alliance | Manager | — | |
 Strix Ridens | corporation | Member | — | |
 Tovan Khev | character | Viewer |
- Viewer Reads the chain: systems, connections, signatures and notes. Changes nothing.
- Member Everything a viewer does, and maps: systems, connections, signatures, intel.
- Manager Everything a member does, and runs the map: access, naming, alerts, settings.
- Owner Everything a manager does, and can delete the map.
04 · Everything else
The rest of living in a wormhole
Smart routing
The shortest way home through the chain and the gates together, weighted by security and by how much lifetime and mass you will trust.
Threat analysis
Recent kills surface against the systems they happened in, so you know what you are jumping into.
Discord alerts
Watch a system, a jump range, or the whole chain. Slash commands answer from the same map.
EVE Scout
Thera and Turnur connections pulled in and kept current, so routing can use them too.
Your own layout
Drag the panels where you want them. Phone, tablet, laptop and desktop each remember their own arrangement.
Undo anything
Every change is a command with an inverse, so a mis-pasted scan or a wrong signature is one keystroke back.
Your map, your database, your machine
Ready to map the void?
Nothing about your chain leaves the box you put it on. Read the code, run it, change it.