Live Helper Chat
Self-hosted customer live chat and support communications.
3 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
VM image; Package / binary installer
Runs in
Documented customer environment
PHP application and database on a customer DigitalOcean Droplet.
- DigitalOcean: Customer cloud account
- DigitalOcean
Servers / containers
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
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
LHC DigitalOcean Docs ↗ · 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 method | VM image; Package / binary installer |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Apache License 2.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%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
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.
Custom auto-login mechanism confirmed; enterprise identity federation remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream PHP installation; distinct from the DigitalOcean packaged image · Source ↗ · Deployment artifact ↗ (5.01v) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Supported software topology; current workload-sized CPU/RAM/storage remains unconfirmed · Source ↗ · DigitalOcean package and optional service overhead ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Live Helper Chat; 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 5.01v release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Live Helper Chat 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
Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.
Community & 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.
Category fit
- Customer support
- Self-hosted customer live chat and support communications.
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
- LHC DigitalOcean Docs ↗doc.livehelperchat.com
- GitHub LICENSE (Apache-2.0) ↗raw.githubusercontent.com
- GitHub Releases ↗github.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.
- LHC DigitalOcean Docs ↗ · DigitalOcean
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- LHC DigitalOcean Docs ↗ · DigitalOcean
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com