Skip to main content

​
How the tech is chosen

When you create a project, Mythex reads your prompt and picks a sensible setup. You can also browse website & app templates on the marketing site for pre-written starter prompts — this page is about which stack the agent uses after you start. Mythex does not ask you to pick React vs Next in a settings screen. It infers from what you write (or from a template’s prompt).

​
Default

If you do not specify a preference, Mythex starts from Vite + React + TypeScript + Tailwind (a live preview is ready while you chat).

​
Prefer something specific?

Say it in the first prompt, for example:
  • “Use Next.js”
  • “Plain static HTML landing page”
  • “Python backend with a simple web front”
  • “C# API” or “Java backend” → Mythex can scaffold and publish via a Dockerfile → Fly (greenfield default is still a modern web app)
You can still ask to change later, but naming a preference early saves credits.

​
Backends via Dockerfile → Fly

For APIs and backends that need a container (for example C#, Java, or a custom Node/Python service):
  1. Ask in chat for the stack you want (e.g. “C# Web API with a Dockerfile”)
  2. Mythex writes the app plus a Dockerfile and records how to run/publish in the project run config
  3. Preview runs in your private sandbox
  4. Publish builds the image and deploys to Fly (same publish flow as static/web apps)
You do not configure Fly yourself — Mythex handles deploy from Publish. Static frontends may publish to Pages instead; container backends use the Dockerfile path.