StarStats is a fan-built, local-first event tracker and manifest archive for Star Citizen players. It pairs with the game, parses your raw log files on your own machine, and turns them into a clean, exportable session-by-session record you actually own.
Every session, the game writes a log. StarStats reads it, sorts it, and gives you back a logbook — kills, deaths, cargo, contracts, jumps, ships flown, time on station — without uploading anything you didn't ask it to upload. Your manifest lives on your drive. Sync is opt-in. Export is always available, in NDJSON, ZIP, or CSV, so you can leave whenever you want.
It does one job and tries to do it well. Pairing, parsing, viewing, and exporting are free — and will always be. There's a supporter tier with cosmetic recognition and longer retention, but no part of the core utility sits behind a paywall.
StarStats is a community project. Contributions, bug reports, and pull requests are welcome on the project's source repository.
The names, manufacturers, roles, and sizes that StarStats uses to turn opaque engine identifiers like AEGS_Avenger_Stalker into "Aegis Avenger Stalker" come from the community-run Star Citizen Wiki — a volunteer effort maintained by the StarCitizenTools team and the wider editor community.
Attribution. Wiki content is © Star Citizen Wiki contributors and licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0). The credit on this page, in the footer of every signed-in surface, in the per-entry "View on Star Citizen Wiki" link on each Knowledge Base detail page, and in NOTICE exists so that attribution travels with the data.
Modifications. StarStats does not republish the wiki dataset verbatim. We strip internal bookkeeping fields (id, created_at, updated_at, version), restructure per-category extras into a single JSONB metadata column, and join each entry to the engine class identifier that appears in your Game.log so the catalogue can be looked up by class name. Entries that lack a usable class identifier are dropped because they can't link back to a game event. The redistributed portion (the public /v1/reference/* API and the /kb Knowledge Base pages) is offered under the same CC BY-SA 4.0 terms.
No warranty. The wiki is community-edited and may be incomplete, out of date, or wrong about a given entity; StarStats passes the data through without warranties of accuracy, completeness, or fitness for purpose. If something looks off, the canonical place to fix it is upstream on the wiki itself.
How we fetch. A scheduled task on the StarStats server fetches the public API (api.star-citizen.wiki) once a day with a generic user agent and no user data attached. The catalogue is cached server-side and joined to your events at render time — your browser never talks to the wiki directly.
StarStats is not affiliated with the StarCitizenTools team or the Star Citizen Wiki. If you maintain the wiki or its API and want the integration adjusted — the attribution amended, the request shape changed, the deep-link convention changed — open an issue on the StarStats repository and we'll work it out before the next release.
Ship specifications & imagery. For vehicles, the spec sheets, flavour descriptions, and ship images shown on Knowledge Base pages are enriched directly from Roberts Space Industries' official Ship Matrix. Those specifications, descriptions, and images are © Cloud Imperium Rights LLC / Cloud Imperium Rights Ltd and are shown here as unofficial fan reference, not endorsed by or affiliated with Cloud Imperium Games or Roberts Space Industries. Each vehicle page carries this notice inline, and we honour removal or adjustment requests — see the disclaimer in §04 below.
StarStats is a fan-built site and desktop tool, not a derivative work, mod, or replacement of any game. It is published as fan fiction and fan tooling under the spirit of Cloud Imperium's published fandom guidelines. The text below appears verbatim wherever it is required.
We try to read CIG's fandom guidelines conservatively. If you want to confirm what they actually allow — and where StarStats sits within those boundaries — these are the source documents we work from.