✻Standing datalink · New Eden
EDENCOM’s real achievement was never the Vorton projector. It was getting four empires that had spent a millennium shooting at each other to read one threat picture and trust it. Your eleven alts have the same problem. This is their datalink.
Read-only ESI access · you choose the scopes
The feed
Most capsuleers run their holdings on spreadsheets, screenshots, and a Discord bot that died two patches ago — every source partly right, none agreeing. This is the same data, pulled straight from ESI, in one place that agrees with itself.
Wallet
Every character’s wallet in one ledger, next to your corporation’s division wallets. Journal entries roll up by reference type, so you can see what the ISK actually was — bounties, taxes, escrow — instead of scrolling a thousand lines.
Inventory
Every item in every station, ship, and nested container, searchable, with stack counts and location drill-down. Nothing is overwritten, so “what did I hold before that downtime” is a question with an answer.
Industry
Industry jobs, blueprints with their ME and TE levels, and job slots counted from what your characters have actually trained. System cost indices and the rigs fitted to your structures are part of the same picture.
Market
Open orders and full transaction history, across characters and corp divisions. What filled, what expired, and what it cleared at — without logging in eleven times to find out.
Structures
Fuel runway, service modules, fitted rigs, and reinforcement state for every Upwell structure. Industry-tax revenue is broken out per structure per day, so you know which citadel is earning its fuel blocks.
Clones
Jump clones and where they’re parked, implant loadouts, and jump-timer availability, across every character. Skill training history rides along, so who trained what, and when, is on record.
Mercenary dens
Your dens with development and anarchy levels, reinforcement timers, and a map of what sits around them. Intel sharing is opt-in and scoped to exactly one alliance — no further.
Analytics
CSV feeds built for Google Sheets =IMPORTDATA(), keyed to a personal token. The asset, order, industry and blueprint feeds each answer for a past date, so your spreadsheet time-travels with the database.
Blueprints
Name an item; it resolves the blueprint that builds it and prices the material bill against runs, ME, your structure’s role bonus, its fitted ME rig, and system security — a rig counts only where it actually covers that product. You reach it by asking an AI assistant in plain language, over an OAuth-authorized MCP server scoped to exactly your own data.
The doctrine
Every asset, order, job, and blueprint is versioned: a change closes the old row and opens a new one. “When did that stack move?” is a query, not an argument.
Row-level security scopes every read to your own account, and access is granted one ESI scope at a time. Shares are deliberately narrow: one ship, one alliance’s intel, one public page.
The site holds no write permission against your account and never asks for one. It can tell you what you own; it cannot touch it. It is a receiver, not a transmitter.
Standing up the link
Link a character
Sign in through EVE SSO and grant scopes one at a time. Anything you skip simply stays dark — the site works with whatever you choose to feed it.
Let the pipelines run
Scheduled jobs pull every endpoint on their own clock and keep every version. Backfill is automatic; there is nothing to import, export, or paste by hand.
Read the picture
Browse it, wire a spreadsheet to a CSV feed, hand out a share link scoped to exactly one thing, or point an AI assistant at your data and start asking questions.
“It knows where everything is — every hangar, every can, every wallet division. Including the corpses. It knew the corpses by name.”
— a nullsec logistics director, who asked not to be identified
Add a character and you’re about a minute from a single picture of everything you own.