Start with the infrastructure already in place
A BuildPad project is a connected development environment, not an empty repository. The backend is provisioned, the starter carries your project context, and the path from code to production is wired. You start by building, not by assembling services.
- A DaaS backend per project
- Git repository and remote set up
- AWS Amplify pipeline connected
What a project gives you on day one.
Three pieces of setup work are done before you write your first feature.
One DaaS backend per project
- Creating a project provisions its own DaaS backend
- Collections, fields and relations are ready to use
- Roles, policies and permissions come with it
- The Main App and every microapp share one data model
Fields map to real database column types, and relations are resolved by the backend.
A starter that already knows the project
- Starters for Claude Code, Copilot, Kiro and Antigravity
- Project context and backend connection filled in
- MCP connections configured for you
- The assistant reads your real schemas instead of guessing
A starter project for your editor, pre-loaded with your project credentials and MCP connections.
Source control and deployment already wired
- A Git repository with its remote already set up
- An AWS Amplify app connected to that repository
- Amplify watches the main branch and builds on merge
- The amplify.yml build file ships in the project root
What the backend already covers.
DaaS gives an application more than storage, so it can grow past simple CRUD screens without a new service for every requirement.
Who can reach what
The shape of the app
What the data does next
Logic also starts inside the backend, so scheduled work runs with no client connected.
From project creation to production.
Five stages, each one carried by the environment BuildPad sets up for you.
Step 01 of 05
Create the project
Create a project. BuildPad provisions a DaaS backend and gives you one place to manage the Main App, its microapps and any workers.