Supabase Integration
Supabase is a first-class database integration in Deploy Services on CreateOS. It gives you a fully managed Postgres database, authentication, file storage, and realtime subscriptions — all provisioned and connected to your project in one step.
Overview
When you add Supabase from Deploy Services, CreateOS provisions or connects a Supabase project and injects your credentials into the deployment environment automatically. You do not configure a separate Supabase dashboard to get started.
Supabase is available under the Database tab in Deploy Services.
Prerequisites
- An active CreateOS account
- A project created in CreateOS
- Optionally: an existing Supabase project if you want to connect one instead of creating new
Setup Instructions
Connect or create a Supabase project
- Open your project in CreateOS
- Navigate to Deploy Services from the project dashboard
- Select the Database tab
- Click Supabase under Integrations
- Choose one of the following:
- Create new project — CreateOS provisions a new Supabase project and injects credentials automatically
- Connect existing project — paste your Supabase project URL and service role key; your existing schema and data remain untouched
- Your Supabase credentials are now available as environment variables in your project
Tutorial Video
What You Get
Each Supabase integration includes the following services:
- Postgres — a relational database with full SQL support, joins, complex queries, and ACID compliance
- Auth — built-in user authentication with email/password, OAuth providers, and magic links
- Storage — managed file storage for images, videos, documents, and user-generated content
- Realtime — live database subscriptions that push changes to connected clients without polling
How It Works
When you connect Supabase through Deploy Services, CreateOS handles credential injection at the environment level. Your environment variables are available to your application at runtime without any manual configuration.
For staging and production environments, connect a separate Supabase project to each deployment context. Credentials are scoped per environment, so your staging and production databases remain isolated.
Environment variables injected in your project
POSTGRES_DB
POSTGRES_HOST
POSTGRES_PORT
POSTGRES_USER
POSTGRES_PASSWORD
Common Use Cases
SaaS MVP
If you are building a web app that needs user accounts and persistent data, Supabase gives you Auth and Postgres together. You can implement login, signup, and data storage before writing any custom backend logic.
Realtime Collaboration
If you are building a shared workspace, doc editor, or kanban board, Supabase Realtime provides live database subscriptions. Changes propagate to all connected clients the moment they are written — no WebSocket server required.
User-Generated Content
If your app accepts file uploads — photos, videos, documents — Supabase Storage handles managed hosting. Combined with Auth and Postgres, you can associate files with user identities and query them relationally.
AI Apps with Persistent Memory
If you are building an AI agent or LLM-based tool, Postgres with pgvector (Model Context Protocol) extension lets you store conversation history, vector embeddings, and structured AI outputs in a queryable format.
Internal Tools
If you need a production-grade database behind an internal dashboard without managing infrastructure, Supabase Postgres is available with no DevOps setup.
Troubleshooting
Credentials not injecting
If your environment variables are not available at runtime, confirm that your deployment was triggered after connecting Supabase. Redeploy your project after connecting to ensure credentials are picked up.
Connecting an existing project
If you connect an existing Supabase project, CreateOS does not modify your schema or data. Only the credentials are read. If the connection fails, verify that your service role key has not been rotated or revoked in your Supabase dashboard.
⚠️ Important: Rotating your Supabase service role key after connecting will break your deployment environment. Update the connection in Deploy Services immediately after any key rotation.
Realtime not receiving updates
Realtime subscriptions require that Row Level Security (RLS) policies on the target table allow reads for the connected user. If updates are not arriving, check your RLS policies in the Supabase dashboard.