Skip to main content
Connect Supabase when your app needs more than a static page. A Supabase project can store form submissions, manage user accounts, keep uploaded files, and support backend functions. The project and its data stay in your Supabase account. You do not need Supabase for a landing page, portfolio, or other site that does not save data.

​
What you can build

Save data

Store contact requests, bookings, profiles, products, and other information your app needs later.

Add accounts

Let people sign up, sign in, and see information that belongs to them.

Store files

Support uploads such as profile photos, documents, or product images.

Use functions

Run backend work that should not happen in a visitor’s browser.

​
Connect a project

You need a Mythos project and a Supabase account. Mythos handles the connection flow, so you do not need to find or paste project keys.
1

Open Cloud

In the project workspace, open More → Cloud.
2

Connect your Supabase account

Select Connect Supabase account. Sign in to Supabase and approve access in the window that opens.
3

Choose a project

Select the Supabase organization and project this Mythos app should use. If you do not have a suitable project, create one in Supabase and return to the workspace. When more than one project is available, Mythos asks you to choose.
4

Wait for Connected

Mythos checks that the project is ready and then opens the Cloud tools for it. If a Build paused to request Supabase, that same Build continues after the connection is ready.
Connecting Supabase does not spend credits. A later request that changes your app uses the normal Build price. See Credits & pricing.

​
Ask Mythos to use your data

Once the project is connected, describe the behavior you want in plain language. Include who should be allowed to read or change the data.
Mythos can prepare safe, additive database changes as part of the Build. Requests that could delete or rewrite existing data need extra care and are not applied automatically.

​
Manage the connection

Open More → Cloud to see the connected project and shortcuts for its database, users, storage, functions, logs, and usage. These tools work with the Supabase project you selected. To use a different Supabase project, disconnect the current project first, then connect the new one. Mythos does not copy data between Supabase projects. Disconnecting Mythos does not delete your Supabase organization, project, database, users, or files.
Keep private service keys and third-party secrets out of prompts and frontend code. Mythos does not need your Supabase service-role key to connect the app.

​
Troubleshooting

Return to More → Cloud and refresh the connection. Confirm that the Supabase account you approved can access the organization and project you want to use.
Keep the workspace open and wait for the project to become ready. Mythos continues once Supabase reports that the project is available.
Rephrase the request as a safe addition and say who should have access. Changes that delete data or weaken access rules require a separate manual review.