Scheduling comparison

Easy!Appointments vs Tidetime

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

What the evidence answers

A reading of reviewed official documentation for Easy!Appointments and Tidetime. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
0 requirements
Documented for one
2 requirements
Not verified for either
0 requirements
Prices
Not like-for-like yet

Price

A complete like-for-like price comparison is not established; the next steps say what is missing.

Documented in unconfirmed terms

These facts may describe different measures, markets, languages or scopes. Check each plan, unit and period before comparing them.

Calendars
Easy!Appointments The project lists Google Calendar synchronization.
Tidetime Providers can connect Google Calendar or Microsoft 365 for busy-time conflict checks, and Google Meet links are generated for services located on Google Meet when the provider has Google connected.
Events
Easy!Appointments The project lists service and provider organization together with working plans and booking rules.
Tidetime Services have their own duration, location, intake questions and an optional manual-confirmation step, and one or more providers are assigned to each service.

Limits to check

  • Easy!Appointments The project describes a self-hosted deployment.
  • Easy!Appointments A production install needs Apache or Nginx, PHP 8.2 or above and a MySQL database.
  • Tidetime The project says there is no hosted plan at the captured revision.
  • Tidetime The production Compose file runs PostgreSQL, the standalone Next.js server, a background jobs worker and Caddy; the app container applies database migrations before it starts.

Not verified yet

Every compared requirement has evidence for at least one.

Documented for one product only, shown in the table below: Tidetime: seats and team scheduling.

Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.

Side-by-side evidence

Documented values with their sources and check dates; requirements the sources do not establish stay marked.

  • Documented as supported
  • Documented as unsupported
  • Not verified Sources do not establish it
  • Not applicable
Documented scope and limits; unverified dimensions remain unknown.
RequirementEasy!AppointmentsTidetime
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

Who it is for
Easy!Appointments describes an open-source scheduling system for booking workflows.

Verified Nov 4, 2026 · Easy!Appointments: easyappointments-source

Tidetime describes self-hosted appointment scheduling for one company with multiple services and providers.

Verified Nov 3, 2026 · Tidetime: tidetime-source

Coverage limits
The project describes a self-hosted deployment.

Verified Nov 4, 2026 · Easy!Appointments: easyappointments-source

  • Self-hosted A production install needs Apache or Nginx, PHP 8.2 or above and a MySQL database.
The project says there is no hosted plan at the captured revision.

Verified Nov 3, 2026 · Tidetime: tidetime-source

  • Self-hosted The production Compose file runs PostgreSQL, the standalone Next.js server, a background jobs worker and Caddy; the app container applies database migrations before it starts.
SeatsNot verified
Team members have one of four roles (Owner, Admin, Scheduler, Member); a provider is a member assigned to a service, and an assigned Scheduler also becomes bookable.

Publisher project README at release v0.2.0 (commit a65ba361) captured on 9 November 2026; supplier description, not a deployment or independent test. The README states no per-seat pricing and does not state a member limit.

Verified Nov 11, 2026 · Tidetime: tidetime-project

Calendars
The project lists Google Calendar synchronization.

Publisher project README at release 1.6.1 (commit d30cba6d) captured on 9 November 2026; supplier description, not a deployment or independent test. The README does not name other calendar providers or describe two-way behaviour.

Verified Nov 9, 2026 · Easy!Appointments: easy-appointments-project

Providers can connect Google Calendar or Microsoft 365 for busy-time conflict checks, and Google Meet links are generated for services located on Google Meet when the provider has Google connected.

Publisher project README at release v0.2.0 (commit a65ba361) captured on 9 November 2026; supplier description, not a deployment or independent test. The README says Google needs the instance on a custom domain with HTTPS and OAuth credentials in Google Cloud, and Microsoft 365 needs an app registered in Microsoft Entra; neither connection was tested.

Verified Nov 11, 2026 · Tidetime: tidetime-project

Events
The project lists service and provider organization together with working plans and booking rules.

Publisher project README at release 1.6.1 (commit d30cba6d) captured on 9 November 2026; supplier description, not a deployment or independent test. Bookings are organised as services offered by providers; event types, durations, buffers and group capacity are not described in the captured README.

Verified Nov 9, 2026 · Easy!Appointments: easy-appointments-project

Services have their own duration, location, intake questions and an optional manual-confirmation step, and one or more providers are assigned to each service.

Publisher project README at release v0.2.0 (commit a65ba361) captured on 9 November 2026; supplier description, not a deployment or independent test. The README also lists a booking lifecycle with confirm, reschedule and cancel, and email notifications; none of it was tested.

Verified Nov 11, 2026 · Tidetime: tidetime-project

Team schedulingNot verified
Customers can choose a provider or Tidetime assigns the least-busy available one; each provider sets weekly hours, and admins manage team availability, daily booking caps and group events with multiple seats.

Publisher project README at release v0.2.0 (commit a65ba361) captured on 9 November 2026; supplier description, not a deployment or independent test. A provider can keep several named schedules but only the default one is used for bookings. Provider assignment is described for a single company; no round-robin routing across organisations is described, and the behaviour was not tested.

Verified Nov 11, 2026 · Tidetime: tidetime-project

Coverage note

Publisher project README at the captured revision, 4 November 2026. No account, installation, appointment, poll, integration or performance test. Exact release, hosted services and third-party terms require separate review.

Publisher repository README at the captured revision, 4 November 2026. No installation, booking, integration or performance test. Hosting, service access and third-party terms require separate review.

Next steps

  • Confirm Easy!Appointments's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm Tidetime's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Ask Easy!Appointments about seats and team scheduling; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.