Guides / Comparisons
Built into the app vs Supabase Auth for launching a new product
How people sign in. Shipyard can set up either Built into the app or Supabase Auth for you. This is how they differ when the goal is to get a new product live quickly.
The short answer
- Built-in sign-in is email and password with sessions stored in your own Postgres. It works with every database option.
- Supabase Auth is handled by Supabase and needs Supabase as the database.
- Pick built-in for the simplest setup. Pick Supabase Auth if you already chose Supabase and want its sign-in screens and providers.
Built into the app
Email and password, sessions in Postgres.
- No token needed: it is part of an account you already connect.
Supabase Auth
Needs Supabase as the database.
- 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