
# Customer support on DigitalOcean

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

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/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: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

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

3 listings.


## Chatwoot Self-Hosted

Self-hosted customer-support inbox combining live chat, email and messaging conversations.

- Listing: https://launchinyourcloud.com/directory/chatwoot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; proprietary enterprise features and paid self-hosted plans
- Licensing model: open-source
- Installation: Production Docker Compose, Linux VM or Kubernetes deployment
- Architecture: Customer-operated application and workers with PostgreSQL, Redis and upload storage
- Operations: Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.
- Product website: https://www.chatwoot.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Community Edition excludes paid features such as SSO/SAML, SLA policies and Captain AI. Captain integrations may send data to external model providers. Official Azure and Google Cloud deployment guides are marked work in progress; validate their instructions against current requirements before production.

The self-hosted offering combines an MIT Community Edition with proprietary Enterprise feature code. Paid feature entitlements are distinct from community source-code rights; premium support alone is not the basis for this classification.

The production Docker guide runs Rails application/worker services alongside PostgreSQL and Redis, or connects to separately managed equivalents. Official cloud guides use VMs and also identify Kubernetes paths.


Cloud evidence scope: Official Azure VM and Google Compute Engine guides exist and are marked work in progress; other cloud badges are not inferred.

### Category fit

- customer-support: Shared support inbox, live chat, email and messaging channels, with automation and reporting; feature entitlements depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/gcp (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/aws (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Chatwoot self-hosted deployment on AWS (aws): https://developers.chatwoot.com/self-hosted/deployment/aws
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Azure (azure): https://developers.chatwoot.com/self-hosted/deployment/azure
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Google Cloud (gcp): https://developers.chatwoot.com/self-hosted/deployment/gcp
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on digitalocean (digitalocean): https://developers.chatwoot.com/self-hosted/deployment/digitalocean
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Community support functionality: https://www.chatwoot.com/community

- Production Docker installation: https://developers.chatwoot.com/self-hosted/deployment/docker

- Edition licensing: https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- Self-hosted plan features: https://www.chatwoot.com/pricing/self-hosted-plans

- Azure deployment: https://developers.chatwoot.com/self-hosted/deployment/azure

- Google Cloud deployment: https://developers.chatwoot.com/self-hosted/deployment/gcp

- Chatwoot self-hosted deployment on aws: https://developers.chatwoot.com/self-hosted/deployment/aws

- Chatwoot self-hosted deployment on digitalocean: https://developers.chatwoot.com/self-hosted/deployment/digitalocean

### Licensing sources

- https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- https://www.chatwoot.com/pricing/self-hosted-plans

### Infrastructure sources

- https://developers.chatwoot.com/self-hosted/deployment/docker


### 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: Edition-dependent. SAML SSO is included in Enterprise, but not Community or Premium Support. Scope: Self-hosted plan comparison. Source: https://www.chatwoot.com/pricing/self-hosted-plans (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production guide links an upstream Compose stack with Rails, Sidekiq, PostgreSQL and Redis. Its application image uses latest; pin a compatible release, set secrets, and configure TLS, storage and backups. Scope: Production Docker deployment. Source: https://developers.chatwoot.com/self-hosted/deployment/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/chatwoot/chatwoot/blob/develop/docker-compose.production.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The technical requirements page specifies 4 CPU cores and 4 GB RAM for its smallest example workload; the pricing FAQ separately says 2 CPU cores and 4 GB. Resolve this difference for your workload before sizing. Scope: Technical requirements; compare the pricing FAQ. Source: https://developers.chatwoot.com/self-hosted/deployment/requirements (reviewed 2026-11-14). Supporting source: Self-hosted pricing FAQ: production starting point — https://www.chatwoot.com/pricing/self-hosted-plans.

- License pricing: Documented. Community is free to self-host. The current page lists Premium Support at $19 and Enterprise at $99 per agent/month; SAML is Enterprise-only. These are software/support plan units, excluding your infrastructure, taxes and connected AI usage. Confirm currency and billing terms at checkout. Scope: Current self-hosted edition comparison; not a hosted subscription or a total operating-cost estimate. Source: https://www.chatwoot.com/pricing/self-hosted-plans (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- zendesk: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.

- intercom: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.





## Discourse

Self-hosted discussion and community platform for workplace collaboration and customer support communities.

- Listing: https://launchinyourcloud.com/directory/discourse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, linode, vultr, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-2.0 core; review extensions separately
- Licensing model: open-source
- Installation: Official Docker installer on a Linux cloud or local server
- Architecture: Persistent Docker server; the standalone template includes web, PostgreSQL and Redis services with host-mounted data volumes.
- Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
- Product website: https://www.discourse.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.

The listed self-hosted core has a GNU GPL version 2 license. Official paid hosting is a separate service; review the licenses of selected extensions separately.

The official installer requires a Linux server and Docker. Its standalone configuration mounts persistent host storage and includes PostgreSQL and Redis; this is a server workload.


### Category fit

- collaboration: Public or private discussion communities with searchable topics, chat and shared knowledge.

- customer-support: Customer and peer-support communities; this is a discussion platform rather than an agent-ticket helpdesk.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 


### Cloud deployment evidence

- Discourse supported cloud server installation (aws, gcp, digitalocean, linode, vultr, hetzner): https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md
  The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official customer directory identifies Docker, Elastic and GitLab support communities as Discourse users, without establishing their hosting model. The official release service records security-maintenance updates on November 10, 2026 for the latest, monthly and ESR channels; the supported 2026.10.1 release includes 38 security fixes.

Reviewed 2026-11-14.

- Named support-community adopters: https://www.discourse.org/customers

- Current releases and support timelines: https://releases.discourse.org/

- 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Sources

- Official self-hosting installation guide: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- Official standalone Docker service and storage template: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml

- Discussion, chat and administration features: https://www.discourse.org/features

- Discourse core license: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- Official releases and support timelines: https://releases.discourse.org/

- Official customer community directory: https://www.discourse.org/customers

- Discourse 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Licensing sources

- https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

### Infrastructure sources

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml


### 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. DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service. Scope: Official DiscourseConnect self-hosted forum authentication. Source: https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology. Scope: Official self-hosted launcher and standalone container installation. Source: https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml. Artifact reference: main (moving branch). Supporting source: Standalone configuration template — https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml.

- Minimum footprint / sizing: Documented. The upstream cloud guide lists 1 CPU core, 1 GB RAM with swap and 10 GB disk as minima; 2+ cores, 2 GB+ RAM and 20 GB+ disk are recommended. Plugins, traffic and data growth change sizing. Scope: Upstream standalone cloud install baseline. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (reviewed 2026-11-14).

- License pricing: Documented. The upstream Discourse software is GPL version 2. Hosted subscription prices on discourse.org are for separately operated hosting/services and should not be presented as the license cost of the self-hosted core. Infrastructure, implementation and optional services are separate. Scope: Upstream self-hosted core license; hosted plan pricing is a different offering. Source: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Live Helper Chat

Self-hosted customer live chat and support communications.

- Listing: https://launchinyourcloud.com/directory/livehelperchat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Package / binary installer
- Architecture: PHP application and database on a customer DigitalOcean Droplet.
- 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://doc.livehelperchat.com/docs/development/hosting-on-digitalocean
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

PHP application and database on a customer DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted customer live chat and support communications.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean (checked 2026-11-19). 


### Cloud deployment evidence

- LHC DigitalOcean Docs (digitalocean): https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean
  PHP application and database on a customer DigitalOcean Droplet. Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes remdex, doncaz, mysubcult, 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/LiveHelperChat/livehelperchat/graphs/contributors

- Upstream project: https://github.com/LiveHelperChat/livehelperchat

### Sources

- LHC DigitalOcean Docs: https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/LiveHelperChat/livehelperchat/master/LICENSE

- GitHub Releases: https://github.com/LiveHelperChat/livehelperchat/releases

### Licensing sources

- https://raw.githubusercontent.com/LiveHelperChat/livehelperchat/master/LICENSE

### Infrastructure sources

- https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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 guide documents custom signed auto-login links for existing operator IDs/usernames using a shared secret and optional expiry. Mailbox OAuth and these links do not by themselves establish a supported SAML/OIDC identity-provider integration, account lifecycle or role mapping. Confirm the intended external authentication design. Scope: Custom auto-login mechanism confirmed; enterprise identity federation remains unconfirmed. Source: https://doc.livehelperchat.com/docs/users/auto-login (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide installs an upstream release archive, optionally with dependencies bundled, on a PHP/web-server/database host. Configure database credentials, writable directories, initial admin access and the chat widget; Docker is a separate linked option. Use a version-matched package rather than an unpinned archive. Scope: Upstream PHP installation; distinct from the DigitalOcean packaged image. Source: https://doc.livehelperchat.com/docs/install (reviewed 2026-11-20). Deployment artifact: https://github.com/LiveHelperChat/livehelperchat/releases/tag/5.01v. Artifact reference: 5.01v.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide specifies PHP, web-server and database dependencies. Its DigitalOcean guide says the smallest droplet can run the package but does not identify a current numeric whole-stack production capacity. Confirm operator/chat concurrency, mail workers, optional co-browsing, retention and HA; do not reuse the guide's small-droplet price as a current cost quote. Scope: Supported software topology; current workload-sized CPU/RAM/storage remains unconfirmed. Source: https://doc.livehelperchat.com/docs/install (reviewed 2026-11-20). Supporting source: DigitalOcean package and optional service overhead — https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Live Helper Chat; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/LiveHelperChat/livehelperchat/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 5.01v release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Live Helper Chat upstream application; verify compatibility with the selected package. Source: https://github.com/LiveHelperChat/livehelperchat/releases/tag/5.01v (reviewed 2026-11-19).






