
# Zammad

Self-hosted helpdesk and ticketing application for customer service and internal support teams.

Canonical page: https://launchinyourcloud.com/directory/zammad/
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.


1 listing.


## Zammad

Self-hosted helpdesk and ticketing application for customer service and internal support teams.

- Listing: https://launchinyourcloud.com/directory/zammad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 repository license for the core application
- Licensing model: open-source
- Installation: Official Linux packages; Docker Compose and Kubernetes alternatives are documented
- Architecture: Persistent application and worker services with PostgreSQL, Redis and a web proxy; Elasticsearch is strongly recommended for search.
- Operations: Customer runs the application stack, database, backups and security updates; follow supported distribution and release requirements.
- Product website: https://zammad.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted helpdesk core. The official repository supplies an AGPL-3.0 license, although the marketing open-source page labels it GPL v3; verify the license shipped with the selected release. Zammad 7.2.3 is a critical security release and self-hosted operators should upgrade immediately. Package installations using nginx or Apache must update the reverse-proxy configuration for the Remote-User header; Docker images include the change.

The listed self-hosted core repository supplies the GNU Affero GPL version 3. The vendor describes the full helpdesk as open source; separately purchased services or integrations are outside this classification. Marketing shorthand says GPL v3, so check the selected release's supplied license for exact terms.

The official system documentation describes persistent Linux application services, PostgreSQL, Redis and proxy services, with container-stack alternatives. Elasticsearch is strongly recommended rather than a hard dependency.


### Category fit

- customer-support: Agent helpdesk with tickets, customer communication, configurable fields and a knowledge base.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/zammad (checked 2026-11-12). Source: https://github.com/gridalpha/zammad-railway/blob/main/zammad/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Zammad community deployment on Railway (railway): https://railway.com/deploy/zammad
  The community recipe deploys Zammad application roles with PostgreSQL, Redis, Memcached and Elasticsearch in a customer project. Its wrapper builds on the official Zammad image and adapts storage/bootstrap configuration for Railway. Review all image versions, object-storage settings, credentials, email integration and upgrades; this is not Zammad hosted service.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the Zammad Railway application wrapper (railway): https://github.com/gridalpha/zammad-railway/blob/main/zammad/Dockerfile
  The inspected application wrapper derives from ghcr.io/zammad/zammad and supplies Railway-specific startup/bootstrap behavior. The tag is configurable; pin and review it together with the backing services rather than assuming that latest remains compatible.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official case studies document daily customer-support use by Nextcloud and De'Longhi, without establishing every customer's hosting model. The release page records the 7.2.3 critical security update on November 11, 2026, and directs self-hosted installations to upgrade immediately, providing maintenance evidence beyond repository popularity.

Reviewed 2026-11-13.

- Named customer-support adopters: https://zammad.com/en/customers

- Nextcloud implementation story: https://zammad.com/en/customers/nextcloud

- Recent feature and security maintenance: https://zammad.com/en/product/releases

- 7.2.3 critical security release: https://zammad.com/en/product/releases/7-2-3

### Sources

- Official Linux package installation: https://docs.zammad.org/en/latest/install/package.html

- Server, database and deployment prerequisites: https://docs.zammad.org/en/latest/prerequisites/software.html

- Helpdesk and customer support features: https://zammad.com/en/product/features

- Zammad core repository license: https://raw.githubusercontent.com/zammad/zammad/develop/LICENSE

- Vendor open-source policy: https://zammad.com/en/company/open-source

- Supported and emergency security releases: https://zammad.com/en/product/releases

- November 2026 critical security release: https://zammad.com/en/product/releases/7-2-3

- Customer support implementation stories: https://zammad.com/en/customers

- Nextcloud customer support case study: https://zammad.com/en/customers/nextcloud

### Licensing sources

- https://raw.githubusercontent.com/zammad/zammad/develop/LICENSE

- https://zammad.com/en/company/open-source

### Infrastructure sources

- https://docs.zammad.org/en/latest/install/package.html

- https://docs.zammad.org/en/latest/prerequisites/software.html


### 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 administrator guide documents SAML and OpenID Connect login with your identity provider. Configure issuer/client credentials, claim mapping and account-linking policy; this does not establish automatic lifecycle provisioning. Scope: Self-hosted Zammad application login, with administrator configuration. Source: https://admin-docs.zammad.org/en/latest/settings/security/third-party/openid-connect.html (reviewed 2026-11-20). Supporting source: SAML configuration — https://admin-docs.zammad.org/en/latest/settings/security/third-party/saml.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide links the Zammad Docker Compose repository and its deployment scenarios. Vendor support covers the Zammad application, not Docker/Compose or Portainer-specific problems; configure HTTPS separately. Scope: Official self-hosted Compose deployment; infrastructure support is separate. Source: https://docs.zammad.org/en/latest/install/docker-compose.html (reviewed 2026-11-14). Deployment artifact: https://github.com/zammad/zammad-docker-compose. Artifact reference: master (moving branch; select matching release/scenario).

- Minimum footprint / sizing: Documented. The hardware guide gives a 2-core, 6 GB RAM minimum baseline with PostgreSQL, plus 4 GB if Elasticsearch shares the host. Its Docker guide separately says at least 4 GB for containers; these are different baselines, not a complete production sizing plan. Scope: Current self-hosted hardware guidance; selected topology and ticket load govern sizing. Source: https://docs.zammad.org/en/latest/prerequisites/hardware.html (reviewed 2026-11-14). Supporting source: Docker-specific prerequisites — https://docs.zammad.org/en/latest/install/docker-compose.html.

- License pricing: Documented. The self-hosted application uses AGPLv3; commercial support is purchased separately. The current pricing page lists annual support packages rather than the hosted per-agent subscription. Your team remains responsible for updates, backups and availability; support, AI usage and infrastructure have their own terms and costs. Scope: Self-hosted support versus hosted subscription; no transfer of hosted seat prices. Source: https://zammad.com/en/pricing#self-hosted (reviewed 2026-11-20). Supporting source: Published Zammad 7.2.3 AGPL licence — https://github.com/zammad/zammad/blob/7.2.3/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






