Listen Notes
Podcast search on boring Django, one founder
Wenbin Fang built Listen Notes — a podcast search engine and API — as a one-person company on Django, PostgreSQL, Redis, and Elasticsearch. It started on three DigitalOcean droplets for ~$30/month and grew without a platform cosplay phase.
Jan 2017
Three droplets, zero AI cosplay
Django
Python
PostgreSQL
Redis
Elasticsearch
DigitalOcean
Fang’s famous “boring technology” post is blunt: no AI, no deep learning, no blockchain — just a podcast search engine built with tools he already knew. In January 2017 Listen Notes ran on three DigitalOcean droplets costing roughly $30/month.
The MVP shipped Django on Ubuntu, PostgreSQL as the main store, Redis for caching and stats, Elasticsearch for search — uWSGI behind nginx, Celery for offline processing. No Docker, no Kubernetes: “as you gain experience, you know when not to over-engineer.”
Lesson
Your overthinking is a competitor’s opportunity. Ship with tools you’ve already paid the learning tax on.
2018–2019
AWS fleet, still one human
Django
PostgreSQL
Redis
Elasticsearch
AWS EC2
CloudFront
+1 more
By 2019 the stack had grown to roughly twenty AWS servers — web, API, DB, Elasticsearch cluster, workers, load balancer — named production-web1, production-db1, and so on for horizontal scaling. Fang provisioned everything with Ansible and deployed from a MacBook via a dead-simple shell script.
He still ran the company alone: Datadog + PagerDuty for alerts, Rollbar for Django exceptions, Slack webhooks pinging him when users signed up. The web frontend was React bundles on S3/CloudFront; the backend stayed monolithic Django.
Lesson
Horizontal scaling does not require microservices. Name your servers predictably and add production-web3 when press hits.
2020–today
Business ops, not engineering cosplay
Django monolith
PostgreSQL
Elasticsearch
AWS hosting
Ansible
Fang later clarified the famous post: “boring” meant familiar, not frozen. Engineering evolved, but most of his time went to email, partnerships, and thinking — not rewriting the stack because Hacker News discovered a new database.
Listen Notes remains proof that a podcast API business can run on a monolith plus search infrastructure, operated by one founder who optimizes for time back, not headcount.
Lesson
If 80% of your week is email and product calls, your stack is already doing its job. Upgrade when features hurt, not when Twitter says so.
Sources
- Listen Notes — The boring technology behind a one-person Internet company
- Hacker News — Listen Notes boring-tech thread (2024)
- Listen Notes — How I accidentally built a Podcast API business
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
Listen Notes's stack made sense for Listen Notes. 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