Open-source project
alextselegidis/easyappointments avatar
alextselegidis/easyappointments

Easy!Appointments: a self-hosted booking desk you run on your own PHP host

:date: Easy!Appointments - Self Hosted Appointment Scheduler

4,492 stars1,592 forksPHPGPL-3.0

At a glance

What is it?
Easy!Appointments gives a small team or solo practitioner a booking calendar with providers, services and working plans, running on plain PHP and MySQL with no vendor account. The scheduler is capable, but the setup wizard and the absence of any payment path define where it fits.
Who is it for?
Adopt Easy!Appointments if you want booking pages that live on infrastructure you already run and you can live without online payment capture. Do not adopt it if a stranger is the one booking, if the payment step is part of the transaction, or if you need a vendor answer the phone when the server is down.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • alextselegidis/easyappointments4,492 ★ · +98
Star history
Repository2026-09-232026-11-15
alextselegidis/easyappointments4.4k4.5k

98 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The booking unit is a service assigned to a provider, not a calendar slot

Easy!Appointments is a scheduling system for businesses that sell time rather than goods: a clinic with several practitioners, a repair shop with two bays, a tutor with one desk. The data model starts with providers and services, and the bookable surface is built from that pairing. Appointment and customer records hang off it, so the shape of the calendar follows how you organised the people and the work.

The interesting piece for an evaluator is what happens around that core. Google Calendar synchronisation exists so a practitioner's existing day is not shadowed by a second calendar that only knows about bookings. Email notifications cover confirmations. A multi-language interface and working plans (the availability rules that say when a provider can be booked) round out the set, and the feature list groups them under scheduling needs rather than breaking them into modules.

Two absences matter as much as the features. Nothing in the README describes taking a payment inside a booking, and there is no store, catalogue or seat inventory to deplete. Anyone whose revenue model depends on charging a deposit at booking time is looking at the wrong tool. The repository also ships an openapi.yml at its root, mounted into a Swagger UI container in the compose file, so the API surface is treated as a first-class part of the project rather than an afterthought.

One CodeIgniter application, one PHP-FPM container, and MySQL on port 3306

The architecture is a single PHP application. The repository root carries application/, system/, assets/, storage/, config-sample.php and index.php, the layout of a CodeIgniter-era project: controllers and views under application/, the framework under system/, and user-writable files confined to storage/. There is no separate API service to deploy.

The Docker development environment makes that shape concrete. It builds PHP-FPM from docker/php-fpm, mounts the working tree at /var/www/html, and drops a php-ini-overrides.ini into /usr/local/etc/php/conf.d/99-overrides.ini so local ini changes are picked up without rebuilding the image. nginx:1.23.3-alpine serves the tree, with the port taken from the NGINX_PORT variable and defaulting to 80. mysql:8.0 backs it with MYSQL_DATABASE=easyappointments, and the compose file publishes 3306 to the host by default through MYSQL_PORT.

Mailpit catches outbound mail on 1025 for SMTP with a web inbox on 8025, and phpMyadmin sits on 8080. A node:22-alpine service runs npm install and npm start, a baikal service is also defined, and swagger-ui serves the openapi.yml file on port 8000 by default. That is a wide development surface for an application that in production is just PHP, a web server and MySQL.

docker compose up is the whole quick start, and the container is where you actually work

The documented development path is three commands. Clone the repository, move into it, and start the environment:

bash
git clone https://github.com/alextselegidis/easyappointments.git
cd easyappointments
docker compose up

nginx then serves the project on port 80 unless NGINX_PORT says otherwise. The work happens in a second terminal, because the container is where dependencies and assets live:

bash
docker compose exec php-fpm bash

Once inside a shell, the README's commands do the work. Install pulls both trees at once, since this is PHP with a JavaScript front end:

bash
npm install && composer install
npm start
npm run build

The environment is claimed for Linux and macOS with Docker Compose, and on Windows under WSL.

Production is Apache or Nginx, PHP 8.2, and a hand-edited config-sample.php

There is no packaged build to download and no one-line installer script in the README. Production deployment is a manual sequence: create a database, upload the easyappointments folder to the server, make the storage directory writable, copy config-sample.php to config.php, fill in the values, then open the site in a browser and follow the setup wizard. The requirements are listed as Apache or Nginx, PHP 8.2 or later, and MySQL.

That sequence puts the whole trust boundary in one file. The database credentials, and whatever else the config file holds, are edited by hand before the first request, and the setup wizard runs only after that file is in place. A misconfigured storage directory or a mistyped password surfaces as a browser error with no rollback step described. The README documents no upgrade path and no migration command either, so nothing tells you what a version change altered before you make it.

Before committing to a production install, check what your host actually gives you. PHP 8.2 is the floor, not the recommendation, and if your distribution ships 8.1 the composer.json requirements decide the outcome rather than anything in the README. The storage directory must be writable by the web server user, which is a common failure on hosts that run PHP-FPM under a different account than the one that owns the uploaded files.

