Case studies·Tools

Transistor.fm

Podcast hosting on Rails and AWS — two founders, open revenue

Justin Jackson and Jon Buda bootstrapped Transistor in 2018 on Ruby on Rails and AWS (Elastic Beanstalk), sharing revenue publicly via Baremetrics. They hit ~$20k MRR in 11 months — not five years — on boring SaaS infra and calm growth.

Jan–Aug 2018

$33 in February, launch on Product Hunt

$33 revenue (Feb 2018) · 46 paying customers / ~$1.4k MRR first month

Jackson and Buda each put $5k in via Stripe Atlas and built the MVP nights and weekends — Rails API, Postgres, AWS hosting. They committed to an August 1 launch publicly so Podnews would hold them accountable.

Launch day on Product Hunt brought ~46 paying customers and about $1,400 MRR — enough validation, not enough salary.

Lesson

Public launch dates are free accountability. Ship rails-on-AWS before you ship a platform roadmap.

2018–2019

$20k MRR in 11 months, not 60

~$20k MRR (~12 months post-launch) · ~$30k MRR (2019 Jackson blog)

They forecast five years to full-time income; compounding marketing + product work got them to ~$20k MRR in about a year. Jackson’s “$30k” post breaks down salaries: ~50% of revenue to founder pay, predictable MRR beat SV vanity metrics.

Mixergy and indie podcasts document the open Baremetrics dashboard from $0 upward — transparency as distribution, not just virtue signaling.

Lesson

Open revenue charts attract the customers who want you around next year. Boring recurring revenue beats exciting burn rates.

2020–today

Small team, Rails 7, still independent

$1M+ ARR passed (per Mixergy interview) · 4th anniversary blog (2022)

Ship It! #61 with Jon Buda describes infra upgrades — Rails 7, Ruby 3, Elastic Beanstalk platform bumps — done as a batch because they finally had breathing room after shipping podcast websites.

Transistor’s anniversary posts emphasize margin: emotional, financial, and operational. Still Rails on AWS, still bootstrapped, still saying no to complexity that makes founders hate their calendar.

Lesson

Upgrade the framework when maintenance debt hurts, not when Hacker News declares your stack dead.

Sources

Facts drawn from public engineering posts and interviews. Numbers are approximate where sources disagree — we're stack advisors, not historians.

Get the right stack for YOUR scale — not theirs

Transistor.fm's stack made sense for Transistor.fm. Yours won't — and copying theirs is how you end up with a $4k/month bill and three unused Kubernetes clusters.

Plan my stack — free