OTOBO

Self-hosted service desk for tickets, queues, service workflows and customer records.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker / Compose
InfrastructureServers / containers
Perl application, database, search, web server and background jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The OTOBO 11.1 Docker guide documents Kerberos SSO through its Nginx proxy with an Active Directory service principal/keytab and browser configuration. Enable the application HTTP authentication backend and map existing users; LDAP password checks and mailbox OAuth alone are different paths.

Versioned OTOBO 11.1 Kerberos/Nginx setup; not a generic SAML/OIDC claim · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The 11.1 guide recommends Docker Compose and links the otobo-docker repository. Select the patch-matched tag, configure .env, passwords, persistent volumes and TLS, then run the application installer. The base stack and HTTP/HTTPS overrides are separate files; do not treat the moving branch as a fixed application version.

Versioned OTOBO 11.1 installation with patch-matched Compose configuration · Source ↗ · Deployment artifact ↗ (rel-11_1 (moving branch; guide requires selecting the matching patch tag)) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The 11.1 guide gives a test baseline of 4 GB RAM and 10 GB storage, and a production starting point of a 3 GHz Xeon-class CPU, 8 GB RAM (16 GB recommended) and 40 GB storage. Ticket volume and attachments drive sizing; these are not a replicated 1 TB HA specification.

Versioned production-versus-test host guidance; configure database and attachment storage separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

OTOBO; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

OTOBO is maintained separately from historical OTRS editions; extensions and support contracts have their own scope.

Community & maintenance

The reviewed upstream contributor history includes bschmalhofer, stefanhaerter, MichaelThumes, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Customer support
Self-hosted service desk for tickets, queues, service workflows and customer records.

Compare within Customer support

  • Chatwoot Self-HostedSelf-hosted customer-support inbox combining live chat, email and messaging conversations.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Combodo iTop (Community)Community IT service-management application with tickets, configuration records and service workflows.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Deskpro Private — Self-HostedCommercial helpdesk installed on customer servers or in customer-controlled private infrastructure.
    • AWS
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core
  • django-helpdeskDjango-based helpdesk for tickets, queues and support communication.
    • Azure
    Customer-operated · Open Source / Open Core
  • Frappe HelpdeskSelf-hosted support desk for tickets, knowledge content and service operations.
    • Azure
    Customer-operated · Open Source / Open Core
  • Jira Service Management Data CenterCommercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • LibreDeskSelf-hosted shared inbox and customer support desk.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core

Showing 8 of 14 other listings in Customer support. These products address related workflows; read their category-fit notes before comparing scope. See all of Customer support →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Perl application, database, search, web server and background jobs. OTOBO is maintained separately from historical OTRS editions; extensions and support contracts have their own scope.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory