Interactive map — drag systems, draw connections, set wormhole class/type/status per connection. Snap-to-grid, optional minimap.
Wormhole intel — per-connection mass tracker (≤10% / ≤50% / critical), end-of-life flag with countdown, K162-aware static identification, frig-hole and gas-site auto-tagging from sig type.
Wormhole type picker — searchable popover for assigning the exact wormhole type to a connection; statics quick-info on hover shows destination class, mass, lifetime.
Multi-select bulk operations — shift-click to select multiple systems/signatures, then bulk-assign type, delete, or rename.
PNG export — render the current map (with sig counts, connections, status) to a PNG for sharing.
Map PNG / clipboard — copy or download the current chain as an image for pings.
Personal & corp maps
Solo / Corp split — every user has personal maps that are always private; in corp mode each corp also gets shared corp maps. Cross-corp visibility is opt-in via CORP_MAP_SHARED.
Multi-map support — each character (or corp) can maintain multiple independent maps up to configured limits (MAX_USER_MAPS / MAX_CORP_MAPS).
Map locking — admins can freeze a corp map’s topology. Systems, connections, and the map name lock for non-admins, but signatures, structures, and per-system notes stay editable so ops can continue while the layout is pinned. The toolbar shows an amber chip while the lock is active, and passive location tracking won’t auto-add new systems on a locked map.
Role-based access — admin / full / edit / readonly. Roles only restrict corp-map actions; every user owns their personal maps regardless of role.
System intelligence
System panel — per-system cards for signatures, structures, NPC stations, notes, killboard, and activity charts; cards are reorderable via drag-and-drop and persist per-user.
Signature management — paste EVE scan results directly; tracks created/updated age per signature; auto-deletes sigs missing from a re-paste; bulk type assignment for multi-select.
Structure import — paste EVE overview data to import player-owned structures.
Activity charts — 24-hour rolling history of jumps, ship/pod kills, and NPC kills, polled from ESI hourly.
Sovereignty & station data — live alliance/corp/faction sov info and NPC station services with in-game waypoint/destination actions.
Killboard pane — recent zKillboard activity per system; recent kills also bubble up as highlights on the map.
Chain effect summary — at-a-glance view of all wormhole effects currently present in the chain.
Live ops
Scout connections — Thera and Turnur public Eve-Scout connections surfaced into the sidebar so you can jump straight to known holes.
A0 sun detection — auto-flags systems with A0 (yellow) suns visible via ESI for capital-friendly skirmish planning.
Proximity alerts — incursions and pirate insurgencies appear as a toolbar chip showing the closest threat in jumps; configurable threshold with browser notification + beep on entry/exit.
Route planner — server-side BFS over stargates + your live chain, so a route through a wormhole hop is a single click.
Location tracking — opt-in live character location dot in the toolbar plus per-map “you are here” indicator.
Online status — toolbar dot shows whether each user is currently logged into EVE Online.
Productivity & UX
Command palette — Cmd/Ctrl + K opens a fuzzy search across systems, sigs, and actions (jump to system, set waypoint, toggle panes).
Home hotkey — jump the viewport back to the home system from any panel.
Recent-kill highlights — systems with kills in the last hour get a coloured halo so you can see fresh activity at a glance.
User stats modal — per-character totals: jumps, signatures by type, broken down by day/week/month/year/forever.
Server status widget — live Tranquility server status, player count, and ESI health in the toolbar.
Demo map — the landing page mounts a non-editable demo map so visitors can see what the tool does before logging in.
Collapsible sidebar — Map Options, Connections, Proximity Alerts, Stale System Fade, and Shortcuts each expand or collapse independently. State persists per browser.
European date format — DD-MM-YYYY everywhere a date is displayed; ISO timestamps in CSV exports for spreadsheet sortability.
For corporations
Multi-corp deployments — CORP_ID accepts a comma-separated list of corporation IDs. One instance can host several corps; each corp’s maps stay scoped to its own members unless CORP_MAP_SHARED=true.
Admin dashboard — a dedicated #/admin page with four tabs: Users, Maps, Reports, Audit log.
User management — change roles, block / unblock, and force an ESI corp-membership re-check on demand. Anyone who has left every listed corp is auto-blocked on next login.
Map management — admins see every corp map with owner avatar, corp ticker, system / connection counts, lock state, and last-active time. Force-lock, force-unlock, and force-delete are one-click each.
Users report — per-character last-login, systems added / deleted, structures added, signatures broken down by type. Filterable by activity and time window, exportable as CSV.
Systems report — aggregate corp-map signatures with a sig-type donut, daily / monthly activity line chart, and a sortable wormhole-type breakdown.
Audit log — every admin action recorded with actor, target, old → new value, and timestamp. Exportable as CSV.
Corp ticker resolution — corp IDs resolved to in-game tickers via ESI, with a 1-hour in-memory cache.
Per-character attribution — sigs, structures, and system add / delete actions recorded with the user who made them, so reports can answer “who has been scanning what” with no manual logging.
It’s open source so you’re free to host it yourself or contribute to it (Github).
Also, if you want a feature, literally ping me. I’d prefer to have something in there that helps someone
Yep, I can definitely do the size element to this. It was slightly bugging me as well!
I’ll push this out later today. I’ve made a few tweaks to the system nodes as we appear to have a lot of info in icons so cleaning them up.
I’ll add a toggle for tracking you known location. That way you can decide when you want to track
Toggling this on and off will prevent Nexum from adding systems as you move through them
Added new options to the menu options. Uniform size will attempt to make all System nodes the same height and width. There’s exceptions as some systems are up to 18 characters so we ignore these (otherwise all nodes would be huge!)
I’ve now added Storm Information. In the case above, hovering over the lightning bolt would show the type and other meta data. There is no official Eve data source for this so I obtain it from eve-scout
Ice data has also now should on the system nodes. i.e. If the system can spawn ice, we show it. NOTE: We do not keep track of anoms therefore it is a ‘known ice system’ rather than a system that has an active anom
I am unsure what I did, but I have two of the same wormhole entry on my map.
If I can figure out why that happened I’ll add steps to reproduce, but I suspect it’s because I have the browser tab open twice with both tabs set to track.
Edit: Is there a way to label systems in a way that shows up on the boxes themselves and not in, say, the notes panel?
I would also like to be able to save my bottom panel layout and have it used as the default for every system when I customize one.
Restricts logins to specific EVE corporations. Comma-separated list of corporation IDs — anyone whose corp is not in the list is rejected at the OAuth callback. Leave empty/unset to allow any EVE character to log in. Example single corp: 98000001. Example multi-corp: 98000001,98000002.
ADMIN_CHAR_ID
When CORP_ID is set
EVE character ID of the bootstrap admin. Forced to the admin role on first login and cannot be demoted or blocked by other admins. Not a corp-membership exemption — this character still has to be in one of the corps listed in CORP_ID to log in. See What happens when a user leaves the corp.
CORP_MAP_SHARED
'‘booleaon true/false’
So for example, If this was me I’d set the following
Easiest way to get the ID’s is use zKill as they appear in the URL for the relevant entity
There’s a couple of optional corp variables as well being
CORP_MAP_TIME - Days an idle corp map can sit untouched before it’s auto-archived. Default 30.
MAX_CORP_MAPS - Max number of corp maps per corp. Default 5.
Full details are also in Codeberg but let me know if you have any issues
The hosted version doesn’t support corporation maps. It’s purely as I’d have to then maintain all corps and their admin users which is unviable.
For corp maps, you have to host this yourself.
I’ll be adding a feature to share a map later next week but I’m not sure how viable it is to share with a whole corp rather than just another set of pilots.
This should be fixed. There were a few edge cases where you might actually want systems on twice but I fear it was happening more often than it should be so now I’ve set it so there are no duplicates allows.
I’ll be introducing the concept of labels on a build, likely next week. You’ll be able to add a label such as ‘Safe’, ‘Hostile’ etc and also add your own custom labels.
Thats actually a bug so I’ll look into that. It should be saving the bottom panel (and all of them really) between sessions and maps
This is now saved to the server. Previously, I was just storing it locally. The panel order is saved and it’s not done on a per system basis (i.e. it’s set the same for each one)
You can now share maps without the other person having to sign in. You can configure what you display in regard to toggling Jump gates to be visible/invisible, signatures, structures and system notes are also all toggle-able .
This latest update might actually help you here.
You can create a map as any character and then share it to either individual pilots or to corporations as a whole. Anyone who has access to the shared map can update systems, add systems etc but they cannot re-share or use live map.
Another update today. Useful for people scanning in k-space
Ability to create maps that are pre-populated with the systems in a region. For example, if you wanted a map of Catch, you don’t need to manually do it. Tried to keep the layout as close to Dotlan as possible.
Ability to merge maps together. Useful if you’ve a personal map and you want to merge the sigs into a corp map or shared map
Tagging. Systems can now be tagged with a status. Users can either pick a predefined status or add their own
chip while the lock is active, and passive location tracking won’t auto-add new systems on a locked map.
