My startup
Firstage Estimations
A desktop app where a team sizes its Jira work together with Poll and Bidding rounds, then records the agreed estimate in Jira.
- Period
- 2026.10 ~ Present
- Organization
- Firstage
- Role
- Planning and development
- Key features
- The room runs on the computer of the person who opens it, and players join from a browser through a link. Firstage runs no server for it.
- Work and results
- Rooms run on the host's computer, with no Firstage server
- Agreed estimates reach Jira only after a person confirms them
- Company settings shared as a JSON file that holds no secrets
- Signed and notarized internal test build
- Tech stack
- Tauri
- React
- TypeScript
- Node.js
- Jira
Context
My personal toy project, the AI-kit estimation room, ran its rooms on a server. In October 2026 I redesigned it as a Firstage desktop app. Every company has its own Jira site and network, so the starting point was keeping rooms and Jira credentials on the computer of the person who opens the room.
Decisions and implementation
- A room runs on the computer of the person who opens it. The app listens only on 127.0.0.1 and admits players through an address the company points at it with its own tunnel or proxy, plus a room key that cannot be guessed. Players join from a browser through a link.
- Poll and Bidding results are frozen and reviewed together, and an agreed estimate is written to Jira only when a person confirms it. Sprints and candidate issues are read from Jira automatically.
- Each company’s Jira site, field mapping, and teams are shared as a JSON settings file that holds no secrets, while each person’s token stays in their own keychain. Nothing company-specific is compiled into the build.
Current status
The signed and notarized internal test build passes entry through a public address, a five-minute idle period, and automatic recovery after the app restarts. Reading and writing a real company’s Jira and public distribution are still ahead. The first public release is planned as a free beta.