Only you will use Build
Choose Personal. You can use it to build paid client websites and business apps. Personal describes a single local user; it does not mean your work must be noncommercial.
The app runs on your computer. Connect a model in Settings → Models and start a project. You do not need Clerk, a Cloudflare account, a domain, or billing setup for this local workflow.
You’re ready to continue when: You can open Build locally and create a project without a sign-in screen.
Your team needs separate logins
Choose Agency. This applies to employees and contractors, even if your clients will never use the builder. Each person gets their own identity and workspace membership.
Agency setup uses Clerk for sign-in and your Cloudflare account for hosting. Your agency provides the model API credentials. Choose manual billing if you are managing access internally or collecting payment elsewhere.
Clients will use your builder
Choose Agency. Set up your installation, become its administrator, create workspaces, assign plans, and invite each client using their own email address.
Online subscriptions are optional. Manual access can be managed without Stripe. Build usage still consumes your provider and hosting resources.
The builder and the websites are separate
Hosting Build lets people use your AI builder. Publishing a finished website lets visitors use that website. They are two separate deployment steps.
A 127.0.0.1 or localhost link only points to the current computer. It is useful for local work, but it is not a link your team or clients can open remotely.
Tell your coding assistant what you need
Read AGENTS.md and docs/INSTALL.md before changing this Build installation. Help me choose a setup based on who needs access: just me, my team with separate logins, or clients with separate logins. Ask whether we need to edit the same projects. Explain the collaboration limits of my downloaded version. Preserve existing data and credentials. Then guide me through the correct setup one step at a time.