Mythos home page
Start building

Connect

Connect your tools

Connect your code to GitHub or bring supported external services into a Mythos project.

You can build and publish many Mythos projects without connecting anything. Add an integration when you need a repository you control or another currently supported service.

Start with the result you want, then open the matching connection surface when the service is available.

Available connections

Managed backend

In development. New database, authentication, storage, and function connections are not currently available in the workspace.

GitHub

Create a private repository in your GitHub account and keep one selected branch in sync with Mythos.

Connectors

Connect supported services and tools from the Connectors catalog. Each entry shows what it can do and what setup it needs.

When to connect something

  • The managed application backend is still in development. Do not treat a visual form, account screen, or upload control as persistent until a real backend is available and configured.
  • Connect GitHub when you want the code in a private repository that you or your team can clone, edit, and use outside Mythos.
  • Open Connectors when the app or your Mythos workspace needs to work with another supported service.

Landing pages, portfolios, documentation sites, and other content-first projects often need no integration at all.

A simple connection flow

Build the first version

Describe the app you want and review it in Preview.

Open the right connection

Use Git for GitHub or More → Connectors for another supported service.

Approve access

Follow the provider's sign-in and permission screen. Choose only the account, organization, or resource you want Mythos to use.

Continue your work

Return to the workspace and continue the project after the connection is confirmed.

You stay in control

A GitHub repository created for you remains in the GitHub account or organization you selected. You can disconnect it later without deleting the repository. Any external Supabase resources connected through the retired legacy flow also remain in the owner's Supabase account; the UI retirement does not delete or change them.

Only approve access to accounts and projects you intend to use. Never paste private API keys, payment secrets, or service credentials into a prompt or client-side code.