Kaeda
Free · Sourced
← All cases
Prerender.io
Dev tool · JavaScript SEO · Solo-built · USA
👤 Todd Hooper (Solo dev hit his own JS-SEO wall, fixed it in a weekend, open-sourced it (24k visits day one), then charged from day one.)🌐 siteLinkedIn

A solo dev turned a weekend hack into a prerendering service serving 100k+ sites and 2.7B+ pages to crawlers.

Will it work? · our read
Charged day one. A real, urgent problem and a trivial one-line fix built a $2.5M solo business. But infra ran thin and SSR frameworks keep eroding the reason to exist.
01How the money moves
A JavaScript site is invisible to Google's crawler
Add one line; Prerender serves crawlers static HTML
Pay per render, monthly — profitable from day one
02The numbers
$2.5M
ARR at exit
founder
100k+
businesses served
saas.group
2.7B+
pages to crawlers
prerender.io
Solo-built to $2M ARR before the founder's brother joined. saas.group teardown
$2.5M ARR at exit — founder-stated in a Starter Story interview and echoed by acquirer saas.group.
03Weight class — CENTStap an axis
ControlEntryNeedTimeScale
Control Mid
His hosted service and brand, but the core engine is open-source — anyone can self-host or clone it.
04The key move
Host the pain
He open-sourced the prerender code — 24,000 visitors day one, free marketing. Then he sold the hosted version, because running headless browsers at scale is a nightmare most teams gladly pay to avoid.
fact
The counter-intuitive move
Giving away the code means anyone can self-host and skip him — and Google's Rendertron was free. It held because reliable infra at 2.7B pages is the real product.
our read
05Where the moat is
The moat isn't code — it's ops and reach.
One-line install, near-zero switching frictionRuns the headless-browser infra you don't wantOpen-source repo as top-of-funnel magnetCaching scale across 100k+ sites
06How it diesmedium confidence
The dead twin: a prerender shop whose infra bill eats its margin while the ecosystem fixes the root cause. Google downgraded dynamic rendering; Next.js/Nuxt SSR make prerendering pointless for new apps. our read
Show evidence · counter
Evidence: Google archived its free Rendertron (Oct 2022) and stopped pushing dynamic rendering as a long-term fix; SSR is now the default for new JS apps.
Counter: AI crawlers (GPTBot, ClaudeBot) revived demand for the same prerendered HTML, and legacy SPAs won't be rewritten — a long tail keeps paying.
07Against rivals
Prerender.io$49+/mo
Next.js/Nuxt SSRFree (built in)
Google RendertronFree, archived
SEO4Ajax/BromboneLow-cost
The real threat isn't a cheaper clone — it's SSR frameworks removing the need. our read
08Who uses it
Angular/React/Vue SPA teamsJS-heavy ecommerce storesSEO agencies fixing client sitesEnterprises: Walmart, Spotify, Netlify
Would it work for you?
Would you give away the code and sell only the annoying ops around it?
You build cheap and ship dev tools. Ask if the moat is the code or the ops nobody wants to run. We don't score you — you answer.
🚀Use it as a launchpada prompt for your own AI
Copy → paste into your AI → then develop it freely in the conversation.
You are a sharp, honest startup strategist. Use the proven case below as a launchpad for MY idea — help me find my own angle, not copy it. <my_profile> Domain I know: [your domain] My unfair advantage (access/audience): [your edge] Interests: [your interests] Resources & goal: [your resources] · [your goal] </my_profile> <case name="Prerender.io" model="devtool"> What it does: A hosted service that pre-renders JavaScript sites into crawler-readable HTML, billed per render. Why it won (moat): One-line setup plus the operational pain of running headless browsers at scale for 100k+ sites. Weakest axis (CENTS): Low entry barrier and thin margins — free tools exist and infra ate about 40% of revenue. How it could die: SSR frameworks (Next.js/Nuxt) make prerendering unnecessary for new apps. </case> <task> Be a skeptical operator, not a cheerleader. No generic startup platitudes. If my angle is weak, say so plainly. First, a reality check: markets like this mostly fail. State the honest base rate (how crowded/hard is this?) and the ONE specific thing that would have to be true for ME to be the exception — grounded in my profile above. Then a compact table: - Fit — does this pattern suit my edge, or fight my gap? - Angle — my sharpest differentiation vs Prerender.io (concrete, not "better UX") - Distribution — exactly where my first 100 users come from (this is the hardest part — be specific, not "content marketing") - Risk — its "how it dies" (above) in MY situation Finish with one line: "The single thing to do next." Use only the facts above; if data is thin, say so — never invent numbers. Then stay with me and go deeper on whatever I ask — tech stack, rough cost & time, the smallest MVP to test, pricing, or timing. </task>
✓ Copied — paste into your AI
👤Placeholders like [your domain] auto-fill from your profile — example values for now.Set up profile →
Sourcesupdated · daily
Revenue is founder-stated (STATED, not a filing): Todd Hooper cited about $2.5M ARR / roughly $220k/mo in a Starter Story interview, and acquirer saas.group independently repeats "about $2.5M ARR" and "100k+ businesses" — first-party plus acquirer corroboration, so independently confirmed. The 2.7B+ pages figure is Prerender.io's own marketing. Dates are fuzzy: founding is 2013 or 2014 across sources, and the saas.group acquisition year conflicts (2018/2020/2022 cited), so I state no acquisition year. Region USA is the likely base (US-focused indie SaaS) but not filing-confirmed. On the SOURCE ANGLE: I searched Inc 5000 / Deloitte Fast 500 / regional lists but Prerender.io is not a listed honoree — I chose it anyway because it clears the higher bar the honesty gate prioritizes (first-party disclosed revenue) over the discovery well; a strong awards-fit alternative (Contractor Foreman) had no disclosed revenue and no confirmed award. The infra-margin point (about $1M/yr infra, cut 80% post-acquisition) and the SSR-obsolescence thesis are documented (saas.group blog; Google archiving Rendertron, Oct 2022). Both keyMove.counter and the 40%-of-revenue infra read are labeled our read/inference. We never score you.