Pricing
Free while you build. Pay when your client goes live.
You pay per site, never per person. Staff, rooms and resources are unlimited in Pro and Agency: you pay for bookings, not for seats.
-
Free
€ 0 per month
For building, testing and small sites.
- 50 bookings per month
- 250 customers
- 1 staff member, 1 site
- Booking form and public API
- Sandbox to build against
-
Pro
€ 19 per month
or € 190 per year
For a business that actually runs on it.
- 1,000 bookings per month
- Unlimited customers and staff
- Classes, waiting lists, packages, tickets, rentals
- Online payments through your client’s own Mollie account
- Management API, MCP server and webhooks
- Your own mails, coupons and intake questions
-
Agency
€ 49 per month
or € 490 per year
For agencies with several client sites.
- 5 client accounts included, then € 9 each
- 1,000 bookings per account
- Everything in Pro
- Switch between client accounts with one login
Introductory prices in euros, per site, per month. An extra client account on Agency is € 9 a month. VAT is not stated here yet.
What each plan includes
Only what the product enforces today. Nothing here is a promise for later.
| Free | Pro | Agency | |
|---|---|---|---|
| Booking form and public API | ✓ | ✓ | ✓ |
| Sandbox (a 24-hour test account, no signup) | ✓ | ✓ | ✓ |
| Documentation and examples | ✓ | ✓ | ✓ |
| Bookings per month | 50 | 1,000 | 1,000 per account |
| Customers | 250 | unlimited | unlimited |
| Staff, rooms and other resources | 1 | unlimited | unlimited |
| Client accounts (projects) | 1 | 1 | 5, then € 9 each |
| Classes, waiting lists, packages, tickets, rentals, coupons, intake questions, reminder mails | – | ✓ | ✓ |
| Online payments through the business’s own Mollie account | – | ✓ | ✓ |
| Management API and MCP server | – | ✓ | ✓ |
| Webhooks | – | ✓ | ✓ |
Against the alternatives
Three ways a client site gets bookings, side by side.
| Build it yourself | WordPress + a plugin | nisebookings | |
|---|---|---|---|
| Time to a booking | weeks | an afternoon | two lines, then configure |
| What you maintain | the whole engine | a plugin, its add-ons and the CMS | nothing on your side |
| Frontend | whatever you build | the theme decides | your stack, your design |
| API for your own UI | you build it | none | public and management API |
| Where the business runs it | in your app | in wp-admin | in its own admin |
| Payments | you build them | a plugin add-on | the business’s own Mollie account |
| Cost model | your hours | a licence per site, forever | per site, per month |
How the limits work
-
A booking counts when it is made
An appointment or a ticket order. Cancelled and rejected bookings never count. Rescheduling is not a new booking.
-
A warning at 80%
The owner sees a warning in the dashboard, and gets a mail at the limit. From then on new bookings are refused with a clear message. Existing appointments, customers and settings stay as they are.
-
Unlimited means unlimited
From Pro up, staff, rooms and resources are never counted. Add every colleague of every client as staff; the invoice stays the same.
-
Yearly or monthly
A yearly plan costs ten months. Switch whenever you like; a running period is not prorated.
Questions
Who pays: the developer or the business?
Your choice. The account belongs to the site, so it can run on your card and your invoice, or the business pays directly. Only the account owner can change the plan.
What if my client stops paying?
The account keeps working for 14 days after the paid period, and the owner gets a mail. Then new bookings stop. Appointments, customers and data stay readable, and paying restores everything at once. Nothing is deleted.
Is the API really in the Free plan?
The public API and the sandbox are: that is what you evaluate and build with. The management API and the MCP server come with Pro, because a live client account runs on them.
Do I pay extra for staff or users?
No. Nothing in the product is priced per person.
Can my client or a colleague log in themselves?
Yes. Settings → Team invites someone by e-mail with one of four roles: owner, admin, front desk or staff. Each role gets its own menu, a staff login is tied to their own staff member under Staff (so they see only that agenda), the invitation is a one-time link and the person sets their own password. An admin can never remove an owner, and the last owner stays — so one login per person, and the owner keeps control.
Put bookings on your next site.
Start free and build against a sandbox. Pay once your client takes real bookings.
Free account. All you need is an e-mail address.