Agendamento: comparação
Tidetime vs VoxelBooking
Preços, recursos documentados e limites de fontes oficiais datadas, lado a lado. O que é desconhecido continua desconhecido; unidades de cobrança diferentes não permitem comparar custos diretamente.
Última verificação das fontes: 11 de nov. de 2026
Para quem éTidetime describes self-hosted appointment scheduling for one company with multiple services and providers.
Última verificação das fontes: 11 de nov. de 2026
Para quem éVoxelBooking describes self-hosted booking for timeslots, resources, capacity and events.
O que as fontes respondem
Uma leitura da documentação oficial revisada de Tidetime e VoxelBooking. Não é um teste prático, um ranking nem a recomendação de um produto.
- Perguntas de compra respondidas para os dois
- 1 requisito
- Documentado para um só
- 1 requisito
- Não verificado para nenhum
- 0 requisito
- Preços
- Ainda não comparáveis
Preço
Tidetime
Plano gratuito · preços pagos não verificados ·
- Self-hosted: sem cobrança de assinatura ·
VoxelBooking
Plano gratuito · preços pagos não verificados ·
- Self-hosted: sem cobrança de assinatura ·
Ainda não há uma comparação de preços completa em condições equivalentes; os próximos passos dizem o que falta.
Perguntas de compra respondidas para os dois
Mesmo quando os rótulos coincidem, verifique em cada fonte as diferenças de planos, unidades e escopo.
- Agendamento em equipe
- 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 em termos não confirmados
Esses dados podem descrever medidas, mercados, idiomas ou escopos diferentes. Verifique cada plano, unidade e período antes de compará-los.
- Usuários
- 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.
Limites a verificar
- 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.
Ainda não verificado
Cada requisito comparado tem fontes para pelo menos um produto.
Documentado para um só produto, na tabela abaixo: Tidetime: calendários.
“Não verificado” significa que nossas fontes revisadas não estabelecem isso. Não significa que um produto não tenha o recurso nem que seja gratuito.
Evidências lado a lado
Valores documentados com fontes e datas de verificação; requisitos que as fontes não estabelecem continuam sinalizados.
- Documentado como compatível
- Documentado como não compatível
- Não verificado As fontes não estabelecem isso
- Não se aplica
| Requisito | Tidetime | VoxelBooking |
|---|---|---|
| Preços | Plano gratuito · preços pagos não verificados | Plano gratuito · preços pagos não verificados |
| Para quem | Tidetime describes self-hosted appointment scheduling for one company with multiple services and providers. Verificado em 3 de nov. de 2026 · Tidetime: tidetime-source | VoxelBooking describes self-hosted booking for timeslots, resources, capacity and events. Verificado em 3 de nov. de 2026 · VoxelBooking: voxel-source |
| Limites de cobertura | The project says there is no hosted plan at the captured revision. Verificado em 3 de nov. de 2026 · Tidetime: tidetime-source
| VoxelBooking documents deployment at the root of a domain or subdomain, rather than a subfolder. Verificado em 3 de nov. de 2026 · VoxelBooking: voxel-source
|
| Usuários | 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. Verificado em 11 de nov. de 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. Verificado em 11 de nov. de 2026 · VoxelBooking: voxelbooking-project |
| Calendários | 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. Verificado em 11 de nov. de 2026 · Tidetime: tidetime-project | Não verificado |
| 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. Verificado em 11 de nov. de 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. Verificado em 11 de nov. de 2026 · VoxelBooking: voxelbooking-project |
| Agendamento em equipe | 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. Verificado em 11 de nov. de 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. Verificado em 11 de nov. de 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 passos
- Confirme os preços dos planos pagos, o prazo de cobrança e os impostos de Tidetime na página oficial de preços; aqui só o plano gratuito está verificado.
- Confirme os preços dos planos pagos, o prazo de cobrança e os impostos de VoxelBooking na página oficial de preços; aqui só o plano gratuito está verificado.
- Pergunte a VoxelBooking sobre este ponto: calendários. Nossas fontes ainda não o confirmam.
- TidetimeIr para TidetimePerfil e planos
- VoxelBookingIr para VoxelBookingPerfil e planos
Comissões nunca mudam custos, elegibilidade ou ordem.