Free while in beta

Describe an app. Get a working one.

Tell it what your business does. You get a multi-page application with navigation, roles, forms, tables and dashboards — backed by a real database, not a prototype. Keep chatting to change it; every version is saved and reversible.

Free while in beta
Try one
  • Multi-page
  • Roles and permissions
  • Real Postgres records
  • Undo any change

From this prompt

Create a booking application for a beauty clinic. Customers can browse treatments, select a staff member, choose an available date and time, and create a booking. Admins can manage services, staff, customers, and bookings. Show today's bookings, monthly revenue, and popular services on the dashboard.

To this application

entities
4
pages
15
roles
3
revenue dashboard
1

In under a minute.

How it works

Three steps, and the second one is watching.

  1. 1

    Describe it

    Create a booking application for a beauty clinic. Customers can browse treatments, select a staff member, choose an available date and time, and creat…”

  2. 2

    Watch it build

    • planning
    • generating
    • validating
    • saving
    • rendering
  3. 3

    Change it by chatting

    “Add a cancellation reason to bookings”

    Version 3 saved. Your data is untouched.

What you get

An application, not a screenshot.

Everything below comes out of one paragraph of description.

Multiple pages and navigation

A dashboard, list and detail pages, and forms — wired together with a sidebar, not a single scrolling mock-up.

Roles and permissions

Say who may see what. Permission checks run on the server for every read and write, not just in the interface.

Real records, kept

Every entity is backed by Postgres. Create a booking, close the tab, come back next week — it is still there.

Tables and forms that work

Search, filter, sort and paginate. Forms validate on the type of each field, and tell you what is wrong.

Every change is a version

Undo a change you did not like. Restore last Tuesday. Your data is untouched by either.

Publish in one click

Share a working link with a colleague. Unpublish just as easily when you are done.

Why it is reliable

The AI writes a specification, not code.

Every application is one validated document. That is why a change can be previewed, versioned, undone and restored — and why “make the buttons green” can never break your bookings.

app.spec.jsonValidated
{
  "entities": [{
    "id": "bookings",
    "label": "Booking",
    "fields": [
      { "name": "customer", "type": "relation" },
      { "name": "scheduled_at", "type": "datetime" },
      { "name": "status", "type": "select",
        "options": ["Pending", "Confirmed"] }
    ],
    "permissions": { "delete": ["admin"] }
  }]
}

Being straight with you

What it does not do yet.

You will find this out in ten minutes anyway. Better you hear it now.

  • Your app's own end-users cannot sign in yet — you preview as any role you defined.
  • No payments or outbound email from generated apps yet; workflows describe them but do not deliver.
  • Published apps live on a shared builder URL. Custom domains are next.
  • No source-code export yet.

Questions

Things people ask before they start.

Do I need to know how to code?

No. You describe what the tool should do, in the same words you would use to explain it to a colleague. If you can write a paragraph about your business, you can build with this.

Is the data real, or a preview?

Real. Every record you create goes into Postgres, scoped to your application. The demo above is a genuine app running on genuine rows — create something in it and refresh the page.

What if the AI changes something I liked?

Every generation is saved as a numbered version. Undo moves you back one; restore takes you to any earlier version. Neither touches the records your app has collected.

Can I export the code?

Not yet. Your app is a validated specification document rather than a pile of generated files, which is exactly what makes versioning and undo reliable. Generating a conventional codebase from that specification is on the roadmap.

What does it cost?

Nothing while we are in beta. No card, no trial timer. When we do charge it will be for usage beyond a generous free tier, and we will tell you well before it applies to you.

What do you want to build?

One paragraph is enough to start. Free while in beta.