Enterprise-grade developer operating system
Make every engineering signal visible, playable, and impossible to ignore.
Rook converts GitHub activity into a live command layer for engineering orgs: quests, progression, loot, guild incentives, realtime feeds, and self-hosted control. It feels playful on the surface and brutally operational underneath.
- Self-hostable backend
- Realtime Socket.io feed
- GitHub-native onboarding
- Dedicated docs at docs.rookapp.dev
Live command stream
rookapp.dev/control
Rook command console
rook leaderboard --watch
Operational surfaces
Separate the narrative layer, the operator layer, and the integration contract.
rookapp.dev
High-conviction positioning, product framing, and launch-grade entry points for buyers, operators, and contributors.
Stay on the root sitedocs.rookapp.dev
Direct Mintlify delivery for guides, quickstart, API reference, and structured operator documentation without path-prefix fragility.
Open documentationGitHub as source of truth
The docs and product narrative now both point back to the same repository, so updates are traceable, reviewable, and ready for automatic deploys.
Review the codebaseWhy teams adopt Rook
Not another dashboard. A pressure-tested ritual layer for shipping teams.
Progress With Consequences
Commits, PRs, reviews, and issue closures resolve into XP, streaks, quests, loot, and prestige. Teams stop guessing whether momentum is healthy.
Realtime Team Theater
Watch rank shifts, drops, crafts, and PR battles stream into the terminal. It turns passive metrics into an active operating loop.
Self-Hosted Control
Express, PostgreSQL, Socket.io, and Mintlify docs make the system inspectable, customizable, and easy to fit into regulated engineering environments.
Behavior Design, Not Vanity Metrics
Daily boards, weekly bosses, guild incentives, and crafting perks create the right kind of pressure: visible, compounding, and difficult to ignore.
Control room
Move between experience, infrastructure, and governance without losing the plot.
Game design with operational outcomes
The surface area is deliberately expressive: progression curves, quest streak bonuses, crafting loops, and guild incentives combine into a developer-facing experience that feels fast, personal, and legible.
- CLI-first interactions keep the feedback loop inside the toolchain engineers already live in.
- Reward design creates habits around reviews, merges, and consistent throughput.
- Realtime outputs make team motion emotionally legible, not just analytically available.
experience.map
Statshero sheet, streaks, loot, guilds, prestige
Dungeondaily quests, weekly bosses, PR battles
Leaderboardfriends, global, watch mode
Craftingrecipes, perks, rarity upgrades
Simple topology, high leverage
Rook is intentionally compact: Commander on the CLI, Express and Socket.io on the backend, PostgreSQL for state, and Mintlify for docs. That simplicity is why it can move fast without turning into operational mush.
- GitHub webhook ingestion awards XP and advances quests automatically.
- Socket.io keeps watch-mode sessions alive with meaningful events instead of noisy polling.
- Cloud Run deployment keeps ops lightweight while still providing production discipline.
runtime.topology
GitHub events
Rook API
PostgreSQL + Socket.io
CLI + Docs
Enterprise posture without killing the energy
The right framing for Rook is not “fun CLI” versus “serious platform.” It is an engineering operating layer that happens to understand motivation, visibility, and team psychology.
- Inspectable self-hosting path for teams that need control over data boundaries.
- Explicit API reference and route inventory for internal review and platform integration.
- A docs surface designed for onboarding contributors, operators, and buyers without ambiguity.
governance.snapshot
Auditabilityopen repo, explicit docs, route-level visibility
DeployabilityCloud Run friendly, domain-ready, minimal moving pieces
Extensibilitynotifications, guilds, API surface, custom reward loops
Ship the product
Marketing site, docs, and infrastructure now align around the same object.
Root site for narrative. docs.rookapp.dev for operator truth. Cloud Run at the edge of the
launch surface. Mintlify for the knowledge system. The split is cleaner and more resilient.
Immediate actions
FAQ
Questions the platform should answer cleanly.
What is Rook actually for?
Rook is for teams who want engineering momentum to feel visible and actionable. It turns GitHub activity into progression, rituals, and team-level incentives without requiring a heavyweight dashboard-first rollout.
Can it be self-hosted?
Yes. The backend is Express, PostgreSQL, and Socket.io. The docs are Mintlify-based. The current delivery
model uses rookapp.dev for product narrative and docs.rookapp.dev for the
documentation system.
Does it expose an API?
Yes. The docs include a much broader OpenAPI definition covering users, quests, leaderboards, crafting, guilds, notifications, and webhook flows.
What is the domain situation?
rookapp.dev is the production domain on Google Cloud, with docs.rookapp.dev
reserved as the direct docs surface. Legacy /docs routes on the root site are redirected to
the docs hostname.