I think the real question isn’t whether PocketBase can handle production, but whether it fits the complexity of the SaaS you’re building.

I’ve found tools like PocketBase really appealing for getting an MVP out quickly. The challenge comes later when requirements around scaling, integrations, background jobs, or more complex data workflows start growing.

For a simple SaaS, keeping the stack lean can be a huge advantage. But if you already know the product will become infrastructure-heavy, it may be worth planning for that transition early.

I think the real challenge appears when the customer base grows. A tool can work perfectly for an MVP, but production usage may expose limits around performance, reliability, or infrastructure that aren’t obvious at the beginning.

I’d be especially curious about the maintenance side. If a SaaS grows significantly, the amount of custom workarounds needed could determine whether PocketBase remains practical or becomes something the team eventually needs to replace.

Yeah, this is something I’ve been curious about too. PocketBase looks great for getting an idea off the ground quickly, but I always wonder what happens once real users start piling in. I’d love to hear from someone who’s actually been running a SaaS on it for months and what surprised them along the way.

PocketBase for a small project but not for a full SaaS. Curious to hear from others too. My main concern would be scaling and multi-tenancy. It seems great for MVPs, but I wonder how it holds up when you have hundreds of paying customers and need things like role-based access at scale.

I think PocketBase works well until it doesn’t. The real question is whether you can afford to migrate later. If the product grows fast, you might outgrow it quickly. But if you plan for that from the start and keep things modular, it could carry you further than people expect.

PocketBase seems really interesting for getting a SaaS off the ground without adding a lot of backend complexity. The part I’d be most curious about is what happens once real customers start creating messy, unpredictable usage patterns. Things that feel completely fine with a small user base can become painful later, especially around scaling and backups. Hearing from people who’ve actually lived through that stage would be more useful than benchmarks.

I think PocketBase is one of those tools where the real question isn’t “Can it scale?” but “How expensive is it to outgrow?” If it lets you reach paying customers quickly without creating a huge mess, that’s valuable. The important part is having a clear exit plan before you actually need one.

The interesting part is what happens after the MVP stage. Something can work perfectly with a small user base but become a different problem once you have real customers, more data, backups, and things that need to stay reliable. I’d be more interested in hearing about the first limitation people actually hit after running PocketBase for a while.

This is a really good question because PocketBase seems especially popular for MVPs, but real-world SaaS usage is a different test entirely. I’d also be interested in hearing from people who have run it in production for several months, particularly around reliability, scaling, backups, and maintenance. Sometimes the limitations of a platform only become obvious once you have real customers and growing data. That kind of firsthand experience is much more valuable than benchmark comparisons. It would be great to hear what people would do differently if they were starting their SaaS with PocketBase again, and whether they eventually migrated or stayed with it.