Skip to main content
Mythos builds the frontend — the React + Vite app, its components, and its UI. Anything behind the UI — a database, user accounts, file storage, server secrets — comes from a backend you bring. Today that backend is your own Supabase project. Mythos keeps each project in a private Git repo and builds it commit by commit. Connect your GitHub account and Mythos creates a new private repository you own, then keeps one selected active branch in two-way sync. The mental model: Mythos owns the app shell and the AI edits; you own your data, your users, and your code.
Cost: building a new project costs 3 credits; an edit costs 2. New accounts start with 5 free credits. Connecting a backend or a repo does not cost credits on its own. See Credits & pricing.

​
Why it works this way

  • Your Supabase data stays yours. Mythos never runs your connected Supabase database or holds the auth tokens of your app’s Supabase users. If you stop using Mythos, your Supabase project and its data are untouched in your own account.
  • Real code, not a locked template. The app the agent writes is a conventional React + Vite project committed to Git. Connect your GitHub account and Mythos creates a new private repository you own, then keeps one selected active branch in two-way sync.
  • No backend lock-in. Mythos captures no backend revenue and does not proxy your app’s Supabase database traffic. Connector setup and connector action traffic use the separate connector gateway.

​
Two distinctions worth getting right

​
What “connect Supabase” means

When this documentation says “connect Supabase,” it always means your own Supabase project — the one holding your app’s database, users, and files. You connect it from Workspace → More → Cloud, it stays in your Supabase account, and Mythos never stores your app’s data anywhere else.

​
A Mythos-built site vs the workspace IDE

  • A Mythos-built site is the app the agent generates — what your visitors see, and what you publish to a live URL.
  • The workspace IDE is the editor inside Mythos where you chat with the agent, browse the file tree, and edit code by hand.
Editing in the IDE changes your project’s code; publishing pushes a built copy of that code live.

​
What you connect

Supabase

Connect your Supabase account, then choose or create the project this app should use. No keys need to be copied or pasted.

GitHub

Review and roll back the managed history, then connect your GitHub account. Mythos creates a new private repository you own and keeps one selected active branch in two-way sync.
Once Supabase is connected, you wire data in plain language — for example:
If that build needs Supabase and the project is not connected yet, Mythos pauses the same build, opens Cloud, and continues automatically after you finish connecting it.

​
App and chat connectors

Connectors are separate from the app’s backend. The catalog exposes bounded setup surfaces for external services and tools; it does not replace Supabase for database, authentication, or storage. Each catalog entry remains authoritative for which setup methods and app/chat modes are available. The current catalog marks these definitions as Ready:
  • Notion
  • Linear
  • Resend
  • Airtable
  • Google Analytics
  • Custom MCP
  • Custom API
Stripe appears in the catalog as Coming soon. Each connector exposes only the setup methods and app/chat modes shown in its catalog entry. Open Connectors from the dashboard, or open Workspace → More → Connectors for project context.

​
What Mythos does not do

  • It does not host a database for you. There is no “Mythos Cloud” backend — that was retired.
  • It does not see your Supabase service role key. The agent is given only your project URL and the public anon key.
  • It does not proxy your app’s database traffic. Your app talks to your Supabase directly.
  • It does not migrate your data between providers — switching backends means pointing at a new project.

​
FAQ

No. Mythos is frontend-first — landing pages, marketing sites, portfolios, and dashboards work with no backend at all. You only connect Supabase when you need data saved, user accounts, or file storage.
Supabase is the only supported, fully wired backend for app data, authentication, and storage. The separate Connectors catalog links external services and tools; those connectors are not alternative app backends.
Mythos keeps each project in a private Git repository it manages, one per project, and every build and edit is a commit. Connect your GitHub account and Mythos creates a new private repository you own, then keeps one selected active branch in two-way sync. See GitHub.
Yours. Mythos connects to a project in your own Supabase account, never stores your app’s data itself, and leaves that project untouched if you stop using Mythos.
  • Connect Supabase — the end-to-end connect flow and what the agent can see.
  • GitHub repos — managed history plus a new private repository Mythos creates in your connected GitHub account, with two-way sync on one selected active branch.
  • Welcome to Mythos — the product overview.
  • Publishing your site — take a built project live (the published build needs the committed .env).