A job card with states
Open, awaiting approval, in progress, waiting on parts and finished, with a timestamp on every change. The customer follows it from their phone.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
A quote the customer approves
Parts and labour line by line, sent as a link. The approval is recorded with a date and time, and a new line asks for approval again.
History per vehicle, by plate
Everything ever done to that car, with mileage and parts replaced. It is what answers the warranty question on the spot.
Bay schedule and service recall
How many cars fit in a day, and an automatic notice when the mileage or the interval for the next service comes round.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build an app for an auto repair shop. Customers with one or more vehicles, each with plate, make, model, year and mileage; a job card opened against a vehicle, with the reported symptom, the diagnosis, parts lines and labour lines each with a price; the quote is sent to the customer as a link and they approve or decline line by line, recorded with a date and time, and any line added later goes back for approval; the job card has the states open, awaiting approval, in progress, waiting on parts and finished, with a push to the customer at every change; each vehicle has a full history of job cards with mileage; a schedule with a limit of vehicles per day; an automatic service reminder when the interval or the mileage passes; and a dashboard with open jobs, revenue per month, average turnaround and most-used parts.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.