Projects
Each project is an isolated runtime of the same app: its own database and files. Use a separate project per client, or for staging vs live-style boundaries. Building changes the shared blueprint; data does not automatically copy between projects unless you import or seed it. Creating and switching projects is mostly UI. Ask Build when you need seed data or project-specific overrides:Create a staging project for dry runs. Keep production data in the live project. Do not copy customer rows between them unless I ask to import or seed.Switch projects from the project switcher in the app. Tables, Files, End-Users, and Chats always refer to the project you have selected. Preview as a role in each project you care about. A blueprint Publish can affect both projects’ recipe while data stays isolated. Each new project starts with Public Project on and a neutral platform Slug (for example
quiet-moonstone.genieforge.ai) that you can rename in Project Settings. That slug is independent of the project display name. Turning Public Project off stops the slug subdomain and custom domains from resolving; the builder portal path for the project still works.
Custom domains and branding overrides are per project. See Custom domains.