Mythos home page
Start building

Connect

Supabase connection status

The former BYO Supabase connection is retired while Mythos builds its managed backend.

New Supabase connections are not available. The former More → Cloud onboarding and workspace console have been retired.

Mythos is replacing the old bring-your-own Supabase flow with a separate managed backend for generated applications. The replacement stays hidden until its database, authentication, storage, jobs, functions, logs, usage limits, and recovery path work end to end.

What this means now

  • Landing pages, portfolios, documentation sites, and other frontend projects continue to build, preview, publish, and connect to GitHub normally.
  • Mythos cannot currently provision or connect a new application database from the workspace.
  • An already-connected legacy project can keep using its previously stored public project URL, anon key, and frontend scaffold. For other projects, a form or sign-in screen is only visual unless the generated application has a real backend that you configure outside the retired Mythos flow.
  • Never paste a service-role key, database password, private API key, or other server secret into a prompt or client-side application.

Existing Supabase projects

Retiring the Mythos interface does not delete or change an external Supabase organization, project, database, user, file, or function. Manage those resources directly in your Supabase account.

Mythos retains the fenced legacy records required to preserve an existing frontend connection and to support safe cancellation, account-authorisation revocation, export, and deletion handling. This compatibility does not permit new OAuth, provisioning, provider-management actions, or database migrations. If you need help with a previous Mythos connection, contact support; do not send credentials.