Alan

An AI software engineer who plans, builds, tests and ships real apps, then tells you exactly what he did.

What he does

Plans in the open

Your request becomes a short list of steps you can read before any code is written, updated live as he works.

Works in his own machine

Every project gets a private Linux machine where Alan installs real packages and runs real code.

Tests before he talks

Alan writes his own tests and runs them. A failing test means he keeps working, not that he reports success.

Hands you a live link

When the app is running, you get a link to open it, plus a preview right next to the conversation.

Takes follow-ups

Ask for a change in plain words. He edits the same project, re-tests and restarts it.

Reports what changed

Every delivery comes with what he added, what he did and which files changed, in language anyone can read.

A session, start to finish

  1. 1

    You describe it

    A sentence or a paragraph about what you need. No technical words required.

  2. 2

    Alan plans it

    He breaks the work into steps and shows them to you.

  3. 3

    Alan builds it

    Files, packages and commands appear as he works. You can watch, or step away.

  4. 4

    Alan proves it

    He writes tests and runs them until they pass. Failures and fixes are on the record.

  5. 5

    You open it

    A live link to the running app, with a report of exactly what was done.

  6. 6

    You refine it

    Ask for changes in the same conversation. He picks up where he left off.

Try one of these

Good to know

Who can use Alan?
Alan is in private preview. You'll need an access code to start a build.
What is he best at today?
Small to medium web apps and tools: dashboards, booking pages, trackers, internal tools and simple APIs.
How long does a project last?
Each project's machine stays alive for about 40 minutes, so make follow-up requests in that window. Longer-lived projects are coming.