Documentation

You need a Clerk account, a monthly subscription, an idea, and credits. Sign in, subscribe to Spark / Builder / Foundry, hit New build, and pick one of the thirteen build types. There is no free plan and no API key required.

Describe your idea in plain words. "A habit tracker with streaks and dark mode" is a complete, valid spec. If you want a richer brief, hit the ✨ Enhance button — it works without any keys and turns your one-liner into a paragraph naming likely features, audience, and tone.

Hit Build it real and watch the stream. Every file the generator writes appears in the log as it lands on disk, followed by the readiness checks. When the badge says READY, Kivlo publishes a public live URL you can share — Open live site in the workspace, or Live ↗ on the dashboard. The Preview tab is the studio view; Download ZIP is a backup of the source, not the product.

Most AI generators hand you a folder and hope. Kivlo verifies. Before any project can be marked ready, it must pass a per-type readiness gate — five to seven checks that read the generated files back from disk rather than trusting the generator's claims.

The checks cover the essentials: the entry point exists and is non-trivial, the file manifest is complete, the type-specific structure is valid (a Next.js package.json with its start script, an MV3 manifest that still parses, real PNG icons for extensions, a Prisma schema when persistence was requested), the preview renders, the README documents how to run the download, and a placeholder scan confirms nobody left TODO markers in shipped code.

If any check fails, the project is marked failed — visibly, with the failing check named. Kivlo never quietly ships something broken as ready. You can watch every check run in the build stream, and the Readiness tab keeps the evidence after the fact.

Every build type is a distinct pipeline with its own generator, readiness checks, and preview — not one template wearing thirteen hats. The interactive explorer on the home page shows the exact file list each type produces; here's the short version of what makes each one real.

The instant types open the moment you download them: Website, Web App, Game, Email Template, and Landing Funnel are single-file or few-file builds with zero dependencies. The install types need one command first: Full Stack (Next.js with API routes — npm install && npm run dev), Mobile (a real Expo project — scan the QR with Expo Go), Desktop (Electron with security defaults), API Backend (an Express server with seven REST endpoints and curl docs), CLI Tool (a zero-dependency Node command), Discord Bot (discord.js v14 with slash commands), and Component Library (typed React with a strict tsconfig).

The Chrome Extension deserves a special note: it's a complete Manifest V3 package with a popup, options page, service worker, content script, and real PNG icons rendered from your project's palette. Load it unpacked in about thirty seconds.

The code Kivlo generates is yours. The download is a plain project folder — no Kivlo runtime, no phone-home, no license key baked into the files. Delete your account and the ZIPs you already downloaded keep working forever.

Generated projects are yours to ship, sell, or learn from. We don't claim rights over output. The hosted live URL shows a small Built with Kivlo chip; the ZIP is unmarked besides a README credit line.

Your data in the studio — prompts, projects, refinement history — is stored in the studio's local data store and is never used to train anything. Export it or delete it any time from the dashboard.

A build finished as failed. Read the Readiness tab — the failing check is named with its evidence. The most common cause is a refinement that asked for something the template couldn't validate (say, edited JSON that stopped parsing); the surgical AI layer falls back to the template version for any file that fails validation, so the failure is always recoverable by re-running.

The preview is blank or stale. The preview tab loads the project's real entry file in a sandboxed frame; multi-page sites rewrite their links so navigation works inside the frame. If a preview looks wrong after a refinement, use the reload button on the preview chrome — it re-fetches the current files.

Where do I report things? The studio is in active beta — every build keeps its full event log, so attaching the project ID (visible in the workspace URL) with a description of what happened is usually everything we need.