PocketBase
One Go binary: SQLite database, auth, file storage, realtime and an admin UI.
Overall in convex alternatives
4of 11 · score 66.5
Data coverage
96%
25 of 26 fields sourced
Best for
- •Internal tools and side projects where one VPS is plenty
- •Anyone who wants the entire backend to be a file they can copy
- •Air-gapped or on-premises deployments
Strong on
- +Cold start 0ms 1/6
- +GitHub stars 48,000 3/10
Weak on
- −MCP server No 8/11Better: Convex: Yes
- −Egress metered No 8/9Better: Convex: Yes
- −Vector search No 8/11Better: Convex: Yes
- −Backing solo-maintainer 11/11Better: Firebase: big-tech
vs Supabase
- •Ahead on Entry price: $0/mo vs $25/mo
- •Ahead on Cold start: 0ms vs 250ms
- •Behind on MCP server: No vs Yes
- •Behind on Egress metered: No vs Yes
How PocketBase scores among 11 convex alternatives25 of 26 fields known
Features13
TS inference
Partial
6/11
Leader: Convex · Yes
Transactions1st
serialisable
1/11
Local-first sync
No
6/11
Leader: InstantDB · Yes
Optimistic writes
No
7/11
Leader: Convex · Yes
Cron & scheduling
Partial
6/11
Leader: Convex · Yes
Vector search
No
8/11
Leader: Convex · Yes
Full-text search
Partial
5/11
Leader: Convex · Yes
Hard limits
One machine. SQLite tops out near a billion bytes per value and a single concurrent writer; everything else is your disk and RAM.
Cold start1st
0ms
1/6
Function timeout
—
Portability & exit5
Exit cost
3
5/11
Leader: Neon + Drizzle · 1
Bulk export1st
Yes
1/11
Raw SQL1st
Yes
1/11
Agentic2
MCP server
No
8/11
Leader: Convex · Yes
Agent fit
3
5/11
Leader: Convex · 5
Pricing3
Egress metered
No
8/9
Leader: Convex · Yes
Traction2
GitHub stars3rd
48,000
3/10
Leader: Supabase · 90,000
Backing
solo-maintainer
11/11
Leader: Firebase · big-tech
Appwrite
Convex
ElectricSQL
Firebase
InstantDB
Neon + Drizzle
Nhost
Zero
