Custom domain deploy
Today, every project lives on a Cloud Run preview subdomain. Pointing your own domain at it starts with GitHub export; first-class custom-domain deploy is on the roadmap.
How it works today
Every Mythos project gets a public preview URL on a Cloud Run subdomain. The URL is stable for the lifetime of the project, public read-only, and ideal for sharing with clients or testers. It is a dev build — fine for prototypes, not what you want in front of paying customers.
The current workaround
- Export the project from the workspace GitHub menu to a repository owned by your account or organization, then clone it locally.
- Connect the repo to Vercel, Netlify, Cloudflare Pages, or Railway — every Mythos scaffold is a stock Vite or Next.js project, so the standard integrations work without modification.
- Add your domain at that platform. DNS lives entirely there; Mythos is no longer in the deploy path.
What we are building
- One-click "deploy to your domain" from inside the workspace — add a CNAME, we serve the production build.
- Production vs preview environments — separate URLs, environment variables per env.
- Automatic SSL via Let's Encrypt for connected domains.
No ship date. The sandbox preview pipeline is the foundation; once it is rock-solid we layer custom domains on top.
Was this page helpful?