Every full-stack application needs a database, most need authentication, and an increasing number need file storage and realtime subscriptions. On CreateOS, builders had to leave the platform to provision each of these services separately — signing up for Supabase, copying connection strings, configuring environment variables by hand, and managing credentials across dashboards that had nothing to do with their actual project. That setup overhead added 30 to 60 minutes per project before a single line of application logic was written, and credential misconfiguration was a recurring failure mode in support tickets.
We built the Supabase integration to close that gap. Supabase is now a first-class service inside Deploy Services, available from the Database tab. One click gives you the full Supabase stack — Postgres, authentication, file storage, and realtime database subscriptions — connected to your project with credentials injected automatically into your environment variables. No separate dashboards, no manual key copying, no configuration files to maintain.
How it works
Open Deploy Services from your project dashboard, select the Database tab, and click Supabase. From there you have two paths.
If you already have a Supabase project with schemas and data, select "Connect existing project." Authenticate via OAuth or paste your API key, select your project from the list, and CreateOS fetches your SUPABASE_URL, SUPABASE_ANON_KEY, and SUPABASE_SERVICE_ROLE_KEY and injects them directly into your project environment. Your Supabase setup stays exactly as it is — nothing migrates, nothing changes on the Supabase side.
If you do not have a Supabase account, select "Create new project." Enter a project name and region, and CreateOS provisions the Supabase project in the background. Credentials are injected automatically when provisioning completes. You end up with a working Postgres database, authentication, storage, and realtime subscriptions without ever visiting supabase.com. The entire flow takes under two minutes and is covered end-to-end on our Docs.
Once connected, credentials persist across deployments. Push a new version of your app, and CreateOS re-injects the Supabase environment variables into the new deployment context automatically. No manual re-linking required.
What you get
The integration connects four Supabase services, each solving a distinct part of the full-stack backend problem.
Postgres gives you a production-grade relational database with full SQL support — joins, complex queries, indexes, foreign keys, and ACID transactions. This is the same database engine running at scale across thousands of production applications, available in the same click that starts your project. For builders working with AI pipelines, Postgres also supports pgvector for storing and querying vector embeddings directly alongside your relational data.
Auth provides built-in user authentication with support for email and password, OAuth providers (Google, GitHub, Apple), and magic links. No separate auth service to wire up, no JWT handling to build from scratch. User accounts and login flows are configured and ready the moment you connect.
Storage handles managed file hosting for images, videos, documents, and user-generated content. No S3 bucket configuration, no CDN setup. Files are stored, served, and managed through the same Supabase client already in your project.
Realtime enables live database subscriptions that push changes to connected clients the moment they are written. Build live dashboards, collaborative editing tools, chat applications, and multiplayer experiences without writing a WebSocket server or implementing polling logic.
Who it's for
If you are building a SaaS MVP and need user accounts plus a database before your weekend is over, connect Supabase and start writing application logic immediately. If you are building a realtime collaboration tool and the prospect of standing up WebSocket infrastructure feels disproportionate to the feature you actually want to ship, Supabase Realtime handles the subscription layer while you focus on the product. If you are an AI builder who needs persistent storage for conversation history, user context, and vector embeddings, Postgres with pgvector gives your agent memory in the same environment it already runs in. And if you are already using Supabase and want to deploy from one place, connect your existing project and keep everything exactly as it is.
What you should know
Supabase billing is separate from CreateOS credits. Supabase charges apply directly to your Supabase account on their free or paid plans. The free tier allows two active projects; users who hit this limit will need to upgrade their Supabase plan to create additional projects from CreateOS. Database schema management — creating tables, editing rows, managing auth users — happens in the Supabase dashboard, not inside CreateOS. We are the deployment and connection layer; Supabase remains the database UI. At launch, each CreateOS project connects to one Supabase project; multi-project switching within the same project is not yet supported.
Getting started
The Supabase integration is available now in Deploy Services. Open the Database tab, connect or create a Supabase project, and your backend is ready. If you are building full-stack applications on CreateOS and want database, auth, storage, and realtime without leaving the platform, this is where you start — createos.nodeops.network.
About NodeOps
NodeOps unifies decentralized compute, intelligent workflows, and transparent tokenomics through CreateOS: a single workspace where builders deploy, scale, and coordinate without friction.
The ecosystem operates through three integrated layers: the Power Layer (NodeOps Network) providing verifiable decentralized compute; the Creation Layer (CreateOS) serving as an end-to-end intelligent execution environment; and the Economic Layer ($NODE) translating real usage into transparent token burns and staking yield.
Website | X | LinkedIn | Contact Us
