From GitHubcommits since 1 MayEngine Room
Counted from our GitHub

Engine Room.

The studio's pulse, counted from GitHub. Every figure is exact. Hover, tap or drag any chart to read it, and the box at the bottom says how each number is counted.

01 / PULSE

The last 24 hours

Every bar and every spike is a real commit, in the 24 hours up to the time shown at the top. Press a bar, drag across the line, or replay the day.

Commits per hour

commits in the last hour, like a pulse rate

02 / GROWTH

How fast it is growing

The running total of commits, and each month on its own. Drag along the line or pick a month.

Running total
Commits per month

03 / RHYTHM

When the commits land

Every commit since 1 May by weekday and hour, London time. Darker means more. Tap a fact to light it up.

04 / EVERY DAY

The wall

One square per day since 1 May. Tap, hover or use the arrow keys to read a day.

05 / ANATOMY

What a commit looks like

What the changes are, and how big. Pick a type, or switch the lines between total and per commit.

Commit types

Lines changed
lines added
lines deleted

06 / SHIPPING

Pull requests and CI

How quickly work gets reviewed and merged, and whether the checks pass.

Median time to merge
min

from opening a pull request to merging it

Merged
Automatic checks (CI)
07 / HANDS

Who writes the commits

People and agents both commit, and we say which.

08 / RECORDS

The records

Biggest, busiest, longest. Tap a card to see how it is counted.

09 / METHOD

How we count

So you can check us.

What counts

  • Every commit saved to a main branch in our GitHub organisation since 1 May 2026, counted once. A commit that exists in two repositories counts once ( were duplicates).
  • Work in progress on branches counts when it is merged, not before.
  • Counts, not effort. A one-line fix and a month of work are each one commit.
  • Authors: people by name, AI agents (committer names starting "Claude"), and automation (sync jobs, dependency bots, CI). Separately, how many commits carry a Claude co-author line.
  • Never shown: repository names, commit messages, client work or anyone's name. Totals only.

Read the story behind these numbers

How it stays exact

1

A small service checks GitHub's own history for every repository in our organisation every minute, with a read-only login, and keeps no code, names or messages.

2

Each commit ID is counted once, even if two repositories hold it. The total is the number of distinct IDs.

3

Only totals and per-hour, per-day tallies are published. The page says how fresh the count is, shown as "as of" at the top.

4

Each full recount starts again from scratch, so a mistake cannot build up. In between, the live feed only adds new commits and pull requests.

5

If the live feed ever stops, the page falls back to the last full count and says when it was taken. We never add made-up increments to look busy.