LibreDesk

Self-hosted shared inbox and customer support desk.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Application platform deployment; Docker / Compose

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger ↗ · Source checked 2026-11-19

  • Railway: Customer platform workspace · Customer-operated

    Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.

    Railway ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodApplication platform deployment; Docker / Compose
InfrastructureServers / containers
LibreDesk application, PostgreSQL, cache and persistent attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Current upstream agent-login configuration, also described by published v2.9.2 source · Source ↗ · Published v2.9.2 feature and installation reference ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Published upstream release recipe; the quickstart image tags still require an explicit pin · Source ↗ · Deployment artifact ↗ (v2.9.2) · Current installation and encryption-key guide ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

Upstream topology confirmed; numeric production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

LibreDesk; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

LibreDesk upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 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.

Scope & considerations

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

Community & 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.

Category fit

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

Compare within Customer support

  • Chatwoot Self-HostedSelf-hosted customer-support inbox combining live chat, email and messaging conversations.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Combodo iTop (Community)Community IT service-management application with tickets, configuration records and service workflows.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Deskpro Private — Self-HostedCommercial helpdesk installed on customer servers or in customer-controlled private infrastructure.
    • AWS
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core
  • django-helpdeskDjango-based helpdesk for tickets, queues and support communication.
    • Azure
    Customer-operated · Open Source / Open Core
  • Frappe HelpdeskSelf-hosted support desk for tickets, knowledge content and service operations.
    • Azure
    Customer-operated · Open Source / Open Core
  • 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
    Customer-operated · Commercial Only
  • Live Helper ChatSelf-hosted customer live chat and support communications.
    • DigitalOcean
    Customer-operated · Open Source / Open Core

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger ↗ · Hostinger

      Provider guide · 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.

    • Railway ↗ · 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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory