Documentation

Everything you need to know to go from a sentence to a published app.

Overview

ion7 pairs a build agent with a deterministic publish pipeline. You describe what you want; the agent writes real source files, compiles them, and ships the result to a live URL. There is no hidden runtime — everything you get is code you can read.

The build loop

  1. You describe an app in the chat panel.
  2. The agent writes source into a project — routes, templates and data access — and runs the compiler.
  3. A green build is committed. A red build hands the compiler error straight back to the agent, which repairs it and tries again.
  4. You click Publish and the compiled binary ships to the edge.

Every step is visible while it runs: open the details view during a turn to watch the individual tool calls as they happen.

Plan vs Build mode

Plan mode is read-only. It inspects the project and writes a step-by-step strategy without touching any files — useful for big changes where you want to agree on the approach first.

Build mode executes: it writes files, compiles, and deploys to your staging URL. New projects start with a plan, so you always see the shape of the work before it happens.

Runtimes

A runtime adapter is a small interface — a scaffold prompt, starter files, a compile step and a publish step. Registering a new engine is one file.

  • Pascal · Horse · HTMX — generally available, compiled to a static binary.
  • PHP · HTMX — beta, with the common extensions preinstalled.

Views are Mustache templates rather than strings glued together in code, so markup stays readable and editable.

Databases

Ask for persistence and the agent provisions a dedicated database for that project, writes the schema, and wires the queries. There are no connection strings to copy; the credentials are injected into the app at deploy time. Delete the project and its database goes with it.

Preview vs Publish

Every project has two environments. Previews go to a staging URL that refreshes as soon as an agent turn finishes, so you can click through changes before anyone else sees them. Publishing promotes that build to the project's live URL.

The live URL always serves the last published build — an edit you have only previewed will not appear there until you publish again.

Custom domains

Paid plans can point their own domain at a published project. Add the domain in project settings and create the DNS record it shows you; certificates are issued automatically once the record resolves.

FAQ

Do I own the code?

Yes. Every file is real source you can read, browse in the project view, and take elsewhere.

What is a credit?

One agent turn. Planning costs one credit and building costs three. Credits refresh at the start of each billing period.

Why compiled languages instead of JavaScript?

Because compiling is a hard yes/no signal. The agent gets an unambiguous verdict every iteration and repairs faster than a lint-and-hope loop — and the artifact starts in milliseconds.

What happens if I hit my project limit?

Nothing is deleted. Your newest projects become read-only until you remove one or move to a larger plan.

Still stuck? Start a project and ask the agent directly — it can explain its own code.