Choose by the website job.

Lucra's lane is a focused Studio model where the site remains inspectable through layers, Theme, forms, data planning, review, publishing, and local agent guides.

Choose Lucra when the priority is a simpler Studio surface and a layer model agents and non-engineers can inspect.

Lucra begins where the website needs to become editable, reviewable, and publishable.

Choose Lucra for a sharper page-building workflow with inspectable primitives and Theme discipline.

Lucra fits when the site needs more explicit page structure, review, and agent-readable build rules.

Lucra is a focused Studio for modern marketing pages when a huge plugin system is not the job.

Choose Lucra when the site needs reusable structure, Theme, and guide-readable layers after launch.

Lucra fits structured marketing sites and launches that need a clearer Studio model.

Choose Lucra when the landing page is part of a larger site system the team keeps editing.

Lucra gives AI-assisted work a website surface with layers, Theme, forms, and publishing context.

Lucra guides can teach Codex how to plan Lucra pages today; the Agent API roadmap can make that safer later.

Lucra can expose an agent-readable build contract so generated work fits the Studio model.

Lucra guides help editor agents understand layer responsibility before they propose changes.

Lucra focuses on the page-building surface where the website is composed and reviewed.

Lucra is more relevant when the current problem is the site, the page, and the launch surface.

Lucra is a more focused builder for teams that need modern website creation without DXP weight.

Lucra can use agent guides and later APIs to make generated UI fit an editable website document.