Tell it in your own words.
What you want, who it's for and what it has to do. The Tech Lead asks whatever is missing and shows you the plan before touching anything. If there are two ways to do it, it tells you which one it recommends and why.
Cplay Builder
Describe your app.
A team builds it, publishes it and maintains it.
Say what you want in your own words. An AI team —someone who plans, someone who codes, someone who reviews and someone who tests— builds it and publishes it on the internet at its own address. After that, every improvement you ask for is done by the same team. The code is kept in your GitHub account: it's yours, and you can take it with you whenever you want.
Build my first app Free to try · pay only for what gets used
You I want an app so my clients can book an appointment at my hair salon and get a reminder the day before.
TL
Tech Lead Do clients pay when booking or at the salon?Reminder by WhatsApp or by email?
- 💬 Tech Lead read your request and asked two things
- ☰ Drew up the plan: 4 tasks
- ✎ Frontend built the booking screen
- ✎ Backend wired up the reminders
- ✓ Review: approved
- ✓ QA tried 6 cases, all green
- ↑ DevOps published it
- ✓ Done. Yours, in your GitHub
Tech Lead It's live at your-salon.pages.dev. The code is in your GitHub, at your-user/your-salon. What would you like to change?
From an idea to a published app, in four steps.
Connect your accounts.
GitHub, where your app's code is kept with its full history. Cloudflare, where it's published so anyone can open it. One button each; if you don't have them, we take you to create them, and they're free.
The team builds, and checks its own work.
Two developers do the work, a reviewer reads it before signing off and a tester uses it the way a customer would. Nothing reaches your app without going through all three.
Published, at your address.
You get the link and it's already on the internet. From there, anything you want to change, you ask for in the same chat.
And when you want to change something, you just ask.
What sets a team apart from a tool that generates code once is what happens afterwards. You ask for an improvement; the team prepares it as a change proposal —on GitHub it's called a pull request—, the reviewer reads it, the tester tries it, and only then is it merged into your app and published. Meanwhile, the version your customers already use stays up.
- One change at a time, with history. You know what changed, when and why.
- Nothing is published without review and testing. Not even a button.
- It can be undone. Every change has its way back.
Change proposal Add card payment when booking
CR Code Reviewer
Read. Approved.
Read. Approved.
QA QA / Tester
Tested: 5 cases, all good.
Tested: 5 cases, all good.
DO DevOps
Merged and published. Can be undone.
Merged and published. Can be undone.
Who works on your app.
- Plan Tech Lead
- Build Frontend · Backend
- Review Code Reviewer
- Testing QA / Tester
- Publish DevOps
“Done” closes nothing. What one of them does, another reads and a third one tests before it reaches your app. And whoever publishes doesn't publish what didn't go through that.
Tech Lead lead @tech-lead Understands what you ask for, asks the missing questions and splits the work into tasks, each with a “how we'll know it's right”.
Frontend Dev builder @dev-frontend What you see: the screens, the buttons, the forms.
Backend Dev builder @dev-backend What you don't see: where the data is stored, the emails that go out, the payments.
Code Reviewer reviewer @code-reviewer Reads what the other two did before signing off on anything. Approves, or sends it back with a note.
QA / Tester builder @qa-tester Uses the app the way a customer would, case by case, and writes down what happened.
DevOps builder @devops Publishes it on the internet at your address. First it writes down how to undo it if something goes wrong.
Each role is an agent with its own computer and its own browser. They work on the same code, and that code lives in your GitHub repository, not on a site of ours.
Yours. Not ours.
The code lives in your GitHub.
The project is created in your account from day one, not in ours. If one day you want to continue with someone else or on your own, it already has everything.
Published on your Cloudflare.
Your app goes live at your address and in your account. We're not in the middle.
Every change, with a name and a date.
Who asked for it, who did it, who reviewed it and who tested it. And it can be rolled back.
Pay for what gets used. No subscription.
You're charged for the team's real work: what it thinks and the time its computers are on, with a small margin. Every expense is logged with the task that produced it. No subscription and no minimums.
Need something else? Build an agent of your own.
The team that builds your app is made of agents, each with its own computer and a real browser. With those same pieces you can put together your own for whatever you need —comparing prices, watching a site, answering email— and watch it work on screen.
Sign in and create an agent →