Availability per professional or resource
Working hours, breaks, durations and blackout dates as data — so two people can never take the same slot.
Availability per professional, confirmation, reminders and check-in — the classic agenda, without the spreadsheet.
Booking apps are where a spreadsheet breaks first: two people take the same slot, the reminder is forgotten, and nobody knows who confirmed. Here the availability is a data model, the confirmation is an automation, and the reminder goes out by email or push without anyone remembering to send it.
People reach this page looking for
What gets built
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Working hours, breaks, durations and blackout dates as data — so two people can never take the same slot.
The customer books, gets a confirmation, and gets reminded by email or push without anyone remembering to send it.
Charge in full, take a deposit, or let people pay on arrival. No-shows stop being free.
A screen per professional showing only their own bookings, plus check-in, rescheduling and a history that survives the month.
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.
Say what the app does and what it has to remember. No diagram, no schema, no naming a single framework.
Screens, data models, login and payments appear while you read. Anything you do not like, you say so and it changes.
Live on your domain in seconds, with version history behind you. Tuesday's conversation is Tuesday's release.
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 booking app for a barber shop with four barbers. Each barber has their own working hours and services with different durations; a customer picks the service, the barber and an available slot, pays a deposit by card or Pix, and gets a confirmation and a reminder the day before. Each barber sees only their own agenda and can mark a customer as arrived or a no-show; the owner sees everyone, plus revenue and no-show rate per month.
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.
Class booking for a studio with a hard capacity: credits, a waiting list that moves itself, and a door roster that records who came.
A salon diary where every appointment reserves the turnaround, so a gap on the board is time that can really be sold — and an assistant that says which gaps are worth a call.
Questions
Yes, because availability is a model in the database and not a rendered calendar. The slot is taken when the record is written, so the second person's booking fails at the database, which is the only place that can decide it consistently.
Keep looking
Most apps end up sitting between two categories. Nothing stops you from asking for both in the same paragraph.
Catalog, cart, checkout, coupons and subscriptions. Card and Pix built in, with orders and customers in your own database.
Profiles, feeds, posts, comments and directories, with ownership rules per record.
Lessons, modules, student progress and a paywall, with video and files hosted on the platform.
Service desks, internal back offices, order tracking, checklists and dashboards for your team.
Pipelines, leads, proposals and follow-ups — a CRM shaped like your process instead of someone else's.
Onboarding, requests, approvals, documents and signatures — the internal flows that live in email today.
Ledgers, budgets, expense control and financial dashboards, with charts that read from your own records.
Quizzes, challenges, scoreboards and interactive experiences that run in the browser.
Directories, forms, catalogs, internal portals — anything you can describe in a sentence.
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.