Describe the idea. Keep the code.
Turn a plain-language brief into working software that you can edit, export, and deploy.
A Claude Code session: you ask for a climbing-gym booking app, it creates a Pylon project, declares the entities and policies in app.ts, writes the functions and the routes, checks it with zero errors, and deploys it to a live URL.
No files yet.
- Normal source code
- The generated project is yours to edit and extend.
- Git ready
- Connect a repository or download the project.
- Local editing
- Open the same project in your own editor.
- Cloud deploys
- Use the shared account and organization control plane.
From brief to working project
Build starts the project. You keep working on the source with the tools you already use.
Describe the workflow
State the users, the data, and the access rules in plain language. Build reads the brief and plans the project.
A booking app for a climbing gym with member passes and waiver signing.
- Usersmembers, staff
- DataMember, Pass, Waiver, Booking
- Access rulesstaff desk, own bookings
Review real code
The data model, access rules, server logic, and interface land in one TypeScript project you can read.
import { entity, field } from "@pylonsync/sdk" export const Member = entity("Member", { name: field.string(), email: field.string(), waiverSigned: field.bool().default(false),}) export const Pass = entity("Pass", { memberId: field.string(), visitsLeft: field.number(), active: field.bool().default(true),})Choose the next step
Keep going in Build, open the project in your editor, connect git, or download the source.
- Open in your editorCursor, Claude Code, VS Code, or any editor
- Connect a repositoryPush to GitHub or GitLab
- Download the sourceclimbday.zip · 2.1 MB
main · 3 commits · 2 minutes ago
Deploy through Cloud
One command moves the project to managed hosting under the same organization.
$ pylon deploy
Building climbday for production… 0.8s
Provisioning server, database, auth, TLS… 1.6s
✓ climbday.stack0.app
330 edge cities · 2.4s total
- Deploy #14main · fix: handle duplicate waivers2.4s
- Deploy #13main · add staff desk2.6s
The result is more than a prototype
Build connects the core application layers, so you can start with a working project.
Data model and application code stay together
Entities, relationships, server functions, and pages live in the same TypeScript project.
Access rules are part of the project
Authentication and row-level policies are generated with the data model.
Export at any time
Download the source and continue without the Build interface.
Deploy through Cloud
Move from the builder to managed hosting under the same organization.
Build and Cloud have different jobs
They share accounts, organizations, and project infrastructure. They remain separate Stack0 products.
- 01
Build creates and edits the project.
- 02
Cloud deploys and operates that project.
- 03
An existing project can skip Build and go directly to Cloud.
Start with the application, not the setup
Describe the first workflow. Keep every line that Build creates.