Planification : comparatif

Tidetime vs VoxelBooking

Prix, fonctionnalités documentées et limites issus de sources officielles datées, côte à côte. Les inconnues restent inconnues ; des unités de facturation différentes ne permettent pas de comparer directement les coûts.

Ce que les sources établissent

Une lecture de la documentation officielle vérifiée pour Tidetime et VoxelBooking. Ce n’est ni un test pratique, ni un classement, ni la recommandation d’un produit.

Questions d’achat traitées pour les deux
1 critère
Documenté pour un seul
1 critère
Non vérifié pour aucun
0 critère
Prix
Pas encore comparables

Prix

Aucune comparaison de prix complète à conditions égales n’est encore établie ; les prochaines étapes indiquent ce qui manque.

Questions d’achat traitées pour les deux

Même quand les libellés concordent, vérifiez dans chaque source les différences d’offres, d’unités et de périmètre.

Planification d’équipe
Tidetime 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.
VoxelBooking The Timeslot booking pattern uses a services × staff matrix with configurable slot duration and buffer times.

Documenté en termes non confirmés

Ces données peuvent décrire des mesures, marchés, langues ou périmètres différents. Vérifiez chaque offre, unité et période avant de les comparer.

Utilisateurs
Tidetime 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.
VoxelBooking Operators can create additional businesses, each with its own isolated booking page and settings, and invite business owners who manage only their own business.
Événements
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.
VoxelBooking The Event booking pattern lists RRULE recurring events, a waitlist and per-booking spot limits.

Limites à vérifier

  • 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.
  • VoxelBooking VoxelBooking documents deployment at the root of a domain or subdomain, rather than a subfolder.
  • VoxelBooking A production server needs PHP 8.3 or newer, MySQL 8.0 or newer and either Apache with mod_rewrite or Nginx.

Pas encore vérifié

Chaque critère comparé est documenté pour au moins un produit.

Documenté pour un seul produit, voir le tableau ci-dessous : Tidetime : calendriers.

« Non vérifié » signifie que nos sources vérifiées ne l’établissent pas. Cela ne veut pas dire qu’un produit n’a pas la fonctionnalité ni qu’il est gratuit.

Preuves côte à côte

Valeurs documentées avec leurs sources et dates de vérification ; les exigences que les sources n’établissent pas restent signalées.

  • Documenté comme pris en charge
  • Documenté comme non pris en charge
  • Non vérifié Les sources ne l’établissent pas
  • Sans objet
Périmètre et limites documentés ; les critères non vérifiés restent inconnus.
ExigenceTidetimeVoxelBooking
Tarifs
Offre gratuite · prix payants non vérifiés

Offre gratuite · prix payants non vérifiés

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

Vérifié le 3 nov. 2026 · Tidetime: tidetime-source

VoxelBooking describes self-hosted booking for timeslots, resources, capacity and events.

Vérifié le 3 nov. 2026 · VoxelBooking: voxel-source

Limites de couverture
The project says there is no hosted plan at the captured revision.

Vérifié le 3 nov. 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.
VoxelBooking documents deployment at the root of a domain or subdomain, rather than a subfolder.

Vérifié le 3 nov. 2026 · VoxelBooking: voxel-source

  • Self-hosted A production server needs PHP 8.3 or newer, MySQL 8.0 or newer and either Apache with mod_rewrite or Nginx.
Utilisateurs
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.

Vérifié le 11 nov. 2026 · Tidetime: tidetime-project

Operators can create additional businesses, each with its own isolated booking page and settings, and invite business owners who manage only their own business.

Publisher repository README at the main branch (commit cbf54db3; the project has no tagged release) captured on 9 November 2026; supplier description, not an installation, booking or performance test. The captured README states no limit on businesses or users and says AGPL-3.0 places no limit on the number of installations. A restricted manager role appears only in the demo accounts table and is not cited.

Vérifié le 11 nov. 2026 · VoxelBooking: voxelbooking-project

Calendriers
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.

Vérifié le 11 nov. 2026 · Tidetime: tidetime-project

Non vérifié
Événements
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.

Vérifié le 11 nov. 2026 · Tidetime: tidetime-project

The Event booking pattern lists RRULE recurring events, a waitlist and per-booking spot limits.

Publisher repository README at the main branch (commit cbf54db3; the project has no tagged release) captured on 9 November 2026; supplier description, not an installation, booking or performance test. Each business is assigned one booking pattern at creation, so event features apply to businesses created with the Event pattern.

Vérifié le 11 nov. 2026 · VoxelBooking: voxelbooking-project

Planification d’équipe
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.

Vérifié le 11 nov. 2026 · Tidetime: tidetime-project

The Timeslot booking pattern uses a services × staff matrix with configurable slot duration and buffer times.

Publisher repository README at the main branch (commit cbf54db3; the project has no tagged release) captured on 9 November 2026; supplier description, not an installation, booking or performance test. This is staff-and-service booking inside one business; the README does not describe round-robin, collective or priority team routing. Each business is assigned one booking pattern at creation.

Vérifié le 11 nov. 2026 · VoxelBooking: voxelbooking-project

Note de couverture

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.

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.

Prochaines étapes

  • Vérifiez les prix des offres payantes, la durée de facturation et les taxes de Tidetime sur sa page de tarifs officielle ; seule son offre gratuite est vérifiée ici.
  • Vérifiez les prix des offres payantes, la durée de facturation et les taxes de VoxelBooking sur sa page de tarifs officielle ; seule son offre gratuite est vérifiée ici.
  • Interrogez VoxelBooking sur ce point : calendriers. Nos sources ne l’établissent pas encore.

Les commissions ne modifient jamais les coûts, l’éligibilité ni l’ordre.