PocketBase
Open-source backend in one Go binary with embedded SQLite, auth, file storage and realtime API.
HN commenters recommend it as a productive backend for personal projects, side projects and internal tools,1234 with one team calling it bulletproof for internal line-of-business apps.5 Caveats are few: one commenter warns its expressive API and overposting need care in public-facing apps,6 and another dislikes its SPA approach.7
Why people recommend it
Side projects · 3
Commenters use it as the backend for personal and side projects, including AI-built tools.
“After discovering pocketbase, I never went back to any of those tools. Works surprisingly well even for mid to large web-apps.”
“I love it and use it for personal projects and internal tools.”
Show 1 more
“You might want to have a look at pocketbase. I use it as a backend for my vibecoded "auto-SaaS" Tools.”
Productivity · 2
Users describe it as a delightful, productive setup that saves time and money.
“I use it with pocketbase and it is a delightful and very productive setup.”
“We use pocketbase for a lot of our internal LoB apps and it's been bulletproof.”
Internal tools · 2
Used for internal tools and line-of-business apps, where one team found it bulletproof.
“We use pocketbase for a lot of our internal LoB apps and it's been bulletproof.”
“I love it and use it for personal projects and internal tools.”
Litestream pairing · 2
Commenters report it works well with SQLite replication via Litestream.
“I use it with pocketbase and it is a delightful and very productive setup.”
Scales further · 1
One former Supabase user says it works well even for mid to large web apps.
“After discovering pocketbase, I never went back to any of those tools. Works surprisingly well even for mid to large web-apps.”
Schema migrations · 1
Automatic database migrations let schema changes go into version control.
“I love it and use it for personal projects and internal tools.”
Caveats and dissent
Public API risk · 1
Its expressive API and overposting risk call for caution in public-facing apps.
“We use pocketbase for a lot of our internal LoB apps and it's been bulletproof.”
SPA approach · 1
One commenter dislikes the SPA approach and would rather use server-side rendering.
“I'll give it a try, but I'm not a fan of the SPA approach.”
Often compared with
Threads where it came up
- Pocketbase – open-source realtime back end in 1 file 5 mentions
- Ask HN: What do you run on a $5 VPS that's worth keeping online 24/7? 1 mention
- Ask HN: How do you keep up with HN these days? 1 mention
- Ask HN: What Are You Working On? (April 2026) 1 mention
- Litestream Writable VFS 1 mention
- Many Small Queries Are Efficient in SQLite 1 mention
Data: pocketbase.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 10
“You might want to have a look at pocketbase. I use it as a backend for my vibecoded "auto-SaaS" Tools.”
“It uses pocketbase as the backend.”
“So I was trying: - pocketbase”
“I've used it with pocketbase and it works.”
“I use it with pocketbase and it is a delightful and very productive setup.”
“After discovering pocketbase, I never went back to any of those tools. Works surprisingly well even for mid to large web-apps.”
“Pocketbase is pretty cool”
“I love it and use it for personal projects and internal tools.”
“We use pocketbase for a lot of our internal LoB apps and it's been bulletproof.”
“I'll give it a try, but I'm not a fan of the SPA approach.”