Zammad
Self-hosted helpdesk and ticketing application for customer service and internal support teams.
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Linux packages; Docker Compose and Kubernetes alternatives are documented
Runs in
Documented customer environment
Persistent application and worker services with PostgreSQL, Redis and a web proxy; Elasticsearch is strongly recommended for search.
- Railway: Customer platform workspace
- Railway
Servers / containers
Operated by
Your team
Customer runs the application stack, database, backups and security updates; follow supported distribution and release requirements.
Deployment boundaries by provider
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Zammad community deployment on Railway ↗ · Source checked 2026-11-12
Source for the Zammad Railway application wrapper ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Linux packages; Docker Compose and Kubernetes alternatives are documented |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core 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. |
| License | AGPL-3.0 repository license for the core application |
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 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.
Self-hosted Zammad application login, with administrator configuration · Source ↗ · SAML configuration ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Official self-hosted Compose deployment; infrastructure support is separate · Source ↗ · Deployment artifact ↗ (master (moving branch; select matching release/scenario)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Current self-hosted hardware guidance; selected topology and ticket load govern sizing · Source ↗ · Docker-specific prerequisites ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Self-hosted support versus hosted subscription; no transfer of hosted seat prices · Source ↗ · Published Zammad 7.2.3 AGPL licence ↗ · Reviewed 2026-11-20
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
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.
Community & 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.
Category fit
- Customer support
- Agent helpdesk with tickets, customer communication, configurable fields and a knowledge base.
Compare within Customer support
- Chatwoot Self-HostedSelf-hosted customer-support inbox combining live chat, email and messaging conversations.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Combodo iTop (Community)Community IT service-management application with tickets, configuration records and service workflows.
- Hostinger
- Deskpro Private — Self-HostedCommercial helpdesk installed on customer servers or in customer-controlled private infrastructure.
- AWS
- DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
- AWS
- Google Cloud
- DigitalOcean
- Hetzner
- Linode
- Vultr
- django-helpdeskDjango-based helpdesk for tickets, queues and support communication.
- Azure
- Frappe HelpdeskSelf-hosted support desk for tickets, knowledge content and service operations.
- Azure
- 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
- LibreDeskSelf-hosted shared inbox and customer support desk.
- Railway
- Hostinger
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official Linux package installation ↗docs.zammad.org
- Server, database and deployment prerequisites ↗docs.zammad.org
- Helpdesk and customer support features ↗zammad.com
- Zammad core repository license ↗raw.githubusercontent.com
- Vendor open-source policy ↗zammad.com
- Supported and emergency security releases ↗zammad.com
- November 2026 critical security release ↗zammad.com
- Customer support implementation stories ↗zammad.com
- Nextcloud customer support case study ↗zammad.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Zammad community deployment on Railway ↗ · Railway
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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 for the Zammad Railway application wrapper ↗ · Railway
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Zammad community deployment on Railway ↗ · Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Named customer-support adopters ↗zammad.com
- Nextcloud implementation story ↗zammad.com
- Recent feature and security maintenance ↗zammad.com
- 7.2.3 critical security release ↗zammad.com