Scheduling comparison
Tidetime vs VoxelBooking
Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.
Latest evidence check Nov 11, 2026
Who it is forTidetime describes self-hosted appointment scheduling for one company with multiple services and providers.
Latest evidence check Nov 11, 2026
Who it is forVoxelBooking describes self-hosted booking for timeslots, resources, capacity and events.
What the evidence answers
A reading of reviewed official documentation for Tidetime and VoxelBooking. It is not a hands-on test, a ranking or a recommendation of one product.
- Common buyer questions answered
- 1 requirement
- Documented for one
- 1 requirement
- Not verified for either
- 0 requirements
- Prices
- Not like-for-like yet
Price
Tidetime
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
VoxelBooking
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
A complete like-for-like price comparison is not established; the next steps say what is missing.
Common buyer questions answered
Even when labels match, check each source for differences in plans, units and scope.
- Team scheduling
- 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.
Documented in unconfirmed terms
These facts may describe different measures, markets, languages or scopes. Check each plan, unit and period before comparing them.
- Seats
- 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.
- Events
- 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.
Limits to check
- 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.
Not verified yet
Every compared requirement has evidence for at least one.
Documented for one product only, shown in the table below: Tidetime: calendars.
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
| Requirement | Tidetime | VoxelBooking |
|---|---|---|
| Pricing | Free plan · paid prices not verified | Free plan · paid prices not verified |
| Who it is for | Tidetime describes self-hosted appointment scheduling for one company with multiple services and providers. Verified Nov 3, 2026 · Tidetime: tidetime-source | VoxelBooking describes self-hosted booking for timeslots, resources, capacity and events. Verified Nov 3, 2026 · VoxelBooking: voxel-source |
| Coverage limits | The project says there is no hosted plan at the captured revision. Verified Nov 3, 2026 · Tidetime: tidetime-source
| VoxelBooking documents deployment at the root of a domain or subdomain, rather than a subfolder. Verified Nov 3, 2026 · VoxelBooking: voxel-source
|
| Seats | 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 | 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. Verified Nov 11, 2026 · VoxelBooking: voxelbooking-project |
| Calendars | 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 | Not verified |
| Events | 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 | 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. Verified Nov 11, 2026 · VoxelBooking: voxelbooking-project |
| Team scheduling | 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 | 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. Verified Nov 11, 2026 · VoxelBooking: voxelbooking-project |
| Coverage note | 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. |
Next steps
- Confirm Tidetime's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
- Confirm VoxelBooking's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
- Ask VoxelBooking about calendars; our sources do not establish it yet.
- TidetimeVisit TidetimeProfile and plans
- VoxelBookingVisit VoxelBookingProfile and plans
Commissions never change costs, eligibility or rankings.