Use cases

Run the business

Service desks, internal back offices, order tracking, checklists and dashboards for your team.

Most internal tools are a spreadsheet that outgrew itself. Describe the process instead: who submits, who approves, what each role can see. You get roles, permissions per record and an interface for each of them, and the data stays in your account rather than in someone's downloads folder.

People reach this page looking for

  • build an internal tool without code
  • order tracking app for my team
  • replace an operations spreadsheet with an app
  • back office app with roles and permissions

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.

01

The internal tool the spreadsheet became

The same process, but with roles, validation and a history — and without four people editing the same cell.

02

Order and ticket tracking

Status per record, an owner, a deadline, and a screen for each role instead of one shared tab nobody trusts.

03

Checklists and routines that get done

Recurring tasks, per-shift checklists, and evidence that they happened, attached to the record itself.

04

Dashboards for whoever has to answer for it

Volume, backlog and time to resolve, computed from the operation rather than compiled by hand on Friday.

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.

Describe it in plain language

Say what the app does and what it has to remember. No diagram, no schema, no naming a single framework.

Watch it get built

Screens, data models, login and payments appear while you read. Anything you do not like, you say so and it changes.

Publish, then keep changing it

Live on your domain in seconds, with version history behind you. Tuesday's conversation is Tuesday's release.

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 internal tool for a small workshop. Service orders with customer, description, status, assigned technician and deadline; the customer follows their order through a public link with a code; technicians see only what is assigned to them and can add notes and photos; the manager sees everything, reassigns work and gets a dashboard with open orders, average time to close and late orders.

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.

Kanbo

Productivity

Work management with boards: a table view grouped by section, a drag-and-drop kanban, and analytics across every board.

4 screens

Atrium

Productivity

A staff portal that shows each person only what is addressed to them, and what is waiting on them.

14 screens

Questions

Frequently asked questions

Because a spreadsheet has no roles, no validation, no history and no way to give a customer a link. What starts as one tab becomes six, and by then nobody can say who changed what. The point of moving is not features, it is that the process stops depending on discipline.

Describe it. See it running. Publish it to the store.

Free to start, no credit card. You only pay when you want to publish under your own brand, and you take the code with you if you ever want to.

Build this app freeUse cases