OTOBO

Flexible web-based ticketing system used for customer service, help desk, IT service management.

Steady · 67
67/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 36/40
Releases 13/25
Community 3/20
Momentum 15/15

Commit activity more than 90% of tracked projects; popularity more than 17%. How this is calculated.

Commits, last 11 months

2025-10: 90 commits 2025-11: 61 commits 2025-12: 158 commits 2026-01: 154 commits 2026-02: 109 commits 2026-03: 151 commits 2026-04: 194 commits 2026-05: 250 commits 2026-06: 388 commits 2026-07: 319 commits 2026-08: 209 commits
2025-10 2083 total 2026-08
Stars337
Latest release—
Repo updated26 Sept 2026
LicenceGPL-3.0
Built withPerl, Docker

Is OTOBO actively maintained?

OTOBO is under active development: 2083 commits landed over the last 11 months, averaging roughly 305 commits a month in the most recent quarter.

Activity is accelerating: the last quarter carried 54% more commits than the one before it.

No tagged releases are published, so there is no stable version to pin to — you would deploy from the default branch or a container image built from it.

OTOBO ranks #8 of 22 in Ticketing, placing it mid-table for maintenance activity.

What OTOBO actually does

OTOBO is a web-based ticketing system designed to help organisations manage customer service requests, help desk queries, and IT service management workflows. It functions as a centralised platform for logging, tracking, and resolving incoming user support tickets. The application is built using Perl and supports containerised deployment via Docker.

Best fit: It is a suitable option for internal IT teams or customer support departments looking for an open-source, self-hosted help desk solution under the GPL-3.0 licence.

Worth knowing: With a relatively modest community footprint and niche popularity, you may find fewer third-party integrations, community plugins, and troubleshooting resources compared to more mainstream alternatives.

Deployment notes

As a web-based database application running in Docker, you will typically need to configure persistent storage volumes for your database and file attachments, alongside a reverse proxy to handle TLS termination.


OTOBO as a replacement for


Alternatives to OTOBO

Projects in the same categories, ordered by health score.