Rapla

Rapla is free, open-source software for planning events and scheduling rooms, people, and equipment. It is best suited to organizations that need configurable resource calendars and can manage a standalone or client-server deployment. Its stable Rapla 2 release covers the core scheduling job; Rapla 3’s newer capabilities come in nightly builds the maker considers untested and unsuitable for production.

Overview

Rapla brings resource booking and event planning into one system, with daily planning granularity and checks for conflicts before appointments are saved. That is a useful combination for institutions coordinating rooms, equipment, and people against the same calendar. The main trade-off is deployment: Rapla 2 runs standalone or in client-server mode, and its desktop client depends on Java and OpenWebStart rather than offering a broadly accessible hosted web service.

Key features

• Flexible scheduling: Month, week, day, and specialized calendar views, along with repeating appointments, cover recurring commitments as well as one-off events. Conflict detection helps prevent a resource clash before a booking is saved.
• Configurable administration: Administrators can define resource, person, and event types, categories, and attributes, then assign fine-grained permissions. This suits organizations with distinct booking rules, though it also means someone must shape and maintain that configuration.
• Sharing and alerts: PDF and iCal exports help users circulate schedules, and email notifications can alert users when a resource is allocated. These are practical handoffs, though they do not amount to a broader integration suite in the stable release.
• Storage choices: Data can be stored in a file or in MySQL, PostgreSQL, or HSQLDB. That gives administrators deployment flexibility, but makes the setup a better fit for organizations prepared to manage their chosen storage environment.
• Newer integrations: Rapla 3 describes Exchange synchronization to booked people’s Outlook calendars, a GraphQL API, OAuth 2.0 with PKCE, sign-in through Microsoft, Google, or Keycloak, and scoped API keys. These capabilities may matter to organizations planning integrations, but nightly builds are self-signed, untested, and not for production. iCal subscription and import are planned rather than available.

Pricing

Rapla (open-source software): free. The software is open source under AGPL-3.0-or-later or Apache-2.0, and no paid plans are listed. That makes it a straightforward option for organizations seeking a no-license-fee scheduler; the trade-off is taking responsibility for deployment and administration rather than buying a paid hosted tier.

Platforms

Rapla is listed for Linux, macOS, Windows, and self-hosted use. Rapla 2’s desktop client supports Linux, Windows, and macOS and uses Java and OpenWebStart; it can run standalone or in client-server mode. The interface is available in English and German, with translations of varying completeness in French, Dutch, Polish, Spanish, Finnish, Brazilian Portuguese, and Czech.

The maker says rapla.org and its demo run on EU-located infrastructure under a data processing agreement. Demo entries are visible to other visitors and removed in a nightly reset, so the demo is not appropriate for confidential scheduling.

Who it's for

The maker identifies universities, schools, hospitals, gyms, and seminar houses as users of Rapla for scheduling rooms, people, and equipment. It is a strong fit where those resource types need configurable calendars, permissions, and exportable schedules, and where an organization can operate a desktop or client-server installation. It is a weaker fit for teams that need a production-ready web service with modern integrations immediately: Rapla 3’s integration features are still in nightly builds.

Support paths include a wiki, documentation overview, FAQ, GitHub issues, and third-party professional support providers. That gives administrators several ways to seek help, though the need to configure and run the system remains part of choosing it.

Pros and cons

• Pro: No-cost open-source licensing avoids per-seat software fees while supporting scheduling for rooms, people, and equipment.
• Pro: Conflict checks, repeating appointments, configurable resource types, and fine-grained permissions address the practical complexities of institutional booking.
• Pro: File and database storage options, plus PDF and iCal export, give administrators flexibility in how they operate and share schedules.
• Con: Rapla 2’s Java and OpenWebStart desktop client, or its client-server deployment, requires more operational ownership than a hosted scheduling service.
• Con: Rapla 3’s Exchange sync, API, and identity features are not production-ready, limiting their value for organizations that need those integrations now.
• Con: Translation completeness varies, which may make the interface less suitable for teams relying on some of the supported languages.

Alternatives

Consider Teamdeck if you want a freemium option with Android, iOS, web, and desktop platform coverage; its free Startup plan is capped at six team members. Choose Ganttic if a free resource-planning option with Gantt charts, reports, and Kanban boards is a better fit; its free plan allows up to 10 resources with unlimited users and projects.

LibrePlan is another open-source, self-hosted option, with a Community Edition and a separate commercial Enterprise Edition. SAVIOM is a paid alternative with Power and Lite license options. Tempo Portfolio Manager may suit teams focused on project portfolios: its free plan allows 10 members, 3 projects, and 300 tasks. Mosaic is a paid alternative. Napta is another paid alternative. Retain is a paid alternative whose cloud plan is priced by quote.

For a wider comparison, browse Resource Management Software or Calendar apps.

Verdict

Choose Rapla if your organization needs free, open-source scheduling for rooms, people, or equipment and values configurable calendars, permissions, and exports. Its stable Rapla 2 release is the safer choice for operational use; look elsewhere if you need a hosted service or production-ready integrations beyond its current stable capabilities.