Loads with pickup, delivery and statuses
Customer, origin, destination, cargo, rate, driver and vehicle, with the statuses picked up, in transit, delivered and exception updated by the driver from the phone.
What gets built
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Customer, origin, destination, cargo, rate, driver and vehicle, with the statuses picked up, in transit, delivered and exception updated by the driver from the phone.
At delivery, the driver records who received it, a photo of the cargo and a signature on the screen. The proof stays on the load, and the customer is notified straight away.
A link per load shows the customer its statuses and the last position the driver recorded, with no account needed. One customer's link never opens another customer's load.
Vehicles with plate, documents and renewal dates, plus fuel, tolls and maintenance logged per trip. The report shows revenue, cost and margin for each route and each truck.
Included
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
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.
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.
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.
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.
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
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
Three steps, and the second one is the one people do not believe until they watch it.
Start here
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 a system for a haulage company with eight trucks running loads between cities. Customers with contact details and pickup addresses; vehicles with plate, model, capacity and documents with renewal dates for registration, insurance and inspections; drivers with driver's licence details and expiry date; loads with customer, origin, destination, cargo description and weight, rate, planned pickup date, driver and vehicle; load statuses updated by the driver from the phone: awaiting pickup, picked up, in transit, delivered and exception, each change recording the time and location; proof of delivery with the name of who received it, a photo of the cargo and a signature on the screen; a tracking link per load so the customer can follow it without creating an account, with an email at every status change; expenses per trip for fuel, tolls, driver allowance and maintenance, with a photo of the receipt; three roles: driver, who sees only their own loads, dispatcher, who creates loads and assigns drivers, and admin; an alert for documents expiring in the next thirty days; and a dashboard only I can see, with today's loads by status, revenue and cost for the month per truck, margin per route and open exceptions.
Ready to start from
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
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.