Publishing always requires an account — a live site needs a real owner. This guide covers what that gate actually requires, the pre-publish checklist, and exactly what changes the moment you go live.
aiKit is built value-first: you see a complete, real draft — and get to revise it — before ever being asked to sign up. The screen itself says it directly: "You've already seen your draft and refined it — all of it free, with no account. A live site needs a real owner, so this is the step where you claim it," with a note explaining the reasoning: people commit after they've seen value, not before.
This screen only appears if you haven't already made an account by this point. Starting a second project, or opening your Projects list, asks for one earlier; if you signed up at either of those, publishing skips straight past this step.
Just an email field and a password field (at least 8 characters), with a single "Create free account →" button. A reassurance line stays under the button: "Free to create. No credit card until you choose to publish & host."
Before you go live, aiKit shows exactly what's still sample content — a warning banner reads "⚠ N of M sections still need your review before this goes live" if any remain, and every section of your draft is listed individually with a ⚠ ("Still showing sample content — replace it before people see this") or a ✓ ("Real content — ready to go").
This is informational, not a hard gate — a note right below it says so explicitly: "Creating is never blocked — the sample flags above are informational, and the call is yours." You can publish with sample content still showing if that's genuinely what you want to do.
Your project's live address is shown as a fixed "/s/" prefix plus an editable slug field (lowercase letters, numbers, and dashes only), with a "Save address" button that only enables once you've actually changed it. A note clarifies this is a real, working address today — a custom subdomain of your own is on aiKit's roadmap but isn't available yet, so every published project currently lives at that shared /s/ address.
Clicking "✨ Start creating →" sets your project's status to live immediately — there's no manual review step and no DNS wait. While it processes, you see a short sequence: "Assembling your site…", "Wiring up every checked feature…", "Making it live…", "Almost there…". Once it's done, the screen changes to "You're live," showing your project name, a live link that opens in a new tab, and a green "🟢 Live" badge.
From there you get two direct sharing actions: "Copy link" (copies your real URL, with a "Copied!" confirmation) and "Email it" (opens your email client with the subject and a link already filled in, ready to send to a client or collaborator).
Your sections, in your chosen style, plus a 'What's included' band if you selected any features, plus a live feedback widget for visitors, plus the 'Built with aiKit ∞' badge that's part of how the free tier is funded. If your project included operational screens (for an app, admin system, internal tool, or client portal), the marketing page shows a clearly labeled "Open" card for each one instead of the screens themselves — clicking it goes to a real, separate app address (e.g. `/s/your-slug/app/internal`), with its own sidebar navigation grouped by role and no marketing header, hero, or footer around it. A project with more than one operational surface (say, an Internal Tool AND a Client Portal) gets one card and one address per surface, since those are genuinely different products for different audiences. Every individual screen also has its own real, shareable URL inside that app address, so you can link a teammate straight to one board or record instead of describing how to find it.
Table and record-detail screens (a customer list, a job's own record, a list of tasks) are genuinely functional, not just a mockup: an "Add" button, an edit pencil, and a delete control let you add, change, and remove real rows and records, backed by real storage — reload the page and what you added is still there. The very first time you open one of these screens, whatever sample data the AI drafted becomes your real starting records, so you're editing something real from the start instead of an empty screen. Only your project's own members can add, edit, or delete — anyone else viewing your published site (or its app address) sees the same data read-only. Kanban boards, dashboards, calendars, and activity feeds are still display-only previews for now — real editing on those is on the roadmap, not built yet.
Have a quicker, specific question instead? Check the FAQ.