Using Supabase with Fabricate

This page used to say Fabricate set up Supabase tables, auth and storage automatically and deployed your app "with Supabase already wired up and working". None of that is true. Searching every starter project for the Supabase SDK returns nothing; the only mentions of Supabase in the entire template set are three code comments using it as a point of comparison. On the platform side, the word appears in two keyword lists that flag a request as complex. There is no connector, no provisioning, no RLS generation.

What is true is narrower and still worth the page: Supabase is a Postgres database with a well-documented JavaScript client, and the AI is perfectly capable of writing that client into your app. Describe your schema, say you are using Supabase, and you get typed queries, session handling and subscription code. That is a normal code-generation job, not an integration.

The default remains Cloudflare D1. It is generated into your project with a Drizzle schema, needs no external account, and is what the templates, the preview and the deploy path are built around. Choose Supabase because you need Postgres or already run one, not because you expect it to be less setup - it is more.

The boundary to keep in mind: everything inside the Supabase dashboard is yours. Creating the project, defining tables, enabling replication for realtime, turning on auth providers, and above all writing and reviewing Row Level Security policies. Fabricate writes the code that calls your database; it does not secure your database.