I'm a huge fan of Pocketbase. Backing up the sqlite though had me more stressed than I'd prefer, and I wanted a plug-and-play way to sqlite3_rsync a backup while Pocketbase was running: so I've been working on this: https://sqlrsync.com. MVP works. Billing isn't being checked yet (be gentle but it's Cloudflare Durable Objects underneath so it should be local, fast, and resilient.) Would love feedback from anyone open to trying it.
Pocketbase – open-source realtime back end in 1 file
101–110 of 211 posts
Re: Pocketbase – open-source realtime back end in 1 file
#102Earlier quoted context omitted.
TrailBase has a comparison page https://trailbase.io/comparison/pocketbase/
What a respectfully and humbly written comparison page. Ditto for their Supabase comparison. I can't rate the objectivity since I know very little about TrailBase but they got my attention now. It brings me such joy to see such a writeup in a world where humility is perceived as weakness. Kudos.
Thanks! Standing on the shoulders of giants :heart:
Re: Pocketbase – open-source realtime back end in 1 file
#103I really like this project too! But i think there is some misunderstanding between pb users and creator. As far as I understand creator making it as complete backend solution and users should write all backend by extending pb.
But a lot of user (including me) use pb as database layer only, not as backend. I still write my backend on my project and pb is just like database as a service for me. And much happier than using it as only backend.
Re: Pocketbase – open-source realtime back end in 1 file
#104Congrats on the launch!
eh? what launch?
been using it for years now, it's brilliant
Re: Pocketbase – open-source realtime back end in 1 file
#105I can mirror everyone singing praise to pocketbase here. Once you grasp the concepts (which map pretty closely to SQL concepts, with rules for row-based security), it is by far the easiest way IMO to create a maintainable, robust backend with direct auth integrations and a pleasant interface.
I have around 5 instances of pocketbase running on a 10 USD/month Hetzner server, serving thousands of users a day without breaking a sweat.
Re: Pocketbase – open-source realtime back end in 1 file
#106Trailbase is the same concept, but written in Rust instead of Go.
Trailbase won my heart by not leaving out curl-commands in their examples :)
Re: Pocketbase – open-source realtime back end in 1 file
#107Beware of pocketbase! I am running my startup wetarseel.ai. You'll be badly locked into one instance with one sqlite file, plus its queries are not mapping to SQL, try a bulk delete and it will choke your entire system, plus other footguns.
Re: Pocketbase – open-source realtime back end in 1 file
#108Postbase uses PostgreSQL and BetterAuth. No GUI yet, but it's in the plan and will be called Admin (Panel). I had the same instinct of using SQLite, but then, after a bit of research, PostgreSQL seemed a better alternative for serious projects.
Postbase, in contrast to PocketBase, doesn’t seem ready for primetime : ” Brand new project launched 02 Nov 2025, this is boiler plate but working! Expect heavy changes coming every few hours until stable Mostly all code is ChatGPT generated but manually tested by human.”
And by that description, I assume it's never going to be ready for primetime.
Re: Pocketbase – open-source realtime back end in 1 file
#109Trailbase is the same concept, but written in Rust instead of Go.
Another selling point for Pocketbase then.
Re: Pocketbase – open-source realtime back end in 1 file
#110I'm a huge fan of Pocketbase. Backing up the sqlite though had me more stressed than I'd prefer, and I wanted a plug-and-play way to sqlite3_rsync a backup while Pocketbase was running: so I've been working on this: https://sqlrsync.com . MVP works. Billing isn't being checked yet (be gentle but it's Cloudflare Durable Objects underneath so it should be local, fast, and resilient.) Would love feedback from anyone ope…
Love seeing the love for SQLite. Personally, I've had a great experience with litestream, which will continuously replicate any changes. Are you using https://sqlite.org/rsync.html?