Statistics tell you what.
Stories tell you why.

The story engine

Question it answers: what kind of project is this? Chapters — The Beginning, The Sprint, The Silence, The Grind, The Launch, The Evolution — derived from velocity, gaps and releases. "The project went quiet for 43 days" corresponds to 43 actual days between commits.

Repository time machine

Scrub or press play and watch the whole life unfold — commits, contributors, and the codebase itself appearing month by month, with milestone ticks on the timeline and a narration line explaining each moment.

Developer fingerprint

Whose fingerprints are on this codebase? The engine profiles the top contributor's rhythm — not their identity — into an archetype, with favorite hour, weekend share, and burst patterns.

The rhythm

Every repository has a pulse. When did the work actually happen — at 2 AM or in standup hours? Weekends? The rhythm section shows the honest answer in a punch card and an hour-by-hour profile.

Roast my git

For when the story needs a sense of humor. Every quip is generated with its evidence attached — a real commit, a real number, a real hour. If the data isn't funny, the roast doesn't fire.

Export studio

Your story shouldn't die in a browser tab. Every story carries a built-in export studio: share cards, animation, vector, README embeds and raw data — all rendered locally, nothing uploaded.

Single-pass analyzer

One git log subprocess for the whole history — roughly two seconds for a 30,000-commit repository, merge commits kept, no O(N) subprocess spawns.

Zero dependencies

Python 3.8+ standard library and git. That's the entire runtime. The claim is testable: the launcher has no package to install.

Privacy by architecture

The CLI never makes a network request. The output file never makes a network request. There is no backend, no database, and no telemetry — nothing to breach.