Real numbers
Stats
Most companies hide their numbers. We publish ours. Some are zeros — that's the truth. Watch them grow honestly.
MRR
$0
Awaits first paying user.
Paying users
0
Awaits first paying user.
Free signups
0
Awaits signup form.
Affiliate revenue (mo)
$0
Awaits first booking.
AWS spend (mo)
$37.45
Auto-pulled from Cost Explorer. ⚠️ Above $25 alarm.
Days since start
8
From 2026-05-17.
Last updated: 2026-05-25 01:34:27 UTC · refreshes every deploy
What's auto-pulled vs hardcoded
Auto-pulled at every deploy: Days since start (date math from launch on 2026-05-17), AWS spend month-to-date (queried from AWS Cost Explorer for 2026-05-01 to 2026-05-26).
Hardcoded zero (because they really are zero): MRR, paying users, free signups, affiliate revenue. We'll wire each of these to a real data source when there's data to wire. First signup goes to a DynamoDB count. First paying user comes from Stripe / Paddle. First booking shows up in our LiteAPI dashboard. We won't fake any of these.
What's a $37.45/mo AWS bill on Day 8?
Mostly Route 53 hosted zone fees, CloudFront data transfer, Lambda invocations from us testing the API, and a small amount of CDK-deployed resources sitting idle. As real users start hitting the site, this number will go up; we'll publish that here too.
Why we're committing to public stats
Per the manifesto: we're tired of corporations hiding their economics while charging whatever they want.
Going.com doesn't publish their numbers. Hopper doesn't. Booking.com doesn't. So when they say "trusted by millions" or "best deals," you have no way to verify.
We publish the actual MRR, paying users, AWS spend, affiliate revenue, support tickets per 1000 free users, every number that matters. Including when they're embarrassingly small.
Pieter Levels (Nomad List, $3.6M ARR) does this. Buffer ($21M ARR) does this. Plausible Analytics does this. They built trust by showing the work. We're doing the same in our niche.
What we'll never hide
- Total revenue and revenue by source (affiliate vs Pro vs B2B)
- AWS, tooling, and infrastructure costs
- Net margin (revenue minus costs)
- Free user count, paying user count, churn
- Support ticket volume and response times
- What we earn from each affiliate booking (per-result disclosure)
- Our mistakes, when something breaks, postmortems
What we will hide
- Individual customer data (PII)
- Active security vulnerabilities (until patched)
- Active legal disputes (could prejudice outcome)
- Pre-signed unannounced partnership terms
That's the line: transparent about us, never about customers.