Skip to content
How it works · beta

The AI writes a document, not your site's code.

The AI never writes your site's code: it writes a document and a stylesheet, and fixed code renders them. Content and design enter only through those two files. A custom app is the one exception: it is written inside its own module, checked against the module contract and tested in a sandbox before it ships.

  1. 01BriefChat and question cards
  2. 02Documentspec.json and one stylesheet
  3. 03RenderA fixed template, the same files every time
  4. 04HostingUpload to cPanel or FTP
  5. 05VerifyChecked on the preview address
  6. 06PublishThe verified build goes live
ONE DOCUMENT, ONE STYLESHEET

The AI fills a form. It does not write the program.

The document says what the business is, what the pages say and which blocks appear. It is validated before anything renders. The stylesheet comes from a separate, guarded step.

// spec.json, an illustrative excerpt
{
  "business": { "name": "Example Bakery", "language": "en" },
  "pages": [
    { "slug": "home",
      "blocks": ["hero", "team", "bookings"] }
  ]
}
1:1

Byte-identical builds.

Two builds of the same document produce the same files, byte for byte. A round-trip test runs on every change to the builder.

AA

A contrast gate that fails closed.

Every render is checked against WCAG AA contrast. If a colour pair fails, the build stops instead of shipping it.

APPS

Apps, inside a fence.

When a site needs more than pages, the app is built as a module of the site. It runs on the same hosting, in the same plain PHP, with its own admin pages.

  • Its own module. A custom app is written only inside its module folder and its migrations, never in the site's core.
  • Checked against the module contract. Routes, permissions and migrations come from a validated descriptor.
  • Tested in a sandbox. The app runs against a throwaway database with synthetic data before it ships.
  • Ready-made modules. CRM-lite and the Telegram notifier are switched on from the chat.

Three Build Modes, one rule: the price follows the mode.

Build ModeWhat does the workToday
SiteBuilderSingle model calls from our server, no agent sessionAbout 5 minutes from brief to preview
WebDeveloperA designer in a sandbox; a planner, an implementer and a reviewer for appsAvailable in the beta
Dev TeamA full development teamPlanned

Every run shows its price before it starts. A project never borrows a role from a more advanced Build Mode unless the client chooses it.

ON NULA7'S SERVER

The builder

  • Chat, question cards, preview
  • The document and the stylesheet
  • Rendering, upload and verification
  • Consoles for hosting companies, clients and developers
ON YOUR HOSTING

The site

  • Plain PHP 8.3
  • MariaDB, or SQLite on FTP-only hosts
  • Its own admin panel with a Download-backup button
  • Its apps, as modules
  • Keeps running if the builder goes away

Honest limits.

  • Tested on JetHost's cPanel and on FTP hosts. Not on every host.
  • The builder is a beta. We need real users building real sites, breaking it and reporting.
  • Pricing is not decided.
  • Imports, a site from your URL and the WordPress path are on the roadmap, not in the product.

What we promise next, and what we don't yet.