Mythos is pay-as-you-go. Some terms below cost credits (a build, an edit, a template remix);
each definition says so. New accounts start with 5 free credits. See
Credits & pricing.
Core terms
Credit
The unit you spend on a generation. One action costs a fixed number of credits, charged when the build starts and refunded in full if it fails. A new project costs 3 credits, an edit 2, a template remix 5. New accounts start with 5 free credits. Credits are bought in packs and never expire. See Credits & pricing.Build
Creating a new project from a prompt — Mythos scaffolds a full React (Vite) or Next.js project, writes the components, and commits it to a private repository it manages for you. Costs 3 credits. Also the verb for what the agent does each time it generates code. (Connect a GitHub account to export the code to a repo of your own.)Edit
A change applied to an existing project — Mythos modifies the code and lands a new commit. Costs 2 credits. Edits are how you iterate after the first build (“make the hero darker”, “add a pricing section”).Build mode
The default way to generate: Mythos builds directly from your prompt, with no questions first. Contrast with Plan mode below. Toggle between them next to the send button in the composer.Plan mode
A guided start. Before building, Mythos asks a few questions, turns your answers into three rendered design directions you choose between, then shows a short plan to approve — all free; you only spend credits when the build runs after you approve. See Plan mode.Build mode vs Plan mode. Build mode = straight from prompt. Plan mode = questions → three
designs → plan → build. Both produce the same kind of project; Plan mode just shapes it first.
Project
One app you are building — its code in a private repository Mythos manages, its chat history, and its connected backend (if any). Your projects live in your dashboard; opening one takes you into the workspace.Workspace
The screen where you work on a single project: the chat (where you prompt Mythos), the live preview, and the built-in code editor (the workspace IDE). Distinct from the dashboard, which is the tray of all your projects.Workspace IDE vs the Mythos-built site. The workspace IDE is Mythos’s editor where you read
and edit your code. The site it builds is your app. The IDE requires a wider screen — on phones it
shows a notice to switch to a larger device.
Publish
Shipping your project to a live, public URL. Mythos runs a production build and serves it from a*.r21.dev address; you can point a custom domain at it afterwards. Publishing is a deliberate step —
your project is private until you publish it. See Publishing.
Artifact
A downloadable file Mythos generates for you on request — a PDF, CSV, XLSX spreadsheet, or chart — plus any files you upload in chat. Artifacts live in the project’s Files tab. They are separate from your app’s source code. See Files & artifacts.Skill
A reusable instruction set the agent can load while building — a focused capability (for example, a house style or a recurring task) defined in aSKILL.md file. Mythos ships built-in skills, and you
can add your own per-account skills. See Skills.
Template remix
Forking a ready-made multi-page template into your own new project, which you then customize by prompting. Costs 5 credits. Start a remix from the template gallery.BYO-Supabase / Cloud
Bring-your-own backend. Mythos builds the frontend; for a database, auth, and storage you connect your own Supabase project. Once connected, the Cloud console (under Services → Cloud in the workspace) lets you manage that Supabase — its database, users, storage, and SQL — from inside Mythos, and the agent can wire your forms and data into it.Your Supabase, not ours. Your data and credentials stay in your own Supabase account. Mythos
stores your connection encrypted and the agent sees only the public URL and anon key. See
Welcome to Mythos.
Rename history
Mythos has changed names and swapped major pieces. These older names still appear in old links, screenshots, and search results — here is what they map to now.| You might see | What it is now | When |
|---|---|---|
| keek.one | mythos.new — the product was renamed; same product, new brand and domain | Rebrand completed 2026-04-25; keek.one retired |
| Clerk (sign-in) | Supabase Auth — sign-in moved off Clerk; you now sign in with Google, GitHub, or an email code | Clerk → Supabase Auth, 2026-05 |
| Mythos Cloud (hosted backend) | Removed. Mythos no longer hosts a backend for you — connect your own Supabase instead (BYO-Supabase) | Mythos Cloud retired 2026-04 |
| Connectors (paste-a-key integrations) | Removed. The old connector system was deleted; backend is now BYO-Supabase via the Cloud console | Connector system removed 2026-06 |
”Cloud” means two different things historically. The retired Mythos Cloud was a backend
we hosted. Today’s Cloud console manages your own connected Supabase. Only the second one
exists now.
I have a link to keek.one — is that still Mythos?
I have a link to keek.one — is that still Mythos?
Yes. keek.one was the old name; the product is now mythos.new. The domain
keek.one was retired
on 2026-04-25.The docs mention Clerk somewhere — do I need it?
The docs mention Clerk somewhere — do I need it?
No. Sign-in moved to Supabase Auth in 2026-05. You sign in with Google, GitHub, or an email
code — there is no Clerk account to create.
What happened to Mythos Cloud / the hosted backend?
What happened to Mythos Cloud / the hosted backend?
It was retired. Mythos is frontend-first; for a backend you connect your own Supabase project,
which you then manage from the Cloud console in the workspace.
Where did Connectors go?
Where did Connectors go?
The connector system (paste-a-key integrations) was removed in 2026-06. The supported way to add a
backend is BYO-Supabase.
Related
- Welcome to Mythos — what Mythos is and how a project flows.
- Plan mode — Build mode vs Plan mode in detail.
- Workspace editor — the built-in IDE in detail.
- Templates — the gallery you remix from.
- Publishing — taking a project live.
- Credits & pricing — what each action costs.
- Changelog — when these features and renames shipped.