LibreBooking
Resource scheduling fork for rooms, equipment, and shared assets
oss-osi-approved planned guide featuredOverview
LibreBooking is an open-source resource reservation system (community continuation of Booked Scheduler concepts). Operators schedule meeting rooms, phone booths, AV kits, and event spaces with quotas and blackout dates.
At a glance
| Field | Value |
|---|---|
| Categories | booking-scheduling, event-management |
| Deployment | self-hosted |
| License class | oss-osi-approved (GPL-3.0-only) |
| Cost model | free-self-hosted |
| Implementation difficulty | moderate |
| Maintenance burden | medium |
| Maturity | stable |
| Verification | partially-verified (2026-07-17) |
Cost reality
Free software with self-hosting costs only.
Pricing and free-tier limits change frequently; re-check official pricing before budget decisions.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Room reservation without commercial workplace suites
- Equipment checkout tracking
- Blackout windows for cleaning and events
Human oversight still needed
- Conflict resolution
- No-show policy enforcement
- Access to reservation PII
Data held
-
reservations
-
resources
-
users
-
announcements
-
Personal data: yes
-
Payment data: no / not primary
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Evaluate export formats and API completeness before deep customization. |
| Security | Apply updates promptly; restrict admin access; enable TLS. |
| Compliance | Operator remains responsible for privacy and local regulatory obligations. |
| Licensing | Verify LICENSE in the active repository fork you deploy. |
| Operational | Plan backups, monitoring, and a restore drill before production use. |
Coworking fit
Roles: operations-manager, community-manager, event-coordinator
Workflows: room-booking, event-lifecycle, facility-maintenance
Problems: fill-meeting-rooms, replace-spreadsheets, improve-member-experience
Smallest useful experiment
Configure three meeting rooms with business-hour rules and run bookings for one week with staff as fake members.
Typical time to first value: 1–3 days
Links
Implementation guide
A routable implementation guide is not currently published.
Verification
- Status:
partially-verified - Last reviewed:
2026-07-17 - Sources:
Seed entry compiled from official project sites and repositories. Re-verify pricing, license text, and feature claims before production decisions. Star counts and free-tier numeric limits intentionally omitted unless verified at review time.