
# Customer support on Hostinger

Compare documented Customer support deployments on Hostinger, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/hostinger/customer-support/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Hostinger account and VPS
- Provider group: vps-hosting
- Provider classification: The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-20).
- Network: Customer server networking, DNS and firewall rules
- Identity and access: Cloud account access, server root/SSH access and application administrators
- Installation guidance: Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
- Guidance source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
- Guidance reviewed: 2026-11-13


### VPS hardening

The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer.
Source: https://www.hostinger.com/tutorials/vps-security/ (reviewed 2026-11-14).

The listings below have evidence for Hostinger. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## Combodo iTop (Community)

Community IT service-management application with tickets, configuration records and service workflows.

- Listing: https://launchinyourcloud.com/directory/itop/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: PHP application, database, attachments and scheduled jobs.
- Operations: 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.
- Product website: https://combodo.com/features/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community and commercially licensed extensions have different capabilities and entitlements.

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

PHP application, database, attachments and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Community IT service-management application with tickets, configuration records and service workflows.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/itop (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/itop
  PHP application, database, attachments and scheduled jobs. Community and commercially licensed extensions have different capabilities and entitlements.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Combodo/iTop/graphs/contributors

- Upstream project: https://github.com/Combodo/iTop

### Sources

- Hostinger: https://www.hostinger.com/applications/itop

- GitHub license.txt (AGPL-3.0): https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt

- GitHub Releases: https://github.com/Combodo/iTop/releases

### Licensing sources

- https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt

### Infrastructure sources

- https://www.hostinger.com/applications/itop


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The separately installed Combodo SAML extension authenticates pre-existing iTop ExternalUser accounts; it does not provision them. The vendor store offers free AGPL versions, while the current manual describes 1.2.6 requiring iTop 3.2+. Confirm the downloadable extension/version compatibility for Community 3.3 before installation. Scope: Optional SAML extension for self-hosted iTop; not an assertion that every Community package bundles it. Source: https://www.itophub.io/wiki/page?id=extensions:combodo-saml (reviewed 2026-11-20). Supporting source: Vendor extension store and available packages — https://store.itophub.io/en_US/products/combodo-saml.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The iTop 3.3 guide documents installing a Community distribution on a PHP/database host and running its web setup. Pin the application package and compatible extensions, configure web-server access and protect the setup directory; a third-party provider image is a separate artifact. Scope: Versioned upstream Community installation; distinct from a marketplace image. Source: https://www.itophub.io/wiki/page?id=3_3_0:install:start (reviewed 2026-11-20). Deployment artifact: https://github.com/Combodo/iTop/releases/tag/3.3.0-1. Artifact reference: 3.3.0-1.

- Minimum footprint / sizing: Documented. The 3.3 table recommends an all-in-one 2-vCPU, 4 GB RAM server with 10 GB database disk for under 20 console users, 200 monthly tickets and 50k CIs. Larger tiers split web/database servers; its >50-user tier lists 8 vCPU, 16 GB and 50 GB database disk. Validate per-server allocation, attachments and HA for your actual workload. Scope: Versioned workload tiers; database-disk figures are not total data capacity or a validated 100-user HA design. Source: https://www.itophub.io/wiki/page?id=3_3_0:install:requirements (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Combodo iTop (Community); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 3.3.0-1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Combodo iTop (Community) upstream application; verify compatibility with the selected package. Source: https://github.com/Combodo/iTop/releases/tag/3.3.0-1 (reviewed 2026-11-19).







## LibreDesk

Self-hosted shared inbox and customer support desk.

- Listing: https://launchinyourcloud.com/directory/libredesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: LibreDesk application, PostgreSQL, cache and persistent attachments.
- Operations: 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.
- Product website: https://libredesk.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.

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

LibreDesk application, PostgreSQL, cache and persistent attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted shared inbox and customer support desk.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/libredesk (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/libredesk (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/abhinavxd/libredesk/graphs/contributors

- Upstream project: https://github.com/abhinavxd/libredesk

### Sources

- Hostinger: https://www.hostinger.com/applications/libredesk

- Railway: https://railway.com/deploy/libredesk

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

- GitHub Releases: https://github.com/abhinavxd/libredesk/releases

### Licensing sources

- https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/libredesk

- https://railway.com/deploy/libredesk


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Agents can use Google, Microsoft or a custom OpenID Connect provider. Create local agent accounts first: LibreDesk matches the provider email to an existing agent and does not create accounts through SSO. Configure the issuer, credentials and registered callback URL. Scope: Current upstream agent-login configuration, also described by published v2.9.2 source. Source: https://docs.libredesk.io/configuration/sso (reviewed 2026-11-20). Supporting source: Published v2.9.2 feature and installation reference — https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published v2.9.2 recipe supplies Compose and configuration files for LibreDesk, PostgreSQL and Redis, or a standalone release binary. Set encryption material and the initial administrator password, pin compatible images and configure TLS, persistence and backups. Scope: Published upstream release recipe; the quickstart image tags still require an explicit pin. Source: https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/abhinavxd/libredesk/blob/v2.9.2/docker-compose.yml. Artifact reference: v2.9.2. Supporting source: Current installation and encryption-key guide — https://docs.libredesk.io/getting-started/installation.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide identifies the application, PostgreSQL and Redis but does not establish a whole-stack CPU/RAM/storage minimum for the selected workload. Size ticket/message throughput, attachments, retention, database and redundancy separately; a single binary does not imply a tiny HA deployment. Scope: Upstream topology confirmed; numeric production sizing remains unconfirmed. Source: https://docs.libredesk.io/getting-started/installation (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: LibreDesk; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.9.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: LibreDesk upstream application; verify compatibility with the selected package. Source: https://github.com/abhinavxd/libredesk/releases/tag/v2.9.2 (reviewed 2026-11-19).







## OTOBO

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

- Listing: https://launchinyourcloud.com/directory/otobo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Perl application, database, search, web server and background jobs.
- Operations: 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.
- Product website: https://github.com/RotherOSS/otobo
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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.


### Category fit

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

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/otobo (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/otobo
  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.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/RotherOSS/otobo/graphs/contributors

- Upstream project: https://github.com/RotherOSS/otobo

### Sources

- Hostinger: https://www.hostinger.com/applications/otobo

- GitHub LICENSE (GPL-3.0): https://raw.githubusercontent.com/RotherOSS/otobo/rel-11_1/LICENSE

- GitHub Releases: https://github.com/RotherOSS/otobo/releases

### Licensing sources

- https://raw.githubusercontent.com/RotherOSS/otobo/rel-11_1/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/otobo


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Versioned OTOBO 11.1 Kerberos/Nginx setup; not a generic SAML/OIDC claim. Source: https://doc.otobo.org/manual/installation/11.1/en/content/sso-kerberos.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Versioned OTOBO 11.1 installation with patch-matched Compose configuration. Source: https://doc.otobo.org/manual/installation/11.1/en/content/installation/installation-docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/RotherOSS/otobo-docker/tree/rel-11_1. Artifact reference: rel-11_1 (moving branch; guide requires selecting the matching patch tag).

- Minimum footprint / sizing: Documented. 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. Scope: Versioned production-versus-test host guidance; configure database and attachment storage separately. Source: https://doc.otobo.org/manual/installation/11.1/en/content/requirements.html (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: OTOBO; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/RotherOSS/otobo/rel-11_1/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






