FAQs

Only questions where a wrong guess would force a rebuild — payments, auth model, tenancy, database needs, and similar high-reversal choices. Copy, colors, and layout preferences become documented assumptions you can correct later.

Ready means your preview shows what you asked for: real copy, working links, and no scaffold placeholders — not simply that processing finished.

Yes. Lock an entire file, a named function, or a specific line range. AI edits that touch protected code pause for your approval before anything is written.

Each project runs in its own cloud development environment. Your codebase is not shared with other customers, and snapshots are saved between edit sessions.

Add keys and secrets on the project. They inject only into that isolated workspace when the preview runs. Platform credentials never mix with yours, and env files are excluded from exports.

Yes. Planning steps, design direction, build progress, and check results stream in the app. The preview opens as soon as the first page is servable.

Curated engineering and design expertise — architecture, security, UI, accessibility, integrations — that attach automatically to the tasks that need them.

Organization-level protection rules that evaluate planned file changes before coding. Violations become approval requests instead of silent overwrites.

No. Visual review surfaces headings, links, and layout issues as findings you can acknowledge or send back as edits. The preview iframe stays open.

Landing pages are single-focus sites. Marketing sites are multi-page brochure sites with shared nav and static export. Software apps — SaaS, internal tools, full-stack, e-commerce — use dynamic previews and fuller validation tiers.

We deliver live previews and static exports. Production hosting and custom domains are your deployment step — not a built-in one-click publish from Codeless IQ today.