Members with a status and a history
A record with unit or category, join date, a status of active or overdue, and each person's payment history.
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.
Dues that repeat on their own
Recurring card billing, with anyone who failed appearing on a list rather than in a spreadsheet somebody has to reconcile.
Booking shared spaces
A hall, a court or a barbecue area with a calendar per space. Two bookings in the same slot fail in the database, not in a conversation.
Votes open only to members in good standing
An agenda published, a window opened, one vote per member, and the count coming out of the records. Anyone overdue does not vote.
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 a residents association. Members with name, contact, unit, join date and status; dues billed recurrently by card, with payment history and a list of overdue members; announcements published by the committee with push to everyone or to one street or block; shared spaces such as a function room, a court and a barbecue area, each with its own calendar and a booking that prevents two in the same slot, with committee approval where I mark it so; meetings with an agenda, a voting window and one vote per member, open only to those in good standing, counted automatically when the window closes; a channel for requests and complaints with a status and a reply; and a committee dashboard with active members, arrears, the month's bookings and the results of votes.
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.