MRBS, the Meeting Room Booking System, is a PHP-based application for booking meeting rooms.
Dated publisher project README captured on 7 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Prebuilt releases need PHP 8.2 or later with listed extensions, Apache 2.4 or later (other web servers are not supported or tested) and MySQL 8.0+ or MariaDB 10.6+.
MRBS needs PHP 7.2.5 or above with MySQL and/or PostgreSQL support, MySQL 5.5.3 or above or PostgreSQL 8.2 or above, and any web server that PHP supports.
Publisher project README at release v1.12.3 (commit 299686ed) captured on 9 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms. Corrects the earlier statement of PHP 7.2 to the PHP 7.2.5 minimum in the current README.
The project documents admin and user roles, with the first registered user becoming admin, and settings to disable open registration or restrict it by email domain.
Publisher project README at release v1.23.3 (commit 53c5e3c7) captured on 9 November 2026; supplier description, not a deployment or independent test. The captured README states no user or seat limit.
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.
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.
Participants, the people who can vote on polls, are unlimited on both Hobby and Pro.
Rallly pricing page captured on 9 November 2026; supplier statement, not a purchase or test. This describes voters, not paid seats: Pro is priced per seat, and the passage does not say whether voters use seats. The README adds that participants need no account to vote.
Microsoft states that Bookings supports up to 100 staff members in a Bookings page.
Microsoft Learn source (MicrosoftDocs/microsoft-365-docs, CC-BY-4.0) article Add team members to Bookings at commit ee0f8f75 captured on 9 November 2026; supplier documentation, not a deployment or independent test. Applies to shared Bookings pages.
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.
Poll creators can choose whether anonymous votes are allowed or voters must give a name, and whether registration is required for voting.
Dated publisher project README captured 9 November 2026; supplier description, not a deployment or independent test. Feature list only; no poll was created and no seat or user limit is stated.
MRBS documents three access levels: unknown users who can view most pages but change nothing, authenticated users who can make and change their own bookings, and administrators who can modify other people's bookings and add or remove rooms and areas.
Publisher authentication documentation on the project website, captured on 9 November 2026; supplier description, not a deployment or independent test. The captured page states no user or seat limit.
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.
The project lists Google Calendar synchronization.
Publisher project README at release 1.6.1 (commit d30cba6d) captured on 9 November 2026; supplier description, not a deployment or independent test. The README does not name other calendar providers or describe two-way behaviour.
Microsoft documents a setting that makes the free/busy information from staff members' calendars affect their bookable availability.
Microsoft Learn source (MicrosoftDocs/microsoft-365-docs, CC-BY-4.0) article Add team members to Bookings at commit ee0f8f75 captured on 9 November 2026; supplier documentation, not a deployment or independent test. Applies to shared Bookings pages. The same article says the setting is on by default and that staff from outside the tenant cannot share free/busy information with Bookings.
The project documents connected calendars from Google, Microsoft 365, CalDAV (such as iCloud, Fastmail or Nextcloud) and ICS feeds.
Publisher project README at release v1.3.1 (commit 46c1fc0b) captured on 9 November 2026; supplier description, not a deployment or independent test. Google, Microsoft and CalDAV accounts are the customer's own and have separate terms.
The architecture documentation lists Google (through the Google API) and CalDAV as calendar connections that Appointment can query and write event data to.
Publisher architecture documentation (docs/README.md) at release r-0954 (commit ecdda9f7) captured on 9 November 2026; supplier description, not a deployment or independent test. The document itself says its component chart is slightly outdated. Calendar sync was not tested.
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.
Per-resource iCalendar and RSS feeds, a tablet display and an embeddable calendar snippet become available once Public Access is enabled for that resource; they are off by default.
Publisher administration guide (docs/source/ADMINISTRATION.rst) at release v7.2.0 (commit bfb13ca2) captured on 8 November 2026; supplier description, not a deployment or independent test. The README feature list also names Outlook/Thunderbird integration through ICS. No two-way calendar sync is claimed.
The Free plan lists Microsoft Exchange synchronization, a Microsoft Teams integration and an Atlassian Confluence integration; the page does not say what the Exchange synchronization covers.
Seatsurfing pricing page captured on 9 November 2026; supplier statement, not a purchase or test. Professional says "Everything from Free, plus", so these carry over. The README calls the Confluence integration a Cloud-only feature. Which calendars sync was not established, and nothing was tested.
The README lists Google Calendar, Outlook and Apple Calendar integration.
Publisher project README at default-branch commit 743f3c6f (no releases) captured on 9 November 2026; supplier description, not a deployment or independent test. The deployment guide lists a Google OAuth client ID and secret as required settings and Microsoft OAuth credentials as optional, for Outlook; no integration was tested.
Polls can show hints about possibly conflicting calendar entries around a date option.
Publisher project README at release v9.3.0 (commit 8f3286cf) captured on 8 November 2026; supplier description, not a deployment or independent test. The README does not say which calendars are checked and does not describe writing entries to a calendar.
CloudMeet connects Google Calendar and Outlook Calendar, alone or together; when both are connected, availability is checked across both.
Publisher project README at default-branch commit f6581c9d (no release tags) captured on 8 November 2026; supplier description, not a deployment or independent test. Outlook needs the operator’s own Microsoft Entra app registration, per the same README.
The project's NEWS file records that bookings can be exported as ICS from the search page.
Entry under Version 1.11.6 (6 November 2024) in the NEWS file at release v1.12.3 (commit 299686ed), captured on 9 November 2026; a changelog line, not a deployment or independent test. The same file also records importing an iCalendar from a URL in Version 1.10.0.
Meeting types support durations, custom questions, booking limits, approval before confirming and several locations per type for the guest to pick from.
Dated publisher project README at release v1.41.0 (commit 37b6b4f1) captured on 9 November 2026; supplier description, not a deployment or independent test. The README states no limit on the number of meeting types. Group bookings and paid bookings are not described in the cited passage.
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.
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.
The project lists service and provider organization together with working plans and booking rules.
Publisher project README at release 1.6.1 (commit d30cba6d) captured on 9 November 2026; supplier description, not a deployment or independent test. Bookings are organised as services offered by providers; event types, durations, buffers and group capacity are not described in the captured README.
Rallly polls propose multiple date and time options that participants vote on, and the poll owner finalises one option and notifies everyone.
Publisher project README at the latest GitHub release (commit 4e2bd067) captured on 9 November 2026; supplier description, not a deployment or independent test.
Microsoft documents three service types: 1:1 (one staff member, one customer, the default), 1:N (one staff member, several customers) and N:N (several staff members, several customers).
The project documents booking pages with several durations, locations (in person, phone, link, Jitsi, Google Meet, Microsoft Teams and Zoom), booking questions, seats and recurring bookings, plus requires-confirmation, limits, single-use links and cancellation policies.
A schedule sets the selected weekdays, the slot duration, the earliest and farthest booking limits, an optional meeting-link provider (for example Zoom) and whether booking requests need the owner’s confirmation.
Publisher architecture documentation (docs/README.md) at release r-0954 (commit ecdda9f7) captured on 9 November 2026; supplier description, not a deployment or independent test. The document itself says its component chart is slightly outdated.
The README lists specifying date and time ranges to meet between, "Available" versus "If needed" times, and duplicating polls.
Publisher project README at default-branch commit 743f3c6f (no releases) captured on 9 November 2026; supplier description, not a deployment or independent test. The README also lists exporting availability as CSV and showing responses only to the event creator.
Polls offers two poll types: date polls and text polls.
Published OpenAPI specification (openapi.json) of release v9.3.0 (commit 8f3286cf) captured on 8 November 2026: the poll-creation request names the poll types. Supplier documentation, not a hands-on test.
Polls can be created for a full-day event or for just a few hours, with custom classes, and the poll URL can be set manually or chosen randomly.
Dated publisher project README captured 9 November 2026; supplier description, not a deployment or independent test. Feature list only; no poll was created.
Multiple event types, each with its own buffer, minimum notice, booking window and custom hours.
Publisher project README at default-branch commit f6581c9d (no release tags) captured on 8 November 2026; supplier description, not a deployment or independent test. The README FAQ says recurring meetings are not supported: every booking is a single meeting.
The project site lists flexible repeating bookings, conflict prevention, booking reports, day, week and month views, and bookings by time or by period.
Publisher project website captured on 9 November 2026; supplier description, not a deployment or independent test. MRBS books meeting rooms and other shared resources; event types, buffers and round-robin routing are not described.
The project documents team scheduling in round-robin mode with least-busy assignment and in collective mode where all members must be free.
Publisher project README at release v1.23.3 (commit 53c5e3c7) captured on 9 November 2026; supplier description, not a deployment or independent test. The README also describes dynamic group links that intersect several users' calendars.
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.
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.
Rallly offers a shared team space where members create and manage polls together, with one subscription covering the whole team.
Rallly pricing page captured on 9 November 2026; supplier statement, not a purchase or test. The comparison table lists Team collaboration as Included on Pro and Not included on Hobby; the FAQ passage does not name a plan.
The project documents collective and round-robin event types with weights, priority and fixed hosts, managed event types, dynamic group links, a team availability view and routing forms.
Users in a group given the Group Administrator role can reserve on behalf of, and manage, the users in that group.
Publisher administration guide (docs/source/ADMINISTRATION.rst) at release v7.2.0 (commit bfb13ca2) captured on 8 November 2026; supplier description, not a deployment or independent test. The same guide says Group Administrators cannot create user accounts or change a user’s resource permissions; only Application Administrators can. Delegated resource booking, not round-robin meeting routing.
The README lists finding when a subset of people are available, scheduling across time zones, email notifications and reminders, and availability groups that follow people’s real-time calendar availability.
Publisher project README at default-branch commit 743f3c6f (no releases) captured on 9 November 2026; supplier description, not a deployment or independent test. Described as group availability polling; no round-robin or booking-page routing is described.
Poll owners can invite participants, let Polls remind invited users automatically and confirm options after the poll closes.
Publisher project README at release v9.3.0 (commit 8f3286cf) captured on 8 November 2026; supplier description, not a deployment or independent test. Group date polling for finding a common time; no round-robin or collective booking is described.
Polls can be created as private events that only invited people can access.
Dated publisher project README captured 9 November 2026; supplier description, not a deployment or independent test. Feature list only; how invitations are sent is not described and no poll was created.
Official documentation checked on 18 October 2026; no hands-on test.
Official documentation checked on 18 October 2026; no hands-on test.
Official documentation checked on 18 October 2026; no hands-on test.
Project-maintained documentation captured 3 November 2026; scope is the described software, not an independently performed test, universal hosted plan, security audit or price claim.
Project-maintained documentation captured 3 November 2026; scope is the described software, not an independently performed test, universal hosted plan, security audit or price claim.
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.
Publisher project README at the captured revision, 4 November 2026. No account, installation, appointment, poll, integration or performance test. Exact release, hosted services and third-party terms require separate review.
Publisher project README at the captured revision, 4 November 2026. No account, installation, appointment, poll, integration or performance test. Exact release, hosted services and third-party terms require separate review.
Microsoft Learn source (MicrosoftDocs/microsoft-365-docs, CC-BY-4.0) article Creating personalized and group services in Microsoft Bookings at commit ee0f8f75 captured on 9 November 2026; supplier documentation, not a deployment or independent test. The article describes the feature as part of Microsoft 365 Business Basic.
Publisher project README at release v1.3.1 (commit 46c1fc0b) captured on 9 November 2026; supplier description, not a deployment or independent test.
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.
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.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Réponses rapides
Questions sur Planification
Quels outils de planification proposent une offre gratuite ?
Calendly, Cal.com, Tymeslot, calrs, VoxelBooking, Tidetime, Easy!Appointments, Rallly, OpenCalendar, Thunderbird Appointment, Calnode, LibreBooking, Seatsurfing, Timeful, Polls for Nextcloud, CloudMeet et MRBS documentent une offre gratuite sur leurs pages de tarifs officielles. Les offres gratuites limitent généralement l’usage, le nombre d’utilisateurs ou les fonctionnalités ; vérifiez les limites dans chaque fiche.
Combien coûte un logiciel de planification ?
Parmi les prix d’entrée documentés des offres payantes : Calendly à partir de 10,00 par utilisateur (devise non précisée), Cal.com à partir de 144,00/an par utilisateur (devise non précisée), SavvyCal à partir de 10,00 par utilisateur (devise non précisée), Tymeslot à partir de 9 €/mois et Rallly à partir de 6 $US/mois par utilisateur. Les prix proviennent des pages officielles aux dates indiquées ; les unités et les périodes de facturation diffèrent, comparez donc des offres équivalentes.