Blog · 16 November 2026 · 6 minute read
Supabase or plain Postgres on your host: which database for a new SaaS?
Supabase is Postgres plus sign-in, storage and a dashboard. Postgres on your host is one less account. How to choose for a first product.
They are the same database underneath
Supabase is built on Postgres. Whatever you choose, your data sits in Postgres tables and your coding tool writes ordinary SQL. The choice is about what comes around the database, and how many accounts you want to manage.
What plain Postgres on your host gives you
Some hosts, Railway among them, can create a Postgres database inside the same project as your app. The connection string appears as a variable, the app reads it, and you are done.
- One account and one bill for app and data.
- The database sits next to the app, so connections are fast and simple.
- Nothing extra to learn: it is only a database.
- Sign-in, file storage and anything else are written in your app or added as separate services.
What Supabase gives you
Supabase wraps Postgres with the things many apps need next.
- Sign-in with email, magic links and social providers, managed for you.
- File storage with access rules.
- A dashboard to look at and edit data without writing SQL.
- Client libraries that let a frontend talk to the database directly, guarded by row level security.
- It works with any host, which matters if your app runs on Vercel.
The cost of the extras
Extras are also things to configure correctly. Row level security is powerful, and a missing rule can expose a table to anyone with your public key. If an AI writes your code, ask it to list every table and the rule that protects it, and test with a second account that should not see the data.
You also add one more account, one more set of keys and one more dashboard to the product.
Questions that decide it
- Hosting on Railway and happy to keep sign-in inside the app? Postgres on the host is the simplest setup there is.
- Hosting on Vercel? You need a database elsewhere anyway, and Supabase is a natural partner.
- Want social sign-in without writing it? Supabase Auth.
- Need users to upload files? Supabase storage, or a separate bucket such as Cloudflare R2.
- Moving an app out of an AI builder that already used Supabase? Stay on Supabase in your own account.
What does not change
- Take backups and know how to restore one before you need to.
- Keep the connection string and service keys out of your repository and out of chats.
- Use one database per product, so ending a product never touches another.
- Run schema changes as migrations kept in the repository.
Changing later
Because both are Postgres, moving between them is an export and an import. The harder part is sign-in: if users live in Supabase Auth, moving them to another system takes planning. Decide sign-in with more care than you decide the database.
How Shipyard handles the choice
When you pick a stack in Shipyard you choose Postgres on the host or Supabase, and separately whether sign-in is built into the app or handled by Supabase Auth. At launch it creates the database in your own account, stores the connection details as variables on the host, and tells your coding tool in the build prompt which database and sign-in method to write for.
Launch in an hour, not a weekend
Shipyard connects your accounts once, then sets up the domain, hosting, database, email and payments for every new product.
See how it works