Customer support on Railway

Support inboxes, ticketing and customer service operations.

3 documented options on Railway. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
LibreDeskHostinger, RailwayCustomer-operated
Servers / containers
Open Source / Open Core

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

Application platform deployment; Docker / ComposeCustomer 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.
Scope and evidence

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

  • Hostinger — 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.

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

  • Railway — 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.

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

Cloud evidence reviewed 2026-11-19

UVdesk CommunityRailwayCustomer-operated
Servers / containers
Open Source / Open Core

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

Application platform deploymentCustomer 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.
Scope and evidence

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

  • Railway — 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.

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

Cloud evidence reviewed 2026-11-19

ZammadRailwayCustomer-operated
Servers / containers
Open Source / Open Core

AGPL-3.0 repository license for the core application

Official Linux packages; Docker Compose and Kubernetes alternatives are documentedCustomer runs the application stack, database, backups and security updates; follow supported distribution and release requirements.
Scope and evidence

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.

  • Zammad community deployment on Railway — 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.

    Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Source for the Zammad Railway application wrapper — 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.

    Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Deployment evidence and category fit

LibreDesk

Self-hosted shared inbox and customer support desk.

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

  • Railway ↗

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

    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.

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

UVdesk Community

Community service desk for support tickets and customer communications.

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

  • Railway ↗

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

    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.

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

Zammad

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

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.

  • Zammad community deployment on 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 ↗

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Deployment and procurement checks

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. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

Account boundary: Railway workspace, project and environment; platform-managed infrastructure. Access: Workspace/project access and scoped deployment tokens. Network: Project/environment private networking with separately exposed public services.

Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings