Find your fit
Who it is for
It fits a business or small team that wants appointment booking on its own site and is willing to operate a web application. The open-source core is free, but the business remains responsible for its server, database, setup, updates and a working notification route unless it contracts for help.
A team that prefers vendor help can request managed hosting, migration, support or custom work separately. White-label or resale plans need a specific license discussion rather than an assumption that the free self-hosted terms cover that use.
The work it supports
Core capabilities
Set up each appointment type with a service duration, then assign it to one or more providers. Providers have their own service list, working plan and breaks; global booking rules set how soon and how far ahead customers may book.
A customer can open the public booking page, choose a service and optionally a provider, pick an available date and time, enter contact details and confirm. If appointment emails are enabled, the message can contain a rescheduling or cancellation link.
Administrators, secretaries and providers can create bookings from the backend calendar as well as edit or cancel an existing appointment. Calendar views can use service colors and provider/service filters to make a multi-staff schedule easier to inspect.
The product offers email notifications for schedule changes, but the customer-notification setting and outbound email configuration must be set for the intended route. The current settings guide places email configuration in application/config/email.php rather than the Admin Panel.
Google Calendar can synchronize appointments in both directions after OAuth credentials are configured and a provider connects a calendar. The guide says recurring events are not fully supported and limits each provider to one connected Google Calendar, so check those cases before relying on sync for availability.
Booking settings can choose which customer fields appear and whether they are required, with up to five custom fields. A separate access control can limit providers and secretaries to customer records associated with their appointments; review both settings before opening the booking page.
The vendor’s configuration guide recommends a test booking to verify services, availability and notifications. That is especially useful after setting staff breaks, timezone and booking cutoffs or connecting a calendar.
Understand the offer
Pricing and getting started
The self-hosted open-source core is advertised as free, without a monthly software fee or per-appointment commission. Running it still requires suitable hosting, PHP/MySQL operation, configuration, updates, backup and email delivery; price those duties for your own environment.
Managed hosting, direct technical support, data migration and custom development are separate premium services. The retained premium page asks for a quote rather than giving a fixed rate, so confirm exactly which deployment, backup, maintenance and support tasks the proposed service includes.
The vendor published version 1.6.0 as a release. A newer 1.6.1 beta is explicitly for test or development servers, not production. Select and maintain a production version with the vendor’s current security and upgrade guidance rather than treating beta fixes as already present in 1.6.0.
The premium page separately describes Regular and Extended license options for white-label or commercial reseller use. If the plan is to rebrand or resell the scheduler, request the applicable terms and quote before building that offer.
Look a little closer
Before you choose
Pilot a fictional customer booking from the public page through confirmation, staff calendar view, reschedule and cancellation. Check the provider’s working plan, breaks, timezone and minimum notice so the offered slots match the actual schedule.
Send a test notification to both staff and customer identities. Verify the sender configuration, whether customer notifications are enabled and whether a cancellation or reschedule link reaches the right appointment.
If Google Calendar sync matters, test a provider connection, a changed appointment and recurring external events with fictional bookings. The vendor notes one calendar per provider and incomplete support for recurring events.
Before production, verify server requirements for the selected release and a backup and patching plan. The currently posted 1.6.1 beta is explicitly not production-ready even though it discusses further security and calendar fixes; ask for the current stable update path.
10 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →