Two different starting points
PocketBase packages a SQLite-backed application backend with authentication, file handling and an administration interface. Supabase builds its backend platform around PostgreSQL and related services. Both can reduce the amount of backend code needed for a prototype, but they do not have the same storage architecture or operating surface.
The decision to make first
Write down the shape of the actual data, the expected concurrent use and the integrations that depend on SQL. Then decide who restores the service after a failed deployment. Our recommendation is to treat database familiarity and recovery ability as inputs to the decision, rather than assuming the shorter installation guide means the easier product.
Check the limitations at the source
PocketBase publishes a warning about its pre-1.0 status and production-critical use. Read that warning and the migration guidance before committing important data. For Supabase, distinguish the managed offering from self-hosting: running its services yourself transfers operational responsibility to you. Check which features and maintenance tasks apply to the deployment you are considering.
A comparison you can run
Use the same tiny application in both: two related tables or collections, one sign-in flow, one file upload and a backup. Export the records and restore them somewhere new. Record the manual steps, failure points and recurring costs. Those results will be more informative for your product than a generic ranking; this note does not claim a completed benchmark.