Pinboard
Paid bookmarks on PHP, MySQL, and five boring servers
Maciej Cegłowski built Pinboard as the anti-social bookmarking site: pay to join, fast pages, no engagement bait. It runs on a classic LAMP-ish stack he wrote himself — and famously stayed small enough for one person to operate.
2009–2010
Spreadsheet-era Delicious grief, slicehost MVP
PHP
MySQL
Perl cron/screen scripts
Single VPS (Slicehost)
After Yahoo mangled Delicious, Cegłowski shipped Pinboard as a plain PHP app on MySQL with Perl handling feeds, backups, and batch jobs. He wrote every line himself on a small VPS that also hosted his blog.
In a 2011 interview he explained the philosophy: charge enough to cover costs, keep the user base manageable, and prefer boring tech you can debug at 2 a.m.
Lesson
Payment is a load-shedding mechanism. Pinboard’s fee is product design, not just monetization.
2011–2017
Delicious migration hug, dedicated hardware
PHP
MySQL
Perl workers
Dedicated servers (DigitalOne, ServerBeach)
S3 backups
When Delicious users fled en masse, Pinboard stayed up on MySQL plus dedicated hardware — Cegłowski told ReadWrite he prefers non-virtualized servers for predictable I/O. High Scalability summarized the stack: PHP, Perl, MySQL, Sphinx, cron, S3 — no framework fashion parade.
He bought Delicious’s remnants in 2016 while keeping Pinboard’s ops model: small team, conservative features, reliability over growth hacks.
Lesson
Load RAM onto boring servers before you load buzzwords onto slide decks. Pinboard optimized MySQL, not headcount.
2018–today
Eleven years in, still introvert-scale
PHP 7+
MySQL
Perl background jobs
Owned/bare-metal hosting
S3
On Pinboard’s eleventh birthday Cegłowski wrote about finally moving to modern PHP and MySQL so the site could run on a contemporary laptop — remedial work he’d deferred while the product kept earning.
The architecture did not become a microservices map. It became maintainable enough for one skeptical human to keep promises about speed and privacy.
Lesson
“Boring architecture” is a competitive moat when your competitors need standing meetings about sharding.
Sources
- Thuktun — Interview with Maciej Cegłowski of Pinboard (2011)
- High Scalability — Pinboard.in architecture (pay to stay small)
- Pinboard blog — Pinboard is eleven (2020)
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
Pinboard's stack made sense for Pinboard. 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