Two candidate-stage packages sit in the front-end dependency list

The dependency list is where an upgrade can hurt. package.json pins bootstrap ^5.3.8, jquery ^3.7.1, moment ^2.31.0 alongside moment-timezone ^0.6.0, and one package still at a candidate stage: select2 ^4.1.0-rc.0 in dependencies. Shipping a production site on a candidate-stage selector widget is a decision, not an accident of tooling.

The fullcalendar and moment pair matters operationally. Calendar rendering and the timezone database are two separately versioned dependencies, and a bump in either changes how times are drawn, so a rebuild after a routine dependency refresh can alter the display of a booking window. jQuery 3.7.1 and the trumbowyg ^2.31.0 editor mean the front end still leans on a pre-ESM stack, and the build stays gulp-based: the repository carries a gulpfile.js, and the devDependencies lean on gulp-sass, gulp-babel and gulp-clean-css rather than a bundler.

Code is under GPL v3.0 and content under CC BY 3.0, so a distributed modification of the booking form carries the GPL obligation to publish its source. Beyond that, upgrades mean reading the change notes at the repository root, rebuilding assets with gulp, and re-running your own checks against the database, since the README documents no migration command.

Where Easy!Appointments loses to Cal.com and who should stop looking

Cal.com takes the opposite approach. It is built around a hosted, link-shared booking page where the scheduler, the video call and the payment step are one product, and the person booking never needs your server. Easy!Appointments is the reverse: the database sits on your host, the booking page is one more route in an application you already deploy, and the calendar synchronisation keeps it in step with a Google account rather than replacing it.

That difference decides the fit. If you want to charge a customer during the booking, or hand the scheduling link to strangers and expect it to work without your involvement, Cal.com's shape matches and this one does not. If you need to run bookings inside an intranet, Easy!Appointments' self-hosted deployment is the reason to look closer.

The repository contains no WordPress integration: the application is a standalone PHP entry point at index.php. If your booking needs to live inside an existing WordPress site, this project gives you a self-hosted application to link to, not a plugin to drop into a theme. A reasonable alternative question is whether a plain calendar link plus a contact form would serve a small practice with a handful of fixed weekly slots better than any scheduler.

The first thing to check is the wizard, because nothing after it is documented

Easy!Appointments suits a practitioner or a small team that already runs a PHP and MySQL host and wants booking pages that live on that host rather than on a vendor's platform. It gives you providers, services, working plans, Google Calendar synchronisation, email notifications and a multi-language interface, and it charges nothing for the privilege.

It is the wrong choice when payment capture is part of the booking, when the person booking is a stranger who will never see your infrastructure, or when you need someone else to answer the phone if the server is down. There is no payment path in the README and no plugin layer for WordPress.

Editorial conclusion

Adopt Easy!Appointments if you want booking pages that live on infrastructure you already run and you can live without online payment capture. Do not adopt it if a stranger is the one booking, if the payment step is part of the transaction, or if you need a vendor answer the phone when the server is down. Verify the setup wizard first: run the production steps against your own PHP 8.2 and MySQL pair, rename config-sample.php to config.php, and confirm the wizard completes before importing real customer data. The README documents no rollback and no migration command, so that first successful wizard run is the decision point.

Frequently asked questions

How do I install Easy!Appointments?

For development, clone the repository, run `docker compose up`, then open a shell in the application container and run `npm install && composer install` followed by `npm start`. For production, create a database, upload the easyappointments folder, make the storage directory writable, rename config-sample.php to config.php, and follow the setup wizard in the browser. Production needs Apache or Nginx, PHP 8.2 or later, and MySQL.

How do I use Easy!Appointments after it is installed?

The setup wizard runs in the browser once config.php exists, after which the system is ready. Day to day the scheduling model is built from providers and services, with working plans defining availability and Google Calendar synchronisation keeping bookings aligned with an existing calendar.

What is the difference between Easy!Appointments and Cal.com?

The Easy!Appointments README makes no comparison with Cal.com. Easy!Appointments runs the whole application on your own server with PHP, MySQL and a config file you edit yourself, and synchronises with Google Calendar rather than replacing your calendar.

What can I use instead of Easy!Appointments?

The decision usually turns on payment capture and who hosts the booking page. If you need to charge customers during booking, a hosted scheduler is a better fit, while a small practice with a few fixed weekly slots may be served by a calendar link and a contact form. Easy!Appointments itself documents no payment integration and no WordPress plugin.

Official sources

  1. alextselegidis/easyappointments on GitHub
  2. License: GPL-3.0
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/alextselegidis-easyappointments.svg)](https://hysenlabs.com/projects/alextselegidis-easyappointments)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/alextselegidis-easyappointments.svg)](https://hysenlabs.com/projects/alextselegidis-easyappointments)

Was this useful?