“I'd lean toward PostgreSQL-based infrastructure, such as Supabase or a custom backend using Go/Node.js and PostgreSQL.”
“Horizontal scaling | Limited | More flexible”
“Managed hosting | No official hosting | Yes”
“Database portability | More limited | PostgreSQL ecosystem”
“Production maturity | More caveats | Generally stronger”
“Operational complexity | Low | Moderate”
“PocketBase is absolutely a realistic choice for production, not just prototypes and side projects.”
“PocketBase gives you quite a lot out of the box:”
“In fact, its simplicity is one of its biggest advantages.”
“You get a remarkably simple backend, inexpensive hosting, and very little infrastructure to maintain.”
“The official FAQ even describes PocketBase handling 10,000+ persistent realtime connections on a relatively inexpensive VPS, although actual capacity depends on workload. pocketbase.io”
“PocketBase has built-in backup functionality and documents its recommended production deployment practices.”
“PocketBase uses SQLite and is designed to run on a single server. It scales vertically rather than horizontally.”
“PocketBase explicitly warns that backward compatibility isn't guaranteed before version 1.0.”
“PocketBase is self-hosted and doesn't have the commercial backing, dedicated support infrastructure, or managed hosting ecosystem of larger backend platforms.”
“SQLite is surprisingly capable, but it isn't PostgreSQL.”
“Also, migrating away from PocketBase isn't entirely trivial. Its APIs, access rules, and application-specific integrations are PocketBase-specific. GitHub”