Agenda: comparación

Tidetime vs VoxelBooking

Precios, funciones documentadas y límites de fuentes oficiales fechadas, lado a lado. Lo desconocido sigue siendo desconocido; con unidades de facturación distintas no se pueden comparar los costes directamente.

Qué responden las fuentes

Una lectura de la documentación oficial revisada de Tidetime y VoxelBooking. No es una prueba práctica, una clasificación ni la recomendación de un producto.

Preguntas de compra respondidas para ambos
1 requisito
Documentado solo para uno
1 requisito
Sin verificar para ninguno
0 requisitos
Precios
Aún no comparables

Precio

Aún no hay una comparación de precios completa en igualdad de condiciones; los próximos pasos indican qué falta.

Preguntas de compra respondidas para ambos

Aunque las etiquetas coincidan, revisa en cada fuente las diferencias de planes, unidades y alcance.

Agenda de equipo
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.

Documentado en términos no confirmados

Estos datos pueden describir medidas, mercados, idiomas o alcances distintos. Revisa cada plan, unidad y periodo antes de compararlos.

Usuarios
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.
Eventos
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.

Límites que revisar

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

Aún sin verificar

Cada requisito comparado tiene fuentes para al menos un producto.

Documentado solo para un producto, en la tabla de abajo: Tidetime: calendarios.

«Sin verificar» significa que nuestras fuentes revisadas no lo establecen. No significa que a un producto le falte la función ni que no cueste nada.

Evidencia lado a lado

Valores documentados con sus fuentes y fechas de comprobación; los requisitos que las fuentes no establecen quedan marcados.

  • Documentado como compatible
  • Documentado como no compatible
  • Sin verificar Las fuentes no lo establecen
  • No aplica
Alcance y límites documentados; las dimensiones sin verificar siguen como desconocidas.
RequisitoTidetimeVoxelBooking
Precios
Plan gratuito · precios de pago sin verificar

Plan gratuito · precios de pago sin verificar

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

Comprobado el 3 nov 2026 · Tidetime: tidetime-source

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

Comprobado el 3 nov 2026 · VoxelBooking: voxel-source

Límites de cobertura
The project says there is no hosted plan at the captured revision.

Comprobado el 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.

Comprobado el 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.
Usuarios
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.

Comprobado el 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.

Comprobado el 11 nov 2026 · VoxelBooking: voxelbooking-project

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

Comprobado el 11 nov 2026 · Tidetime: tidetime-project

Sin verificar
Eventos
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.

Comprobado el 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.

Comprobado el 11 nov 2026 · VoxelBooking: voxelbooking-project

Agenda de equipo
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.

Comprobado el 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.

Comprobado el 11 nov 2026 · VoxelBooking: voxelbooking-project

Nota de cobertura

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.

Próximos pasos

  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de Tidetime en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de VoxelBooking en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Pregunta a VoxelBooking por este punto: calendarios. Nuestras fuentes aún no lo confirman.

Las comisiones nunca cambian los costes, la idoneidad ni el orden.