---
title: "How Evonx works"
description: "Follow one request end to end - from your first prompt through the Evolution Thread, live preview, and a published app."
url: https://evonx.ai/docs/get-started/how-evonx-works
locale: en
updated: 2026-09-04
---

# How Evonx works

Follow one request end to end - from your first prompt through the Evolution Thread, live preview, and a published app.

The best way to understand Evonx is to follow a single request through the whole
system. Here's what happens between "I need an app for my auto-service shop" and a
running app your team signs into — and where you stay in the loop.

## 1. You describe, Evonx decides how to build

Everything starts in chat. When you send your first request, Evonx analyzes the
intent and picks a starting shape:

- A brand-new custom idea becomes a **greenfield custom project** — Evonx scaffolds
  a web app repository and an API repository with a database.
- A need that matches the catalog (bookkeeping, CRM, inventory, appointments,
  service) starts from a **template** with a managed backend.
- An imported GitHub repository is treated as an **existing project**: Evonx maps
  the codebase first, then changes it.

Your project lives in real repositories from the first minute. You can see the code,
and you own it.

## 2. Bigger changes run as Evolution Threads

A meaningful request — "add job photos", "let customers book online" — becomes an
[Evolution Thread](/docs/evolve/evolution-threads). The thread moves through stages
you can watch and steer:

1. **Plan.** The AI breaks your request into concrete steps and decides which
   repository each step touches.

2. **Design.** For visual changes, it generates
   [mockups](/docs/evolve/design-and-mockups) first. Nothing gets built until you
   approve the direction.

3. **Execute.** The AI writes the code in an isolated workspace, splitting work into
   verified steps — each one [tested](/docs/evolve/automated-testing) before the
   next begins.

4. **Publish.** Finished changes arrive as pull requests. You review, merge, or
   reject. See [Publishing changes](/docs/evolve/publishing-changes).

## 3. You verify in a live preview

At any point you can run your app in the
[Preview Hub](/docs/preview-and-debug/preview-hub). A preview is a private, isolated
deployment: web apps get a URL and a QR code for your phone; APIs get their own
temporary Postgres database with migrations applied and example data seeded.

If a preview fails to start, [Analyse & Fix](/docs/preview-and-debug/analyse-and-fix)
reads the logs, explains the root cause, and can apply the fix.

## 4. You publish, and Evonx keeps it running

When the preview looks right, you
[publish to an Evonx address](/docs/launch/publish-to-evonx) — or attach
[your own domain](/docs/launch/custom-domains). Published apps get versions with
rollback, a [managed database](/docs/launch/managed-database) you can browse, and
[monitoring](/docs/launch/monitoring).

## Where you're always in control

Three rules hold across the whole loop:

- Nothing user-facing ships without passing through a preview you can open.
- Code changes reach your repositories only as pull requests you approve.
- AI work consumes credits transparently — see [pricing](/pricing) for how plans
  and credits work.

## Next step

Ready to try it? Start with
[Create your account & workspace](/docs/get-started/create-your-account), then
[build your first app](/docs/get-started/build-your-first-app).