A calendar per room, with no double booking
Each room or cabin has its own availability. A booking occupies the nights in the database, so a second booking for the same night fails before it becomes a problem at reception.
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.
Seasonal rates and minimum stays
Low season, high season, holiday and weekend rates, with a minimum number of nights per period. The total appears calculated before the guest pays.
A deposit on booking and the balance on arrival
A percentage paid by card when booking, with the remainder recorded for check-in. The cancellation policy is written into the booking itself.
A guest guide and requests during the stay
Wi-fi password, breakfast hours, local tours and house rules on the guest's phone, plus requests for towels, a transfer or a tour that land at reception.
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 guesthouse with eight cabins. Cabins with name, capacity, photos, amenities and seasonal nightly rates, with low season, high season, holidays and weekends, and a minimum number of nights per period; an availability calendar per cabin that prevents two bookings on the same nights; the guest picks dates and the number of people, sees the free cabins with the total calculated and pays a thirty percent deposit by card, getting a confirmation by email; the cancellation policy is recorded on the booking; two days before arrival the guest gets a link for online check-in with their ID and expected arrival time; during the stay they open a guide with wi-fi, breakfast hours, local tours and house rules, and make service requests that land in a queue at reception; reception sees the month's occupancy, the day's arrivals and departures and the balance due on each booking; and I see a dashboard with occupancy rate, average daily rate, revenue per month and booking sources.
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.