Ship the product, not the demo.
Auth, database, roles and deployment are there from the first prompt — a React frontend on a Python backend with its own PostgreSQL. Tested before every release, and the code is yours to take with you.
A prototype does not survive your first ten customers
Prototype-first tools get you to a convincing screen fast. The trouble starts on the day someone logs in, pays, or asks where their data is — because that is a backend question, and a prototype does not have one.
Airbuild generates the whole thing at once: interface, Python API, PostgreSQL schema with real constraints, authentication and roles. What you demo on Friday is what runs on Monday, and it keeps running once the tenth customer arrives.
What you get from the first prompt
The weeks normally spent on setup, before any of your product exists.
Full stack, not a front end
React and FastAPI with a managed PostgreSQL — foreign keys, constraints, Decimal money, UTC timestamps — plus authentication and team roles.
Tested before it ships
Tests are generated alongside the code, and a security and quality gate runs on every publish. High-severity findings block the release rather than reaching your users.
No lock-in at the raise
Standard exportable code, your own GitHub repository, self-hostable. Nothing about the application depends on us still being in the picture.
Idea to running product
The same four steps for the MVP and for everything you add after it.
Describe it
Write down what the product does — or bring notes, a spreadsheet or an existing spec and let Airbuild read them.
Review the plan
Data model, screens and API surface are laid out before a line is written, so corrections are cheap.
Generate and test
Frontend, backend and database are built together, with tests, and build errors are repaired as they appear.
Publish and iterate
One click to your own domain. The next change takes the same path and lands as a real Git commit.
What you keep when you outgrow us
The question every founder should ask a builder tool before committing to it: what exactly do I walk away with?
- Standard React and Python you can run on your own infrastructure
- Your own GitHub repository, with the full commit history
- An export of your application database on request
- EU hosting with EU data residency, GDPR-native
- Free to start: 250 AI Tasks in your first month with a business email address
Questions founders ask
How much can I actually build on the free plan?
On the free Airbuild plan you can finish a real project rather than only try one: 250 AI Tasks in your first month when you sign up with a business email address, with no daily limit inside that window. Freemail signups start with 50 and can ask for more directly in the chat. After the first month every free account continues with 25 AI Tasks a month. An AI Task is a completed generation, not every small edit.
What happens when we hire our first engineer?
When you hire your first engineer, they get a normal repository with normal code: React on the front, FastAPI and PostgreSQL behind it, migrations included. If you have connected your own GitHub repository — Website Builder Pro and above — changes are committed and pushed there automatically, so the codebase already lives outside our infrastructure on their first day.
Can we take payments?
Yes, an Airbuild application can take payments. A Stripe checkout is generated on request as part of the application, the same way authentication and roles are. It runs on your Stripe account with your keys, which are stored as encrypted environment variables per deployment target and never appear in the generated source.
Is the generated code good enough to raise on?
The code Airbuild generates is production-shaped and good enough to raise on: a real PostgreSQL schema with constraints, tests generated alongside it, and a security and quality gate on every publish. What the gate does not prove is that your authorisation rules are right — who may read which record is your own application logic, so budget a review for sensitive data before you scale.