Scheduling comparison

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

What the evidence answers

A reading of reviewed official documentation for Calnode 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

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
Calnode The project documents team routing with fixed, round-robin, collective and priority assignment.
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
Calnode The project documents workspace members with owner, admin and member roles and email-token invitations.
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
Calnode The project documents event types with per-type duration, location, custom questions and custom email copy.
VoxelBooking The Event booking pattern lists RRULE recurring events, a waitlist and per-booking spot limits.

Limits to check

  • Calnode The repository says the generated encryption key must be backed up separately with the database.
  • Calnode Without Docker, the project’s GitHub releases include standalone Linux amd64 and arm64 archives of the static calnode binary, alongside SHA-256 checksums.
  • 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: Calnode: 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
Documented scope and limits; unverified dimensions remain unknown.
RequirementCalnodeVoxelBooking
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

Who it is for
Calnode describes a self-hosted scheduling application with booking pages and a SQLite database.

Verified Nov 5, 2026 · Calnode: calnode-project

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

Verified Nov 3, 2026 · VoxelBooking: voxel-source

Coverage limits
The repository says the generated encryption key must be backed up separately with the database.

Verified Nov 5, 2026 · Calnode: calnode-project

  • Self-hosted Without Docker, the project’s GitHub releases include standalone Linux amd64 and arm64 archives of the static calnode binary, alongside SHA-256 checksums.
VoxelBooking documents deployment at the root of a domain or subdomain, rather than a subfolder.

Verified Nov 3, 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.
Seats
The project documents workspace members with owner, admin and member roles and email-token invitations.

Publisher project README at release v0.14.0 (commit 9b363351) captured on 8 November 2026; supplier description, not a deployment or independent test. The captured README states no member or seat limit; each install is one workspace.

Verified Nov 8, 2026 · Calnode: calnode-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
The project documents Google Calendar and Microsoft 365/Outlook free/busy conflict checks, plus CalDAV calendars (iCloud, Fastmail, Nextcloud) with free/busy checks and event write-back.

Publisher project README at release v0.14.0 (commit 9b363351) captured on 8 November 2026; supplier description, not a deployment or independent test. Google, Microsoft and CalDAV accounts are the customer’s own and have separate terms.

Verified Nov 8, 2026 · Calnode: calnode-project

Not verified
Events
The project documents event types with per-type duration, location, custom questions and custom email copy.

Verified Nov 8, 2026 · Calnode: calnode-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
The project documents team routing with fixed, round-robin, collective and priority assignment.

Verified Nov 8, 2026 · Calnode: calnode-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

Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, third-party services and managed offerings have separate costs and terms.

Publisher project README at release v0.14.0 (commit 9b363351) captured on 8 November 2026; supplier description, not a deployment or independent test.

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 Calnode'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.

Commissions never change costs, eligibility or rankings.