Bills and receivables with due dates
An entry with amount, due date, category, supplier or client and payment method. Recurring for rent or subscriptions, split into instalments for purchases paid over time.
What gets built
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
An entry with amount, due date, category, supplier or client and payment method. Recurring for rent or subscriptions, split into instalments for purchases paid over time.
Today's balance plus everything due over the next thirty days, day by day. The day the cash goes negative shows in red before it arrives.
Every entry has a category and, if you want, a cost centre or project. The month's report shows where the money went and which part of the business makes a profit.
A receivable becomes a payment link for card or local payment methods, and a confirmed payment marks it paid on its own. Anything paid outside the app is marked paid by hand, with the receipt attached.
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 finance system for a services company with ten employees. Bank accounts and petty cash with an opening balance; payable and receivable entries with description, amount, due date, category, cost centre, supplier or client and payment method, either recurring every month or split into instalments; marking each entry paid with the date, amount paid, interest or discount and the receipt attached; receivables that generate a card payment link and mark themselves paid when the payment is confirmed; transfers between accounts; cash flow for the next thirty, sixty and ninety days, day by day, highlighting days with a negative balance; importing a bank statement from a spreadsheet to match against the entries; two roles: finance, who enters and marks entries paid, and partner, who only sees the reports; an email reminder of bills due tomorrow; and a dashboard only I can see, with today's balance, payables and receivables for the week, overdue amounts per client, expenses by category for the month and the monthly result for the last twelve months.
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.