Project templates
Project templates are pre-configured starting points for a new Project. They bundle a coding language, framework, and basic file structure so you don't have to set one up from scratch. Instead of prompting Builder to build an app from nothing, you can start from a template that already matches your tech stack and go from there.
Templates are useful when you:
- Know which framework or language you want to build with (e.g. React, Next.js, Vue)
- Want a working file structure and dependencies in place before you start prompting
- Are building something that follows a common pattern (e.g. a landing page, dashboard, or CRUD app)
Choose a template
You can select a Starter Template only when making your first prompt from the main Projects page:
- Go to the Projects page and start a new Project.
- Before submitting your first prompt, look for the Starter Template picker.
- Choose the template that matches your stack or use case.
- Enter your prompt as usual. Builder will scaffold your app using the selected template as the foundation.
If you skip this step or don't see a template that fits, you can still start from a blank Project and describe what you want to build. Builder will infer the stack from your prompt.
Default template
The Default template is a starter template that goes beyond scaffolding a framework and build tool. It enables agent-native capabilities that aren't available on the four framework templates.
These capabilities include adding an in-app agent, automatic databases, and automatic authentication.
The Default template in the process of being rolled out to all plans. If you do not yet see the Default template, you may not yet have access to it.
Agent
The Default template supports agent-native capabilities, including adding an in-app agent to the application you're building.
When you prompt for an app that would benefit from an assistant, Builder can generate a working in-app agent as part of the build.
Example Prompt
In the video below, a chat agent is added to an application. Builder asks the user some questions to orient itself before building the chat functionality.
Credits and limits
While you're testing an app in the Builder editor, agent usage always draws from your Space's Builder credit pool, regardless of how the published app's agent connection is configured.
Requesting more resource-intensive work from the agent consumes credits faster.
Once you Publish your Project, you can choose how the agent is funded: using Builder-provided credits, using your own model provider API key, or having end users bring their own key or connect their own Builder account.
In any of these funded setups, the agent stops responding once the relevant credit balance or provider budget runs out. If you're using Builder-funded credits, heavy use by your end users can draw down your own credit balance, so it's worth keeping an eye on usage.
Database
The Default template can automatically provision a database when your app needs one. You don't need to connect an external database provider yourself.
When you prompt for a feature that requires storing data, the template determines whether a database is needed and creates one for you.
Example Prompt
You can also prompt for changes to that database over time. Asking the app to store an additional field will update the database schema behind it, without you needing to know the underlying details.
Support for connecting an external database, whether for migrating existing data or starting a new one, is planned but not yet finalized. Compatibility requirements are still being confirmed, so treat this as an emerging capability for now.
Authentication
Apps built with the Default template can add login or sign-up functionality just by being prompted for it.
Example Prompt
Authentication is presented as a managed capability. You don't need to set up a separate database connection or external auth provider.
Builder handles storing user credentials, such as name, email, and password, behind the scenes as part of the same automatic setup.
Framework templates
Builder provides four standard framework templates, one for each major framework. Each pairs the framework with Vite for fast builds and local development, and each gives you a working file structure and dev server out of the box.
- React + Vite
- Angular + Vite
- Vue + Vite
- SvelteKit + Vite
Pick whichever matches the framework you already use, or the one you want to learn. React + Vite is the default if you don't select a template.