Guides / Comparisons
Postgres on the host vs Supabase for launching a new product
Where the app keeps its data. Shipyard can set up either Postgres on the host or Supabase for you. This is how they differ when the goal is to get a new product live quickly.
The short answer
- Postgres on the host is created inside the hosting project: nothing extra to connect, and the connection string is wired for you.
- Supabase is Postgres in its own project with a pooled connection, and it is required for Vercel hosting and for Supabase Auth.
- Pick Postgres on the host for the fewest moving parts. Pick Supabase if you want its dashboard, or sign-in handled by Supabase Auth.
Postgres on the host
Created inside the hosting project.
- No token needed: it is part of an account you already connect.
Supabase
Postgres in its own project, pooled connection.
- Token: A personal access token
- Set up first: Create an organisation if you have none. The free plan allows two active projects: pause or delete one if you already have two.
- Stays manual: Creating the Supabase account and an organisation. The free plan allows two active projects and pauses a project after a week without use.
Have this set up for you
Shipyard connects your accounts once and then does all of this for every new product, in about an hour.
See how it works