Skip to main content
This guide takes you from a blank account to a published site. The 5-credit sign-up bonus covers a direct first Build; optional Plan AI turns use 1 credit each before the separately charged Build.

Before you start

  • A Mythos account (sign in with Google, GitHub, or an email code).
  • Your 5 free credits — granted automatically when you confirm your account. A first build costs 3, so the free credits cover it.
Two later steps have their own prerequisites: the backend step needs a Supabase project to connect, and GitHub two-way sync needs a one-time GitHub account connection. Neither is required to build and publish your first site.

Build your first project

1

Start from a prompt

On your dashboard, type what you want to build in the prompt box. Be specific about the kind of site and its sections — Mythos turns vague prompts into real ones, but detail gets you closer on the first try.
2

(Optional) Plan it first

Toggle Plan mode before sending to answer focused questions and review an editable plan draft before any code is written. Each accepted AI turn costs 1 credit after its response is saved; a failed turn is refunded, local draft edits are free, and the Build after approval is charged separately. See Plan mode.
3

Watch it build

Mythos scaffolds the project and streams a live progress card, then a preview. This first build costs 3 credits. Behind the scenes it’s a real commit in the project’s private repository. Connect your GitHub account and Mythos creates a new private repository you own, then keeps one selected active branch in two-way sync.
4

Iterate

Refine in chat — each edit costs 2 credits:
Or open the workspace editor to change the code directly when you want precise control.
5

Add a backend (optional)

To make the quote form actually save submissions, connect your own Supabase project under More → Cloud. Mythos then wires the form to a real table in your database. See Connect Supabase.
6

Publish

When you’re happy, publish to a live *.r21.dev URL. You can add a custom domain later. See Publishing.

While a build runs

Generation is asynchronous, so the chat moves through a few states:
Publishing makes your site public on the internet — anyone with the URL can open it. Review what’s on the page (and that no private keys are in the frontend) before you publish.

Tips for a good first build

Name the sections you want (“hero, services, pricing, FAQ, footer”) and the tone (“clean and minimal” / “dark and bold”). Mythos writes real copy for your industry — mentioning the industry helps.
  • Describe one page well rather than asking for a whole multi-page site up front — you can add pages by chat afterward.
  • If you need a form to store data, say so — then connect Supabase so it has somewhere to save.

Limitations to know up front

  • Mythos builds the frontend. A database, auth, and file storage come from your connected Supabase project, not from Mythos.
  • A build that runs out of room or errors is refunded — you’re only charged when a result is delivered.

FAQ

Usually a minute or two for a single page. If you use Plan mode, its questions and editable draft are completed before the separate Build begins.
No. You can build and iterate entirely in chat. The code editor is there when you want it.
Mythos builds it in a private managed repository. You can also connect your GitHub account; Mythos then creates a new private repository you own and keeps one selected active branch in two-way sync.
Yes. Reverting restores an earlier version as a new commit, so your history is never destroyed.