OTOBO is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. https://otobo.io/
  • Perl 96%
  • JavaScript 2.9%
  • CSS 0.9%
Find a file
bernhard 45487a3605 Update the CPAN snapshot file
-  Cpanel-JSON-XS-4.40 => 4.41
-  Template-Toolkit-3.105 => 3.106
2026-05-30 19:44:52 +02:00
.github Github actions: upgrade some more shared actions 2026-04-23 13:03:35 +02:00
bin Issue #5532: require the Docker versions for cpanfile.plackup 2026-05-19 15:19:15 +02:00
Custom Issue #20: remove references and workarounds for PerlEx 2020-05-14 12:52:56 +02:00
development Merge branch 'rel-10_1' into rel-11_0 2026-04-13 12:46:22 +02:00
doc Fixed issue #313. Thanks to Helmut Wollmersdorfer! 2020-08-05 22:48:47 +02:00
hooks Merge branch 'rel-10_1' into rel-11_0 2024-07-30 17:45:07 +02:00
i18n/otobo Deploy new language files. 2026-05-26 14:28:05 +02:00
Kernel Merge branch 'rel-10_1' into rel-11_0 2026-05-30 19:27:26 +02:00
scripts Merge branch 'rel-10_1' into rel-11_0 2026-05-28 14:32:19 +02:00
var Merge branch 'rel-10_1' into rel-11_0 2026-04-27 11:14:05 +02:00
.bash_completion Issue #4995: update the copyright year range to 2019-2026 2026-01-16 12:05:13 +01:00
.dockerignore Issue #4707: we need cpanfile.docker.snapshot in the Docker image 2025-09-17 17:24:47 +02:00
.fetchmailrc.dist Issue #4995: update the copyright year range to 2019-2026 2026-01-16 12:05:13 +01:00
.gitattributes Issue #4731: Add CHANGES.md and language files as merge=ours to gitattributes. 2025-11-12 14:51:15 +01:00
.gitignore Merge branch 'rel-10_1' into rel-11_0 2025-11-21 12:29:02 +01:00
.mailfilter.dist Issue #4995: update the copyright year range to 2019-2026 2026-01-16 12:05:13 +01:00
.perlimports.toml Tidy some more perlimports. 2024-02-18 13:19:53 +01:00
.procmailrc.dist Issue #4995: update the copyright year range to 2019-2026 2026-01-16 12:05:13 +01:00
.screenrc Issue #4995: update the copyright year range to 2019-2026 2026-01-16 12:05:13 +01:00
AUTHORS.md Issue #3425: Updated mail addresses. 2024-06-17 14:32:28 +02:00
CHANGES.md Fix CHANGES. 2026-04-23 10:02:23 +02:00
CONTRIBUTING.md Updated CONTRIBUTING.md file by copying section from README.md. 2026-01-15 13:52:20 +01:00
COPYING-Third-Party Merge branch 'rel-10_1' into rel-11_0 2026-03-24 09:58:33 +01:00
cpanfile Merge branch 'rel-10_1' into rel-11_0 2026-05-05 11:17:32 +02:00
cpanfile.docker Merge branch 'rel-10_1' into rel-11_0 2026-05-05 11:17:32 +02:00
cpanfile.docker.snapshot Update the CPAN snapshot file 2026-05-30 19:44:52 +02:00
cpanfile.plackup Issue #5532: require the Docker versions for cpanfile.plackup 2026-05-19 15:19:15 +02:00
INSTALL.md Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00
LICENSE Initial commit 2020-01-30 21:46:00 +01:00
otobo.elasticsearch.dockerfile Issue #4427: updated code comment concerning the base image 2026-04-14 16:12:18 +02:00
otobo.kerberos.web.dockerfile Issue #3628: prematurely removed the dummy Kerberos Dockerfiles 2024-07-31 09:23:58 +02:00
otobo.nginx-kerberos.dockerfile Merge branch 'rel-10_0' into rel-10_1 2025-01-15 14:31:31 +01:00
otobo.nginx.dockerfile Merge branch 'rel-10_1' into rel-11_0 2025-10-14 17:27:13 +02:00
otobo.selenium-chrome.dockerfile Issue #4839: reinstate the target otobo-selenium-chrome 2025-12-01 18:28:53 +01:00
otobo.web.dockerfile Merge branch 'rel-10_1' into rel-11_0 2026-04-03 16:31:25 +02:00
README.md Merge branch 'rel-10_1' into rel-11_0 2024-07-25 15:49:56 +02:00
RELEASE Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00
SECURITY.md Mention the end of life date of OTOBO 10.0.x in SECURITY.md 2026-01-20 13:48:09 +01:00
UPDATING.md Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00

What is OTOBO?

OTOBO is an extremely flexible, web-based open-source ticketing tool. The application is used for streamlining communication in service organisations such as IT helpdesks, customer service centers, call centers etc.

It provides classical ticketing functionality, a knowledgebase/FAQs with internal and external interface, helps to automate processes and can be extended by an ITSM component with a CMDB to keep track of IT components or buildings, office plants, cars etc.

OTOBO is a fork based on ((OTRS)) Community Edition, started in 2019 to go back to the roots and offer a 100 % free tool, rooted in a strong community, and backed up by professional business services.

Find a list of features here.

License

OTOBO is distributed under the GNU General Public License - see the accompanying LICENSE file for more details.

Documentation

OTOBO documentation can be found at https://doc.otobo.org/

The source code of OTOBO and its extension modules is available on GitHub.

Professional Services for OTOBO

OTOBO is a mighty and highly flexible tool. Pretty much everything can be individualized and adapted to your needs. And more often than not there is more than one way to achieve a goal.

No reason to feel overwhelmed, though. We are happy to help adapt the system optimally to your needs, make sure you take full advantage of it, and assist in securing your operations. Theres also a fully managed version of OTOBO if you do not want to take care of that yourself.

We are Rother OSS GmbH, source code owner of OTOBO. Founder Stefan Rother was first employee of OTRS GmbH back in 2004, and created Rother OSS when he left there in 2011. We have been working with the ticketing tool ever since, and know what we are doing.

Read more about

Or directly get in touch.

Software requirements

The software and hardware requirements can be found in our documentation.

How to contribute

We take the open-source idea very seriously and explicitly invite the community to engage with us.

If you have a request or think you have found a bug, please visit our forums or open an issue on GitHub.

To make our lives a bit easier, please

  • Search the forums before issuing new topics
  • Try to be as precise and complete as possible when reporting bugs it helps a lot if we know how to reproduce them
  • Use the labels provided on GitHub to categorize your request
  • Start a pull request, if you have implemented a feature or fix yourself.

THANK YOU!