scribase
PocketBase alternative

A hosted PocketBase alternative on Postgres

PocketBase is one binary with SQLite, auth, file storage and realtime inside it. It is free, open source and quick to start, and you run it on your own server: there is no managed PocketBase. It scales on one machine only. Scribase covers the same parts as a hosted service on Postgres, so there is no server to patch or back up. Pick Scribase when you do not want to operate a server or you need Postgres. Stay on PocketBase when one small binary on your own box is exactly what you want.

Last checked November 17, 2026.

The short answer

  • Pick Scribase when you do not want to rent, secure, update and back up a server yourself.
  • Pick Scribase when you need Postgres: joins across large tables, extensions such as pgvector, or more than one machine's worth of headroom later.
  • Stay on PocketBase when you want open source, full control, zero vendor and an app that fits comfortably on one server.

PocketBase and Scribase, side by side

PocketBase facts read on pocketbase.io/faq 2026-11-17
PocketBaseScribase
What it isOne self-hosted binaryA hosted service
DatabaseEmbedded SQLite. No plans to support other databases.Postgres 17
Who runs itYou: server, updates, TLS, backupsScribase runs it. Backups and point-in-time recovery are included.
ScalingOne server only (vertical)Managed. Free and Hobby projects scale to zero when idle; Pro stays warm.
Auth, files, realtimeBuilt inBuilt in, enforced by row level security
Access rulesAPI rules per collectionPostgres row level security policies
PriceFree software, plus your server1 project free with no time limit (0.5 GB database, 1 GB files, no card); then $5 or $25 a project a month
Open sourceYesCore is not open source
SupportA personal open-source project built on a volunteer basis, with no promise of maintenance or supportA company with a support inbox. No compliance certifications yet.

Sources: PocketBase: FAQ, Scribase: Pricing

Signs it is time to move off PocketBase

  • You are the only person who can restart the server, and it has gone down while you were away.
  • You are not sure the last backup would restore.
  • You need a Postgres feature: pgvector, full text search across large tables, queues, scheduled jobs in the database.
  • A client or an investor asks who operates the backend and the answer is one binary on a VPS.

Moving from PocketBase

There is no PocketBase importer; the move is manual. It is usually small, because a PocketBase schema is already a set of tables.

  1. Step 1

    Create the project

    One command creates Postgres and Auth and writes the URL and anon key into your .env file.

    Creates the backend and writes the URL and anon key into your .env filesh
    npx scribase init
  2. Step 2

    Recreate collections as tables

    Each collection becomes a Postgres table. Relation fields become foreign keys.

  3. Step 3

    Export and load the rows

    Export each collection to CSV or JSON from your SQLite file, then load it through a migration or the REST API.

  4. Step 4

    Rewrite API rules as policies

    Each collection rule becomes a row level security policy that reads auth.uid().

  5. Step 5

    Swap the client

    Replace the PocketBase SDK calls with supabase-js calls. Users get new ids and reset their password on first sign-in.

What Scribase does not do

  • It does not run on your own machine as one binary. If that is the point, stay on PocketBase.
  • The free project is 0.5 GB of database. A PocketBase server is limited only by its disk.
  • One region today (Frankfurt). If your users or your compliance rules need another region, this is not the right host yet.
  • Direct Postgres connections from the internet (ports 5432 and 6543, for psql or pg_restore) are not open yet. Migrations, the console SQL editor and the HTTP serverless driver work today.
  • No compliance certifications yet (no SOC 2, no HIPAA BAA).
  • The core is not open source. You can export everything, and a licensed self-hosted deployment exists, but you cannot clone the server from a public repository.
FAQ

Questions people ask

Is there a hosted version of PocketBase?

Not from the PocketBase project. PocketBase is self-hosted only; you run the binary on your own server. If you want the same parts (database, auth, files, realtime) as a hosted service, Scribase and Supabase provide them on Postgres.

Does PocketBase support Postgres?

No. PocketBase uses embedded SQLite, and its FAQ says there are no plans for supporting other databases. Scribase projects are Postgres 17.

Can PocketBase scale beyond one server?

The PocketBase FAQ says it scales "only on a single server, aka. vertical". That is enough for many apps. If you expect to outgrow one machine, start on a database that does not have that ceiling.

What does a hosted PocketBase alternative cost?

Scribase keeps one project free with no time limit (0.5 GB database, 1 GB files, no card). More projects are $5 a month each on Hobby or $25 on Pro. PocketBase itself is free; you pay for the server it runs on.

Can I migrate from PocketBase to Scribase automatically?

No. There is no PocketBase importer. You recreate collections as SQL tables, export and load the rows, and rewrite API rules as row level security policies. Users reset their passwords.