Export your site or app as a standard Next.js project
Any Anticode build, a page from the design engine or a model-written app, can be downloaded as a complete Next.js project. You get TypeScript, Postgres through Prisma, Zod validation, a server route for every form and an admin area with roles and two-factor sign-in. There's no Anticode runtime in it, so it runs on any Node host.
When you'd want the code
A published Anticode site already handles forms, bookings and submissions for you. The export is for the point where you need what a hosted builder can't give: real customer accounts, your own database, custom server logic, a developer taking over, or simply the certainty that you can leave. The AI website builder code export is the way out, and it's a working app rather than a pile of generated markup.
How to get it
After a build, choose Download codebase from the project's settings (or Download in the project menu). The zip is put together in your browser tab from the template files and your build, and a message tells you how many files it contains and to open README.md. In Pro mode you can browse the same files first in the Code tab, under nextjs-app/. You can also push it to a GitHub repository you choose instead of downloading it.
What's in the project
| Path | What it holds |
|---|---|
| components/sections/ | One typed React component per part of the page (Header.tsx, Hero.tsx, Services.tsx, Book.tsx…), with your words written straight into the JSX |
| app/page.tsx | The sections in order; reorder, delete or add them here. A multi-page site gets one route per page, sharing one header and footer |
| app/globals.css | Your design system as named tokens (background, accent, card radius…), then type and layout |
| lib/site.ts | The site's name, description, font, and the services and times the booking form offers |
| app/api/ | Route handlers for bookings, contact, newsletter sign-up and email sign-in links |
| app/admin/ | The admin area for owners, admins and staff |
| prisma/ | Schema, migrations (tables, then row-level security) and a seed for the owner account |
| tests/ | Unit tests and guardrails |
Apps export too
A model-written app (a game, calculator or tracker) exports onto the same template. Its markup becomes components, its own code moves to lib/app/main.ts and starts once in the browser, and any inline handlers such as onclick are turned into listeners so the app can run under the template's strict nonce-based Content-Security-Policy. Content it read from your CMS collections is saved to content/collections.json, photos and videos you added go into public/media/, and its contact or booking forms post to the project's own routes. This is also how an app gets the real server it couldn't have inside Anticode's sandbox.
Accounts, roles and security built in
- Four roles. Owners can do everything and read the audit log; admins see full booking and message details; staff see them with emails and phone numbers masked; customers sign in by email link and see only their own bookings.
- Two-factor sign-in. Owners and admins must set up an authenticator app before they see any data.
- Validation and CSRF. Every input is checked on the server with Zod, and every POST must come from the same site.
- Postgres row-level security on every table, so a query that forgets a filter returns nothing instead of someone else's rows.
- Headers. A per-request nonce CSP, HSTS, framing protection and
nosniff, plus rate limits stored in Postgres and an append-only audit log. - Email. Booking confirmations and sign-in links go through Resend; without a key, they're printed to the terminal while you develop.
Running and hosting it
You need Node and a Postgres database. The README covers a hosted database from Neon or Supabase, a local one in Docker, and deploying to Vercel or any other Node host. Copy the example environment file, run the migration and seed, and start the dev server; the site and the admin login are both on localhost. The guides to exporting to Next.js and deploying a Next.js app go step by step.
What to expect and what not to
- It's a one-way copy. Changes you make to the exported code don't flow back into the Anticode builder. Edit in one place.
- You run it. Hosting, database backups, email delivery and updates are yours once you leave Anticode's hosting.
- No payments or shop. The template has no cart or checkout. Add a payment provider yourself if you need one.
- Pinned Prisma. Prisma is pinned to version 6; moving to a later major version is a deliberate upgrade.
- Simpler alternative. If you only need static hosting, the single HTML file export is lighter.
Questions people ask
Does the exported app call Anticode at all?
No. There's no Anticode runtime or service in it. Forms post to its own routes and data goes into your Postgres database.
Can a developer change the design easily?
Yes. Each section is its own React component with the words in the JSX, and the palette and radii are named CSS variables at the top of globals.css.
Do I need a paid plan to export?
The download is in the builder after a build. Check the pricing page for what each plan includes.
Will the booking form keep working?
Yes. The booking route accepts only the services and times in lib/site.ts and handles simultaneous requests for the same slot safely. The day picker shows the next six days.