Opportunities › Technical wiki with live system integration › Proposed app
Gaugebook
Technical wiki whose runbooks show live system state
- Score
- 49
- confidence 57
- Evidence
- 5
- items on the page
- Rivals
- 2
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2004
- Mature market · AI estimate
ScreensConcept
Desktop app: DevOps teams read dense technical pages, edit runbooks, and track system state during extended incident response on a workstation. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
checkout-api
Page matches system99.92%
About this appAI proposal
Gaugebook is a technical wiki for engineering and DevOps teams. Pages for services, runbooks and incident responses embed live metrics and status pulled from the systems they describe, so a page shows what is true now, not what was true when someone last edited it.
Write a runbook step once and attach a read-only query to it. During an incident the step shows its current value next to the instruction, and flags it when the page and the system disagree. Responders stop switching between a wiki tab and a dashboard tab.
It is built for teams who keep docs in a general wiki and check dashboards by hand. Pages stay plain, editable text. Live blocks are read-only, so documentation never changes a system.
- Tagline
- Runbooks that read the system they describe.
- Voice
- PlainPreciseCalm
- Why this name
- A gauge shows the live state of a machine; a book holds the written procedure. Gaugebook joins the two: documentation with the readings on the page.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Live blocks in any page
Embed a metric, status or query result from a connected source. The block shows its value and last refresh time beside the text.
No member yet
Drift flags
Mark what a page claims, such as 'replicas: 3'. Gaugebook flags the page when the live system no longer matches the claim.
No member yet
Runbooks with checks
Each step can carry a read-only check, so responders see whether the expected state holds before they move on.
No member yet
Incident view
Open a page as an incident view: affected service, live readings, runbook steps and timestamped notes on one screen.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#F6F3ECPaper · surface#1E2A2BInk · text#1F6F6BDeep Teal · primary#E0702BSignal Orange · accent#3A5BA0Chart Blue · data#B3362FAlarm Red · incident status
Typography
Aa
Gaugebook
PricingAI proposal
Based on Notion's verified pricing page: two paid plans from €9.50 to €19.50 a month, a free plan, and prices on request. Dollar tiers and the self-hosted price are a starting point to test.
Free
Free
- Up to 5 users
- 10 live blocks
- One connected source
Team
$10 a month
- Per user
- Unlimited pages
- Unlimited live blocks
- Drift flags and stale report
Business
$20 a month
- Per user
- Incident view
- SSO
- Audit log
- Priority support
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$190,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Users invite others. A runbook is only useful when the whole on-call rotation can open it. Authors invite teammates and responders to view pages and join incidents, and each invite means someone uses the wiki.
- Do they become customers?
- Invited teammates are the same engineers who can buy for their team, so invites could convert. Test how many invited responders create their own workspace or upgrade within 60 days.
- First customers
- Platform and SRE leads at software companies of 20 to 100 engineers who run Prometheus and keep runbooks in Confluence or Notion.
- Where to reach them
- Open-source communities: Post worked examples of live runbooks in Prometheus and SRE forums, and in repo discussions of similar wikis.
- Direct outreach to SRE leads: Offer to convert one existing runbook to a live page in a 30-minute call.
- Incident write-ups: Publish sample incident views based on public postmortems, with live blocks shown.
- First milestone
- Five teams in one segment each using live runbooks in a real on-call week, and two paying after a 30-day trial.
Why people already pay for this
- VerifiedGitHub repository gained 402 stars in 85 days
- Public claimThe product is described as a technical wiki connected to the systems it describes, suggesting existing wikis do not provide this live system connection.
- Public claimThe repository targets incident response and runbook use cases, indicating these are known workflows that need better support.
- VerifiedNotion's pricing page lists 2 paid plans, from €9.50 to €19.50 a month, plus a free plan and prices on request for larger customers
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Metrics connectorsPrometheus-compatible HTTP query clientLive blocks need read-only queries against customers' metric sources.
- This app · MCP clientModel Context Protocol client libraryLets pages read status from tools that expose MCP servers.
RisksAI inference
- TechnicalCustomer metric sources sit behind private networks. A cloud wiki needs an agent or tunnel, which adds setup work and may block first trials.
- CommercialTeams may judge Confluence or Notion good enough and be reluctant to move their documentation to a new wiki.
- DataPages may expose sensitive metrics or hostnames to people who should not see them. Access rules per source are needed.
- PlatformObservability vendors could add similar notebook or runbook features to their own products.
- CommercialMarket evidence is thin: a GitHub star count and public claims. Paying demand for a separate wiki is unproven.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.