Build platform
Q-Code is a platform that builds a complete website from a written brief and publishes it to a domain you own.
You describe what you want in plain English. It writes the pages, the components, the structured data and the admin area together, shows you a private preview, and publishes only when you say so. What you get is ordinary static files on your own domain, with the code in your own repository.
You write
A one page site for a plumber in Luton. Services, prices, a contact form, and reviews from customers.
It writes
Preview readynothing live until you say so
The loop
Nothing reaches a visitor because a build finished. Publishing is always a separate thing you choose to do.
01
No brief template, no specification document. "A one page site for a plumber in Luton, with a contact form and prices" is enough to start. Short requests are the normal case and the platform is built to expand them rather than send them back.
02
Before touching a file the agent says in one line what it understood you to mean. If that line is wrong you have lost a sentence, not an afternoon. Then it writes the pages, the components and the structured data together.
03
Every change lands on a private preview build first. The live site keeps serving the last published version until you say otherwise, so nothing reaches a visitor because a build finished.
04
One action puts it on a real domain with a certificate, a sitemap, and a copy pushed to your own GitHub repository. The published site is static files on a global network, so it stays up whether or not the builder is running.
Measured, not claimed
Every figure here came from a run that was recorded at the time. There are no customer counts on this page because this platform has one user, and inventing the rest would make the honest numbers worth less.
Costs are broken down on what it costs.
As standard
These are not add-ons or an upgrade tier. They are in the template, so the first build has them and no site is ever missing one because nobody thought to ask.
Titles, descriptions, Open Graph cards, canonical links, a sitemap, structured data and an llms.txt summary, generated from the site rather than bolted on. Search engines and answer engines are both first-class readers.
Testimonials, questions and answers, your enquiry inbox, social links and the posting schedule, each with its own panel. Content edits are database writes: about a second, no rebuild, nothing spent.
Submissions land in an inbox on the site, with spam traps that answer politely and store nothing. Replies are sent from an address on your own domain, not from a shared one.
Ask for a post and get a finished one: researched against the site, written to a fixed style contract, illustrated, checked, and held as a draft until you publish it. Or set a schedule and let it run.
Bring a domain you own, delegate it, or keep your DNS where it is and add the records the panel gives you. All three are supported, and the panel never sends you to a dashboard to work something out.
Semantic landmarks, one main heading per page, visible focus, enforced alt text, contrast-checked colour, and images that reserve their space so nothing jumps as the page loads. Checked on every single build.
Suited to
Content sites, where the words and the structure are the product. It is not a general application framework, and saying so is more useful than pretending otherwise.
The most common job and the one the template is shaped around. A handful of pages that answer what you do, where, for whom and at what price, with a form that reaches you and opening hours a search engine can read.
For a business whose offer changes faster than its website usually does. The pages are code, but the words on them that move most often are data, so keeping them right does not need a developer or a deploy.
A blog with a schedule, images, categories and a feed. Posts are written to one style contract so the tenth reads like the first, and every post carries the markup that lets it be quoted rather than just crawled.
One page, one job, and every mechanism search and answer engines use to decide whether to show it. Answer-first paragraphs, a clean heading outline, and a page that is complete in the HTML before any script runs.
Questions
Q-Code.ai is a platform that builds and publishes websites from a written brief. A build agent reads the brief, writes the site from a shared Astro template, runs the build, and deploys the result to Cloudflare Pages — end to end, without a person editing the code or running the deploy.
dev.q-code.ai is the first website the Q-Code.ai platform built and published on its own. It is a proof of concept: its job is to demonstrate that the whole chain — brief, agent, template, build, deploy, custom domain — works unattended.
A Q-Code.ai build agent running as a long-lived service on Fly.io. It picked up the brief in its own project workspace, produced the pages, and published them to Cloudflare Pages using a scoped deploy token. No human wrote the markup or triggered the release.
Astro 7 for static output, Tailwind CSS 4 for the design tokens, and React 19 for interactive islands where a page genuinely needs them. Every colour, typeface and radius comes from a single theme file, so the whole site rebrands from one place.
Yes. Every page is pre-rendered to static HTML at build time into a dist/ folder, then served from Cloudflare Pages. There is no server rendering at request time and no database, which is why the site is fast and cheap to run.
Yes. The robots.txt file explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended and the other major AI crawlers, and /llms.txt tells a language model which pages matter and what the site is about. Nothing here is behind a login or rendered only by JavaScript.
More on the questions and answers page.
There is no brief template to fill in and nothing to install. If the reading is wrong you have lost a sentence, and the preview is there so you see it before anyone else can.
Three fields. It reaches the owner directly and gets a reply by email.
★★★★★
“They rebuilt our site and the contact form actually works now. Two new clients found us in the first month.”
Priya Raman · Owner, Raman Bookkeeping
“Straightforward to deal with and the site was live inside a fortnight. Enquiries come through properly now.”
Tom Beckett · Beckett Joinery
★★★★★
“Booking enquiries come straight to my inbox now instead of getting lost. Setup took an afternoon.”
Helen Kirkby · Kirkby Veterinary
Machine-readable versions of everything above:the llms.txt summary for language models,the XML sitemap, andthe robots.txt crawl permissions.