Case studyLiveMIT licensed

Story Points

Realtime pointing poker for agile teams

Built after routine disappointment with pointing tools that did the job but often felt dated and disposable. One standing URL per room, no accounts, nothing to install, and enough memory to come back next sprint.

Story Points room with cards ready to vote
~20 KB
gzipped JavaScript
6
languages
29
themes
$0
to run, on the Workers free plan

Role

Product, design, and engineering

Built with

  • Lit
  • Cloudflare Workers
  • Durable Objects
  • WebSockets

The problem

Story Points came from routine disappointment with the pointing tools I used in real sprint planning. Tools such as PointingPoker.com could run the vote, but the experience often felt dated, temporary, and disconnected from the rest of the team's work.

Many alternatives also ask for something before the first vote: an account for the facilitator, a seat for everyone, or a paid tier once the team grows past a cap. The free ones tend to forget everything when the session ends, so the deck, settings, and history are gone by the next sprint.

The goal was the opposite: a room that is just a URL, costs nothing to open, and is still waiting, with its history, when the team comes back.

Decisions that shaped it

The URL is the product
Create a room or claim any address like /room/your-team, share the link, and everyone joins with a name. The same URL works sprint after sprint, and refreshing the page reclaims your seat. An optional six-character room code is the only lock.
No accounts, including API keys
Auth machinery is accounts by the back door: key issuance, rotation, revocation, a dashboard. So the credential is scoped to one room and shared the way the room is shared. That is also what makes "point your own agent at the API" a one-click idea instead of a setup ceremony.
Identifiers are capabilities
A user id reclaims a seat, so it never leaves the server. Broadcasts carry per-room opaque aliases, votes stay server-side until reveal, and the stats endpoint returns aggregate integers only. Every new field on a public payload gets the same question: is this someone else's credential, or state that is hidden on purpose?
Dependencies must earn their place
Animations are pure CSS and sounds are Web Audio, with no assets. The runtime roster is Lit plus a lazy-loaded 2 KB QR encoder that only downloads if you open the invite QR.

What's inside

Ticket queue
Fill it by typing, pasting a tracker export, importing a Linear or Jira CSV into a preview table you can edit first, or posting from a script.
Round history
Each round records the story, vote spread, and time to reveal. Copy it out as Markdown or CSV, or download JSON.
Voting modes
Auto-reveal, a server-owned countdown, anonymous voting, away votes, custom decks and groups, and optional room codes.
A joy layer
Emoji reactions that ride the socket and are never stored, shuffle-bag celebrations on reveal, a rabbit-hole timer that warns you when a story drags, and a hidden trigger word.
Themes and languages
Twenty-nine themes including seasonal auto-theming, and a UI in English, Spanish, German, French, Portuguese, and Japanese from a zero-dependency translation layer.
Built for agents
A plain-HTTP API for import and export, an llms.txt index, markdown twins of every docs page, and per-agent setup notes.

Under the hood

The frontend is Vite and Lit web components. The backend is a Cloudflare Worker with one Durable Object per room, using the WebSocket Hibernation API so idle rooms cost nothing. Room state persists in the object's SQLite storage for weeks between sessions, and a singleton stats object keeps anonymous aggregate counters.

Because rooms are Durable Objects, self-hosting means your own Cloudflare account. Three commands (clone, install, deploy) put an identical copy there on the free plan, and nothing phones home. The license removes the ability for there to be a catch.

Contribute

Locale files are the easiest way in: one file, one pull request, and the file headers invite native-speaker review. Bug reports, theme ideas, and docs fixes are welcome on the repo too.