Apps your customers sign into, book through, and pay in.
The half that usually stalls the project — accounts, saved data, payments, booking, email — described in the same conversation that built the screens.
No credit card required · Published in minutes
See every guide in this category ↓What you normally give up
The screens are the easy half. What stalls the project is everything behind them: a database somewhere, a sign-in provider, a payment processor, a scheduling tool, an email service. Five vendors, five bills, five sets of settings, and your customer records split across all of them. So most projects ship the screens and postpone the rest — or shrink to a page with a contact form and call that a launch.
What you get
Four things that come with every app in this category.
A real database from the first sentence
Describe what you are tracking — customers, orders, sessions, properties — and get records, search, filters, and edit screens back. It is your data, in your app, exportable any day you want it.
Accounts that belong to your app
Your customers sign in with an email and password or with Google, at whatever level of access you describe. They are users of your app, not accounts on ours, and there is no per-person charge for them.
Take money
One-off checkout, subscriptions, and a self-serve billing page your customers manage themselves — once you connect your own Stripe account. Payments run through your account, so the money never routes through us.
Take bookings
Real availability rather than a form that emails you a preference: capacity, buffers, correct time zones, cancellations, and reschedules. The confirmation email goes out the moment the slot is taken.
What it actually produces
A checklist rather than a highlight reel: what a published customer app does on day one, and what it needs from you first.
Records you own
Every customer, order, and booking is a row in your own database. Search it, filter it, edit it, export it. Nothing is locked inside a tool you would have to scrape to leave.
A sign-in that is yours, not ours
Your customers get their own login with an email and password or with Google, and see only what you said they should. They never touch an Exepad account.
Payments, after you connect Stripe
Checkout, subscriptions, and a billing page your customers manage themselves. This is the one thing that will not work until you connect a Stripe account — we would rather say so here than let you find out at launch.
Booking and the email that follows it
A slot picker with real availability and correct time zones, a cancellation and reschedule link, and a confirmation that sends itself. No reminder tool bolted on beside it.
What's included
Everything below is part of the product, not an add-on.
- Records with search, filters, and edit screens — 50,000 rows on Pro.
- Customer sign-in by email and password, or with Google.
- Checkout, subscriptions, and a billing page, once your Stripe account is connected.
- Bookings with real availability, time zones, cancellations, and reschedules.
- Confirmation email and in-app notifications, sent when something actually happens.
- File uploads attached to the record they belong to — 500 MB.
- Your own web address, with the security certificate handled for you. (Pro)
Free covers simple web apps: three to build, one live at a time, up to 50 form responses a month. Stored records, customer sign-ins, and payments are Pro.
Pro is $25 a month for unlimited full-stack apps and advanced AI models — 50,000 records, bookings, payments, transactional email, and your own web address.
See plansEvery guide in this category
All 9 guides in this category — the full list, not a selection.
Manage every client in one app
Stop tracking clients across a spreadsheet, an inbox, a shared drive, a kanban board, and reminders you keep in your head. Publish one app that holds the contact, the notes, the files, and the next action.
Build a customer database you actually own
Stop scattering customers across a trial CRM, an Excel export, an email list, and a support inbox. Publish one database with the schema you want, the fields that matter, and exports any time.
Track every lead from form to close
Leads come in from a form, get pasted into a sheet, sometimes get an email — and most fall through. Publish one app that captures the lead, tags the source, fires the follow-up, and shows what actually converts.
Share files with clients in one portal
Client work is scattered across cloud-storage links, chat channels, file-transfer services, and email attachments — and clients still email asking where the latest version is. Publish one portal that holds every file, every version, every approval.
Manage every member in one place
Most clubs and associations run on a spreadsheet, a contact list, a forum login, and a payments dashboard — and lapsed members never come back. Publish one app that holds the roster, the dues, the renewals, and the directory.
Take bookings from any visitor, any device
Stop juggling a calendar SaaS, an email tool, a payment add-on, and a spreadsheet. Publish one booking page that captures the slot, sends confirmations, and writes every record to your own database.
Schedule appointments across every staff calendar
Stop running the front desk on phone calls, a paper appointment book, and an Outlook calendar that never syncs. Publish one internal app where every staff calendar, availability rule, and recurring appointment lives in one place.
Run every event from one published app
Stop stitching a ticketing site, an email blaster, a Google Form, a payment plugin, and a custom landing page. Publish one app that handles the registration page, the attendee database, the reminders, and on-site check-in.
Manage classes, rosters, and reminders in one app
Stop running a studio on a class-management SaaS, a separate email tool, a payment plugin, and a spreadsheet roster. Publish one app where the schedule, attendance, payments, and reminders share one student database.
Who builds these
Three ways people arrive at the same result.
People
You describe the app the way you would explain it to a friend, and the parts you were dreading — the sign-in, the payment page, the confirmation email — come with it. Changing your mind later is another sentence, not another quote.
Developers
Skip the week that always goes to plumbing: schema, auth, checkout, scheduling, mail. Generate that layer, then write your own code for the screens where the details actually matter.
Agents
An agent can build the whole app and publish it — including the database, the sign-in, and the paid flows, not just the screens.
Frequently asked
Can I build a customer app on the free plan?+
No, and it is worth being blunt about it. Free is for simple web apps: three of them, one live at a time, and up to 50 form responses a month. It stores no records and serves no app requests, so a sign-in, a booking, or a checkout needs Pro at $25 a month.
How much can my app store?+
On Pro: 50,000 records and 250 MB of data, plus 500 MB of file storage with a 10 MB limit per file, and 100,000 app requests a month. For most customer apps that is years of bookings and orders. If you are heading past it, tell us before you build rather than after.
How many emails can my app send?+
200 transactional emails a month on Pro — confirmations, receipts, reset links — and there is also a per-app daily cap, so a runaway loop cannot burn the month in an afternoon. They go out from an Exepad address unless you configure your own sending domain. This is transactional mail only, not marketing campaigns.
What do I need before I can take payments?+
A Stripe account of your own, connected to the app. Checkout, subscriptions, and the customer billing page all run through it, which is why the money reaches you directly and never sits with us. Until that account is connected, the paid parts of the app will not run — it is the one piece we cannot do for you.
Do my customers need an Exepad account?+
No. The sign-in belongs to your app, not to our platform. Your customers register with an email and password or with Google, and you decide what each level of access can see. There is no per-person charge for the people who use your app, however many of them there are.
Is everything my app might need already built in?+
No, and we would rather list the ones that are. Bookings, payments, transactional email, in-app notifications, content and blog pages, and form capture are complete and shipping today. Anything you do not see named on this page, assume we have not built it yet and ask before you plan around it.
Can I change the app after real customers are using it?+
Yes. You describe the change the same way you described the app, and you publish when it looks right. Every published version is kept, so if a change lands badly you can go back to the one before it without losing the records your customers created in between.
Describe the app. Get the half that usually stalls.
Accounts, records, bookings, payments, and the emails that follow them — in one app, at one web address, from one conversation.
Describe your app →