Documentation

You need a Clerk account, a monthly subscription, an idea, and credits. Sign in, subscribe to Spark / Builder / Foundry / Max on /pricing, hit New build, and pick one of the thirteen build types. A new Deep Build is 15 credits; enhance or recorrect is 3–4. Remaining credits stay on the dashboard after you log out. 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.

Submit your prompt and follow the plan, files and source checks in the conversation. When output is available, the workspace shows a preview. Send follow-up edits in the same conversation. Share opens the browser preview; Publish shows hosting or distribution requirements. A generated preview is not proof that an application was deployed or tested in its intended runtime.

Each project type has source checks that inspect generated files rather than trusting the generator's claims. Read the individual results and evidence. The source status is separate from runtime verification, a successful deployment or a native installation.

Source checks examine entry points, file manifests, type-specific structure, preview entry files, run instructions and placeholder markers. Application checks can require installation, compilation, browser interaction or a native runtime. A file existing is not evidence that its code executes successfully.

Inspect PASS, FAIL, BLOCKED and NOT_RUN results in Readiness. A blocked or unexecuted check is not a pass. Fix the reported issue and run the applicable checks before releasing. Preview availability alone does not guarantee functional correctness, security or store approval.

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.

Websites and browser web apps can provide an interactive browser preview. Full-stack apps, APIs, funnels with server-side lead collection and bots need their backend runtime and configuration. Mobile uses Expo, desktop uses Electron, and extensions require installation in a compatible browser. Read the generated README for the actual dependencies and run commands; a simulated preview does not validate those runtimes.

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.

You can export editable source and run it outside Kivlo. Review its dependencies, licenses, configuration and external-service requirements. Source portability does not mean that hosting, backends or developer accounts are included or will remain available 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.

Studio prompts, projects, credits and recorded refinement activity are associated with your account. Production requires durable server storage. Do not include credentials in prompts or project files. Provider processing and data-retention terms need to be reviewed separately; source checks are not a privacy-policy certification.

A build or update failed. Open activity details and Readiness for the recorded error. Web refinements validate a candidate before replacing the working output; if rejected, the previous working version is retained. Do not repeatedly submit an identical billable request to diagnose an error. Contact support with the project ID and redacted error details.

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.

Open /support for build and billing help. Include the project ID from the workspace URL, the expected behavior and redacted error details. Never include passwords, API keys, database connection strings or card details.