Etherpad
Self-hosted real-time collaborative text editor.
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
7 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 →
Etherpad authentication and author-token advisories
Upstream documents an OIDC login bypass and an author-token isolation correction in separate advisories.
Scope: GHSA-62cj-9j72-mfrh and GHSA-746x-9w89-7xv6; consult each notice for its own affected and fixed versions.
OIDC/password configuration and clients without author tokens change exposure; plugin/package versions must be checked separately.
Action: Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.
Primary source · Author-token isolation advisory · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Cloudron package; Application platform deployment
Runs in
Documented customer environment
Etherpad application, database and persistent plugins and settings.
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- Linode: Customer cloud account
- Vultr: Customer cloud account
- Hostinger: Customer VPS account
- LumaDock: Customer VPS account
- Railway: Customer platform workspace
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
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
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- 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.
Cloudron Store ↗ · Source checked 2026-11-19
- LumaDock: 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.
Cloudron Store ↗ · 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 method | Cloudron package; Application platform deployment |
|---|---|
| Infrastructure | Servers / containers Etherpad application, database and persistent plugins and settings. 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%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed configuration includes an embedded OIDC issuer with admin/user clients, and the API supports mapping a host application’s users and permissions. This does not establish login federation to an existing corporate SAML/OIDC IdP for the selected pad/admin deployment. Confirm the supported external-auth plugin or portal integration.
Embedded identity issuer and host API integration are distinct from external-IdP federation · Source ↗ · Official host-user/API integration design ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official Docker documentation provides container/environment configuration and persistent data/plugin handling. Pin compatible application/plugins, supply a production database and secrets, and configure the reverse proxy. A standalone container does not by itself supply durable clustered operation or external-user SSO.
Upstream Etherpad container deployment and configuration · Source ↗ · Deployment artifact ↗ (develop (moving branch); pin application and compatible plugins) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Cloudron package declares 768MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing.
Selected Cloudron application package; add database, files, backups and concurrent workload requirements · Source ↗ · Cloudron platform requirements ↗ · Reviewed 2026-11-19
Documented · 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.
Etherpad; 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 v3.3.19 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Etherpad 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
Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.
Community & maintenance
The reviewed upstream contributor history includes JohnMcLear, rhansen, Pita, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Collaboration
- Self-hosted real-time collaborative text editor.
Compare within Collaboration
- 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache AnswerSelf-hosted community questions, answers and knowledge content.
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
- BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Hetzner
- Scaleway
- BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
- Campfire (ONCE)Self-hosted group chat and team conversation application.
- DigitalOcean
- Collabora Online (CODE)Community office editing server for integration with a document platform.
- AWS
- DigitalOcean
- Hetzner
- Linode
- Vultr
- Hostinger
- LumaDock
- Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- AWS
- Azure
- Google Cloud
- DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
- AWS
- Google Cloud
- DigitalOcean
- Hetzner
- Linode
- Vultr
Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →
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
- Cloudron Store ↗www.cloudron.io
- Railway ↗railway.com
- Apache-2.0 LICENSE ↗github.com
- Releases v3.3.19 ↗github.com
- Etherpad | Cloudron Docs ↗docs.cloudron.io
- Cloudron customer-server and named-provider installation ↗docs.cloudron.io
- Etherpad authentication and author-token advisories ↗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.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
- Railway ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. This source is distinct from the Cloudron package.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com