Skip to content
Sixerr
Join the waitlist

Technology

Static sites. Served from the edge.

Every site is built from a validated site definition and served as static files from Cloudflare’s global network. Nothing runs when a visitor opens a page.

The path from a short conversation to a live site: a brief, a site definition, a check against our schema, a build, and the edge network that serves it.

  1. Brief
  2. Site definition
  3. Validate
  4. Build
  5. Edge

Describe the business in three short steps.

The model produces one thing: a structured description of your site.

We check it against our schema before anything is stored, rendered or built.

A publish never mixes versions. Every visitor receives one complete build.

Served from Cloudflare’s global network, close to whoever is reading.

  • Cloudflare
  • WordPress
  • GitHub
  • Google
  • Stripe
  • Pexels
  • Astro
  • Amazon SES

Static by design

Files, not a running system.

A published site is a set of files, served from Cloudflare’s network close to whoever is reading. Nothing runs on it, so there is nothing to patch.

An illustration of a global edge network: a globe of fine dots with glowing yellow nodes joined by thin arcs, and a card reading “Static · Served from the edge”

Model output

The AI writes data, not code.

The model produces one thing: a structured description of your site. We check it against our schema before anything is stored, rendered or built.

A Site definition panel at Version 7 with a yellow Validated badge: rows for Hero, Services, Testimonials and Contact holding placeholder fields, beside a grey preview with a Build button

Versions and publishing

Nothing is overwritten.

Each change writes a new version of your site’s description. The old versions stay, which is what makes undo work.

  • A publish never mixes versions. Every visitor receives one complete build.
  • The previous build keeps serving until the new one is complete everywhere.
  • A failed build leaves the live site as it is, and the chat says so.
A Publish card: Build, Upload and Verify checked and Switch in progress, with the note “Version 7 stays live until Version 8 is complete everywhere”

Security and data

Decided on the server.

Domain ownership, plan limits and payments are settled on our servers, never by what a browser or a model asks for. Card details stay with Stripe.

The Security screen on the dark workspace: the domain with CNAME and TXT verified and the certificate active, uploads validated and re-encoded, payments handled by Stripe with no card details stored, and plan limits from the subscription record

Built on

The platforms behind your site.

A short stack, chosen so there is less to go wrong. Each one does a single job.

  • CloudflareHosting, storage, the global edge network, and the certificate for your custom subdomain.
  • AstroThe static site builder that turns your site definition into the files visitors receive.
  • StripePayments and subscriptions. Card details are handled by Stripe and never stored on our side.
  • Amazon SESWaitlist confirmation emails, signup notifications and contact form enquiries.
  • GoogleSign in with Google, as an alternative to an email address and a password.
  • GitHubOn Pro, your exported source can be pushed to a repository you own.
  • PexelsThe stock image library your first draft is built from.
  • WordPressImport an existing WordPress site. Your posts and pages are rebuilt, and you keep your URLs.

Boundaries

Some things are left out on purpose.

Each is a way a website can break or be attacked. Leaving it out removes the problem instead of managing it.

  • No server codeA published site has no server-rendered pages and no per-customer functions. Nothing runs when a visitor opens a page.
  • No code editingThere is no code editor in the product, and no path by which model output becomes code.
  • No pluginsNothing on your published site has to be updated or patched.

Questions

Straight answers.

Help when you need it. Submit a request, follow its status and read a person’s reply in the ticket.

Keep reading

What does static actually mean here?

Your published site is a set of files. No application server, no database and no plugin runs when a visitor opens a page, so there is far less to break, slow down or patch.

Can the AI write code that runs on my site?

No. The model only produces a structured description of your site, and we validate it before use. It is never executed, and no model-written code reaches the template your site is built from.

What happens if the model returns something invalid?

It gets one repair attempt carrying the validation errors. If that fails, the request fails and says so. Nothing invalid is stored, rendered or built, and your site stays as it was.

Do I need a Cloudflare account?

No. You keep your domain, your registrar and your DNS provider, and add two DNS records where they are now. We obtain and renew the certificate.

Am I locked in?

No. On Pro you can download your site as a deployable static archive, download its editable source, or have it pushed to a repository you own.

Waitlist

Your site starts with a conversation.

Join the waitlist. We will email you when it is your turn to build. No card or commitment.