Easy!Appointments alternatives: first, check which Easy Appointments you have

Search for "Easy Appointments alternatives" and the first page is directories. AlternativeTo's list for Easy!Appointments opens with Thunderbird Appointment, Cal.com, Notion Calendar, Lunacal and Calendly (checked 29 October 2026). Those are tools for letting people grab a slot on your calendar. Easy!Appointments is something else: services, providers, working plans, a public booking page for customers. Swap one for the other and you'll find out in the first week.

There's a second trap before you even get to alternatives. Two different products answer to the name, and the right replacement depends on which one is running on your server.

Two products answer to the same name

The one most developers mean is Easy!Appointments: a PHP and MySQL web app you install on your own server, on GitHub as alextselegidis/easyappointments, licensed GPL-3.0. Its current composer.json asks for PHP 8.2 or newer.

The one most WordPress users mean is Easy Appointments, no exclamation mark, a plugin on WordPress.org with more than 10,000 active installs, version 4.0.4 and a 4.3 rating when I checked. As far as I can tell it's a separate project: its listing never mentions the Easy!Appointments maintainer, and its changelog points to its own site, easy-appointments.com. Online payments through Stripe, PayPal or WooCommerce are listed as part of its paid Pro extension.

To make it more confusing, there is also an official Easy!Appointments plugin on WordPress.org by Alex Tselegidis, around 500 active installs. It isn't the booking engine. It's a bridge: you install the PHP app separately, paste its address into the plugin's settings, and embed the booking form with a block, an Elementor widget or the [easyappointments] shortcode.

The rest of this piece is about the PHP app, because that's what people searching "easy appointments open source" or "easyappointments docker" are running.

Easy!Appointments is still alive in 2026

Before you plan a migration, check whether you need one. The release history from the project's own changelog:

The two-year silence between 2022 and 2024 is where a lot of the "is it abandoned?" searches come from. It wasn't. Since 1.5.0 it has had a REST API, webhooks, Google Calendar and CalDAV sync, LDAP, and the model service businesses actually have: services, providers, working plans and breaks.

Read the 1.6.1 notes if you're on anything older. Among the fixes: the booking-page CAPTCHA could be skipped by leaving the field out of the request, login throttling wasn't blocking repeated wrong passwords, an ID in the body of a REST API update could redirect the update to a different record such as an administrator account, and secretary accounts could read other providers' calendar sync tokens and CalDAV passwords. None of that is a reason to leave. It is a reason to upgrade this week, and to admit that a self-hosted scheduler is a thing someone has to watch.

What the open-source download doesn't do, as far as I could find, is take money. Payments aren't in its feature list or anywhere in the changelog I read. The maintainer sells managed hosting, white-labelling, one-hour support sessions, custom development and quoted data migration on easyappointments.org; the premium page links out to a separate pricing page and lists no figures itself.

Why the directories hand you Calendly clones

Directory lists are built from tags, and "appointment scheduler" covers two jobs that barely overlap.

A meeting scheduler shares your free time: one person, one calendar, a link, a slot. Calendly, Cal.com, Notion Calendar, Thunderbird Appointment and Rallly all live here, and they're good at it.

A service scheduler sells time on a menu: a 45-minute colour with a senior stylist, a physio's follow-up, a car service bay. It needs services with durations and prices, several providers with their own working plans, a public page where a customer picks all three, and usually a payment. Easy!Appointments lives here, which is why moving its users onto a meeting tool rarely sticks: there's nowhere to put the service menu.

So the first question isn't "which project is most popular." It's what you used Easy!Appointments for.

Pick by the job you hired it for

LibreBooking is the one I'd look at if your Easy!Appointments install was really booking things rather than people: meeting rooms, lab equipment, vehicles, desks. It's the GPL fork of Booked Scheduler and it has been moving fast, from v6.0.0 on 1 October to v7.1.0 on 13 October 2026. It thinks in resources, accounts, quotas and approvals, not in a public service menu. I wrote up where the Booked code went and how LibreBooking compares separately.

Thunderbird Appointment is Mozilla's open-source meeting scheduler, MPL-2.0, Docker being the only supported way to build it. Good if what you really had was "people book a call with me." Cal.diy, the community fork of Cal.com after Cal.com closed its source, is MIT, but its own site recommends it for personal, non-production use. I'd take that warning at its word.

Everything else in the open-source column is narrower: MRBS for meeting rooms, Seatsurfing for desks (German readers: I compared Seatsurfing and LibreBooking for desk sharing in German, works-council settings included), Rallly for group polls. If you run a single clinic, the patient scheduling options are a different decision again, because there the scheduler usually comes with the records system.

When the server is the real complaint

Most people I talk to who leave Easy!Appointments aren't unhappy with the scheduler. They're unhappy with being its sysadmin: PHP upgrades, a MySQL backup nobody tested, an SMTP relay that started landing in spam, and now a security release with a list of fixes that long.

If that's you, the honest answer is not a different self-hosted PHP app. LibreBooking on your own box gives you the same chores with a different interface. Keep the software and hand off the server: the maintainer's managed hosting, or one of the one-click Easy!Appointments deploys that PaaS catalogues such as Railway and Elestio list. You keep your data model, your booking page and your staff's habits, and someone else applies 1.6.2.

Moving off it entirely costs more than people expect. I couldn't find a maintained importer from Easy!Appointments into any of the tools above, which is probably why the maintainer sells data migration as a quoted service. Plan on exporting customers from MySQL to CSV, recreating services and providers by hand, and moving only future appointments.

Charging at the moment of booking is a different category

I build Opencals, so weigh this section accordingly.

If the reason you're looking is that a customer should pick a service, see a price, add an extra and pay before the slot is theirs, you're no longer shopping for a scheduler. You want commerce with a calendar underneath: services as products, variable pricing, add-ons, discounts, customer accounts, and a checkout. That's the shape we built Opencals around. Every booking is an order.

What that means against Easy!Appointments, plainly:

• Opencals is hosted and not open source. You can't install it on your own server. The open parts are the MIT-licensed Next.js templates, the @opencals/storefront-sdk and our Agent Skills; you can fork a template, put it on your own domain and keep the front end entirely yours, but the engine runs on our side. Here's why we drew the line there.
• It takes card payments through Stripe once Stripe is connected to your store, which the open-source Easy!Appointments download doesn't do.
• It has no LDAP or Active Directory login and no outgoing webhooks. Easy!Appointments has both since 1.5.0. Booking events in Opencals go out through Zapier. If your setup depends on staff logging in with company accounts or on a webhook into your own system, that's a real gap on our side.
• Price (checked 29 October 2026): $0.99 per appointment with no monthly fee, or $14.98 a month including 300 appointments and $0.20 each after that. The pricing page says the fixed plan is cheaper past about 16 bookings a month.
• The free development store has every feature in test mode, no card needed, but it can't take real payments until you're on a plan.

If you're a developer who picked Easy!Appointments because you wanted to own the booking page, the booking API is the part to look at: you write the front end, we run availability, carts and checkout.

My pick, and what would change it

If Easy!Appointments does the job, upgrade to 1.6.1 and stay. It's maintained, it's free, and nothing on the alternatives list does customer appointments better on your own server.

If the server is the problem, pay someone to run the same software rather than migrating to a different app with the same chores.

If you were booking rooms or kit, move to LibreBooking. If you were booking calls, move to Thunderbird Appointment.

And if what you need is money at the moment of booking, stop comparing schedulers and look at hosted engines, ours included. The one thing that would change that last answer is a hard requirement that the whole system run on your hardware. Then you're back to Easy!Appointments plus your own payment integration, and you should budget for that integration honestly.