EveISR Lake

A local archive of EVE killmails as columnar files, with derived tags, the Static Data Export as a library, and a versioned query contract for tools to build on.

At a glance

Status: In development. Runs locally.
Platform: .NET 10 on Windows and Linux. DuckDB over Parquet.
For: Developers and analysts who build tools on kill data. It is not an end-user application.
Consumers: EveISR Intrep (web app and Discord bot)
Availability: Private. No hosted service and no public data download.

What it is

EveISR Lake holds the public killmail record as an archive that tools can query quickly on one machine. It is the only writer of the data. Everything that reads it, including EveISR Intrep, is a read-only consumer.

Killmail history as Parquet. In the maintainer’s lake as of October 2026: about 95.6 million killmails, 441 million attacker rows and 1.4 billion item rows, from December 2007 onwards. It is queried with DuckDB.
Derived tag tables. Each kill is labelled with attributes such as solo, awox, padding, capital, time zone, gang size and region. Tag definitions live in a table, and consumers look bit positions up there instead of hard-coding them.
An association layer that records which pilots were seen together, and operator overrides for corrections.
The EVE Static Data Export as a library. Download, verify, convert to SQLite and Parquet, update atomically, and look up names by key.
A loader that tails the live killmail feed and back-fills from published daily files.
A command-line tool, eveisr-lake, to load, tag, query and inspect the lake.

The query contract

Tools do not read the files directly. They call a versioned interface, ILakeQuery, that has three operations:

Status: what the lake holds and which data and tagger versions it is at.
Analyse: per-character summaries for up to 500 characters at once, plus an aggregate. A summary has kills, final blows and losses, trailing 30, 90 and 365-day windows, a 24-month activity series, top ships, and first and last seen.
Recent: one character’s kills and losses, paged.

Characters go in as ids, and ids with ship, system and region names from the SDE come out. The contract has its own version number, changes only additively within a version, and has no dependencies, so a tool references it instead of copying it. The same interface can later be answered by a hosted service without changing the tools that call it.

Where the data comes from

The lake is built from publicly published killmail data (zKillboard and R2Z2 day files, and ESI) and from the game’s published Static Data Export, within their published usage rules. Exigentec is not affiliated with zKillboard or with the game’s publisher.

Status and limits

It runs locally and is under active development. A hosted design exists on paper, but nothing is deployed.
There is no public query service and no public download of the data.
The interface is still in its 0.x versions and may change.

Independence

Exigentec’s EVE tools are independent third-party software. They are not made, endorsed or supported by CCP Games (now Fenris Creations). EVE Online, the EVE logo and all related marks and assets belong to their owner and are used here for identification only. “EveISR” describes what the tool is for and implies no affiliation with the game’s publisher.