
# Customer support on Railway

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

Canonical page: https://launchinyourcloud.com/clouds/railway/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: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

3 listings.


## 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).







## UVdesk Community

Community service desk for support tickets and customer communications.

- Listing: https://launchinyourcloud.com/directory/uvdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: UVdesk application, MySQL, files and mail services in Railway.
- 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://www.uvdesk.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.

Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

UVdesk application, MySQL, files and mail services in Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Community service desk for support tickets and customer communications.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/uvdesk-helpdesk
  UVdesk application, MySQL, files and mail services in Railway. The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes papnoisanjeev, komal-sh-27, PeopleInside, 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/uvdesk/community-skeleton/graphs/contributors

- Upstream project: https://github.com/uvdesk/community-skeleton

### Sources

- Railway: https://railway.com/deploy/uvdesk-helpdesk

- GitHub LICENSE.txt (OSL-3.0): https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt

- GitHub Releases: https://github.com/uvdesk/community-skeleton/releases

### Licensing sources

- https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt

### Infrastructure sources

- https://railway.com/deploy/uvdesk-helpdesk


### 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: Sources checked — unresolved. The vendor advertises social-login/SSO apps for its SaaS support portal, while the reviewed Community v1.1.8 security configuration uses application form login. These sources do not confirm a version-compatible external identity-provider integration for Community agents or customers. A Symfony authentication extension would need an actual supported configuration. Scope: Community Edition versus SaaS app boundary; no positive SSO availability established. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/config/packages/security.yaml (reviewed 2026-11-20). Supporting source: Vendor social-login app, labelled SaaS — https://www.uvdesk.com/en/apps/social-login-app/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published Community v1.1.8 README documents Composer project creation or downloading the release, followed by helpdesk configuration; Docker and persistent-container guides are linked separately. Pin the selected version, install dependencies, configure database/mail and protect the application. A provider template may package a different release. Scope: Published Community release installation instructions. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/uvdesk/community-skeleton/releases/tag/v1.1.8. Artifact reference: v1.1.8.

- Minimum footprint / sizing: Documented. The v1.1.8 README lists at least 4 GB RAM and a 1 GHz processor with a PHP/web-server/MySQL stack. This is an upstream starting point, not ticket/attachment retention capacity or an HA topology. Review the version-matched supported OS/runtime rather than copying the README's old OS examples unchanged. Scope: Published upstream Community baseline; whole-stack HA and 1 TB data capacity require further sizing. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/README.md (reviewed 2026-11-20).

- License pricing: Documented. Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: UVdesk Community; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







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






