Start with the infrastructure already in place

A BuildPad project is a connected development environment, not an empty repository. The backend, starter and path to production are set up, so you start by building.

Integrated Application Infrastructure

What a new project ships with

  • A DaaS backend per project
  • Git repository and remote set up
  • AWS Amplify pipeline connected

Connected at project creation

What a project gives you on day one.

Three pieces of setup, done before your first feature.

Backend

One DaaS backend per project

  • Each new project gets its own DaaS backend
  • Collections, fields and relations ready to use
  • Roles, policies and permissions included
  • The Main App and its microapps share one data model
Data ModelDaaS Studio
FieldType
reference
string
event
uuid
seats
integer
status
string

Fields map to real database column types, and relations are resolved by the backend.

Context

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
  • The assistant reads your real schemas, no guessing
AI IDE Setup4 editors

A starter project for your editor, pre-loaded with your project credentials and MCP connections.

Shipping

Source control and deployment already wired

  • A Git repository with its remote set up
  • An AWS Amplify app connected to it
  • Amplify builds on every merge to main
  • The amplify.yml build file sits in the project root
mainSucceeded
Merge to mainamplify.yml
Provision
Build
Deploy
Amplify watches the main branch.

What the backend already covers.

More than storage, so your app grows past CRUD screens without a new service for each need.

Main App and microapps

REST API

One BuildPad DaaS backend

Access

Who can reach what

  • Roles
  • Policies
  • Permissions
  • Item filters
  • Server-side validation
  • File permissions
If allowed

Data

The shape of the app

  • Collections
  • Fields
  • Relations
  • Files
  • REST APIs
  • Relation-aware data
On change

Logic

What the data does next

  • Workflows
  • Event hooks
  • Cron jobs
  • State transitions
  • Scheduled tasks

Logic also starts inside the backend, so scheduled work runs with no client.

From project creation to production.

Five stages, all on the environment BuildPad sets up.

  1. Create the project

    BuildPad provisions a DaaS backend and one place to manage the Main App, its microapps and any workers.

  2. Download the starter

    Pick your AI IDE. Its starter has credentials and MCP connections filled in, so the assistant reaches your real backend.

  3. Build against real context

    Work in feature branches. The AI sees your collections, the component registry and the project, so its code fits.

  4. Merge to main

    Test locally, review in source control and merge, like any other code.

  5. Amplify builds and deploys

    Amplify picks up the merge, runs the project's amplify.yml and publishes the new version.

Want to see this in a real app?

We show you this part working end to end, in an app we have built.