Stock levels that come from movements
Stock in, stock out, transfers and count adjustments, each with a date, quantity, reason and the person responsible. Each product's balance is calculated from them and never edited by hand.
What gets built
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Stock in, stock out, transfers and count adjustments, each with a date, quantity, reason and the person responsible. Each product's balance is calculated from them and never edited by hand.
Every product has its own minimum. When the balance drops below it, the product joins the reorder list on the dashboard and you are told before the shelf runs empty.
Suppliers with contact details and lead times, purchase orders with items and costs, and receiving an order books the stock in, with a check of what actually arrived.
Shop, warehouse and branch each with their own balance, transfers between them and access by role: sales staff book stock out, the stock keeper receives goods and only you adjust a count.
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 an inventory management system for a building supplies store with a warehouse. Products with SKU, barcode, name, category, unit of measure, cost, selling price and reorder point; two locations, the store and the warehouse, each with its own stock level; movements for stock in, stock out, transfers between locations and count adjustments, each with a date, quantity, reason and the user who made it, with stock levels calculated from them; suppliers with contact details and lead times; purchase orders with items, quantities and cost, where receiving an order books the stock into the warehouse with a check of what arrived; a reorder list with the products below their minimum; stock counts per location that show the difference between the counted and the system figure before adjusting; three roles: sales staff, who book stock out at the store, the stock keeper, who receives goods and makes transfers, and admin, the only one who adjusts counts and sees costs; importing products from a spreadsheet; and a dashboard only I can see, with total stock value at cost, products below their minimum, the month's best sellers and items that have not moved in over ninety days.
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.