
# Collaboration on Railway

Compare documented Collaboration deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/collaboration/
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: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### 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.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

8 listings.


## Apache Answer

Self-hosted community questions, answers and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-answer/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- 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: Cloudron package; Application platform deployment
- Architecture: Apache Answer application and persistent database/storage.
- 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://answer.apache.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.

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

Apache Answer application and persistent database/storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted community questions, answers and knowledge content.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/apache-answer (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/apache-answer.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/apache-answer
  Apache Answer application and persistent database/storage. The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes LinkinStars, aichy126, kumfo, 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/apache/answer/graphs/contributors

- Upstream project: https://github.com/apache/answer

### Sources

- Cloudron Store: https://www.cloudron.io/store/apache-answer.html

- Railway: https://railway.com/deploy/apache-answer

- Apache-2.0 LICENSE: https://github.com/apache/answer/blob/main/LICENSE

- Releases v2.0.3: https://github.com/apache/answer/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/apache/answer/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/apache-answer.html

- https://railway.com/deploy/apache-answer


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. The official plugin guide demonstrates building Answer with GitHub and Google OAuth connector plugins. Include and configure compatible plugins in the deployed binary/image; this is not a claim that the default image includes enterprise SAML/OIDC. Scope: Official plugin-based application-user OAuth authentication. Source: https://answer.apache.org/docs/plugins (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 installation guide supplies Docker/Compose and binary installation options. Persist the data directory, configure the selected database and include required authentication plugins in the built image; default standalone examples do not supply production HA. Scope: Apache Answer application installation; plugin/custom-image build may be required. Source: https://answer.apache.org/docs/installation (reviewed 2026-11-20). Deployment artifact: https://answer.apache.org/docs/installation. Artifact reference: Current official deployment examples; pin binary/container and plugin versions.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/apache-answer.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Apache Answer; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/apache/answer/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.0.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Apache Answer upstream application; verify compatibility with the selected package. Source: https://github.com/apache/answer/releases/tag/v2.0.3 (reviewed 2026-11-19).







## Docmost Self-Hosted

Self-hosted collaborative wiki and documentation with real-time editing, spaces and page history.

- Listing: https://launchinyourcloud.com/directory/docmost/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; Business and Enterprise features use separate commercial terms.
- Licensing model: open-source
- Installation: Vendor Docker Compose installation with PostgreSQL/Redis, or a community Railway project template.
- Architecture: Persistent web/API and collaborative-editing services with PostgreSQL, Redis and attachment storage
- Operations: Customer manages workspace access, secrets, database and attachment recovery, mail configuration and upgrades. Railway operates the underlying platform within the customer project.
- Product website: https://docmost.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used upstream 0.97.0, which includes security updates. Select a current pinned image; the canonical Railway template uses latest. Do not use the older 0.95.0 template unchanged: upstream fixed a private-space metadata issue in 0.96.0. SSO, audit logs, AI and other paid features require appropriate entitlements. Optional AI, mail and link-preview integrations introduce external connections.

Core code is AGPL-3.0. Enterprise directories and paid Business/Enterprise features are commercially licensed; this entry does not classify those features as open source.

Persistent web/API and collaborative-editing services with PostgreSQL, Redis and attachment storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- collaboration: Provides collaborative wiki pages, spaces, comments, attachments, history and documentation search. Paid governance and integration features have separate edition requirements.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/docmost (checked 2026-11-13). 


### Cloud deployment evidence

- Community Docmost deployment with database, queue and storage (railway): https://railway.com/deploy/docmost
  The canonical community template installs the upstream Docmost image with PostgreSQL, Redis and persistent attachment storage in a customer Railway project. Its image is mutable: select a current pinned release and validate APP_SECRET, database/queue variables, HTTPS and backups against vendor instructions. Paid-feature claims on the template page do not override upstream edition licensing.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Upstream maintains active releases and security advisories with contributions from multiple participants. Release 0.97.0 records maintenance and security updates; contributor history establishes ongoing participation beyond repository stars.

Reviewed 2026-11-13.

- Reviewed 0.97.0 release: https://github.com/docmost/docmost/releases/tag/v0.97.0

- Contributor history: https://github.com/docmost/docmost/graphs/contributors

### Sources

- Vendor installation, persistence and upgrades: https://docmost.com/docs/installation

- Self-managed edition pricing and features: https://docmost.com/pricing

- Metadata access advisory and fixed release: https://github.com/docmost/docmost/security/advisories/GHSA-c34c-w352-hq95

- Community Docmost deployment with database, queue and storage: https://railway.com/deploy/docmost

- Core and enterprise license boundaries: https://github.com/docmost/docmost

- Exact core license: https://github.com/docmost/docmost/blob/main/LICENSE

- Reviewed 0.97.0 release: https://github.com/docmost/docmost/releases/tag/v0.97.0

- Contributor history: https://github.com/docmost/docmost/graphs/contributors

### Licensing sources

- https://github.com/docmost/docmost

- https://github.com/docmost/docmost/blob/main/LICENSE

### Infrastructure sources

- https://docmost.com/docs/installation

- https://railway.com/deploy/docmost


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 documented, 1 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. The vendor self-hosted guide documents SAML, OIDC and LDAP with a paid edition. Identity/group mapping and the applicable license need configuration. Scope: Paid self-hosted Docmost; not Community. Source: https://docmost.com/blog/how-to-set-up-sso-for-a-self-hosted-wiki/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM user/group provisioning and deactivation require Enterprise. SSO must be configured first; SCIM-managed group membership takes precedence over login-time group sync. Scope: Self-hosted Enterprise. Source: https://docmost.com/blog/how-to-set-up-sso-for-a-self-hosted-wiki/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. The project documents that the core self-hosted wiki can run air-gapped without external dependencies. Confirm offline licensing and any separately enabled AI or external integration before applying this to a paid configuration. Scope: Core self-hosted wiki capability; not a claim that every integration works offline. Source: https://docmost.com/docs/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The upstream Compose file defines Docmost, PostgreSQL 18 and Redis 8 with persistent volumes. Replace example secrets and the application URL, enable WebSockets through the proxy, and pin compatible versions instead of relying on latest. Scope: Upstream self-hosting example; not a multi-node HA reference. Source: https://docmost.com/docs/installation (reviewed 2026-11-20). Deployment artifact: https://raw.githubusercontent.com/docmost/docmost/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide and Compose stack establish application, PostgreSQL and Redis dependencies, but publish no CPU/RAM or concurrency minimum in the reviewed instructions. Confirm sizing for users, document/attachment volume and HA before choosing a host. Scope: Self-hosted dependency topology; no quantitative production floor established. Source: https://docmost.com/docs/installation (reviewed 2026-11-20). Supporting source: Upstream Compose dependencies — https://raw.githubusercontent.com/docmost/docmost/main/docker-compose.yml.

- License pricing: Documented. Community is free. Business is listed at $6/seat/month billed annually with a ten-seat minimum; Enterprise has custom pricing. Paid features and self-hosted license activation are separate from running the free core and paying for infrastructure. Scope: Published self-hosted Community, Business and Enterprise plans. Source: https://docmost.com/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v0.97.0, published 2026-10-25. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream docmost/docmost release record; commercial editions and deployment packages may differ. Source: https://github.com/docmost/docmost/releases/tag/v0.97.0 (reviewed 2026-11-14).







## DokuWiki

File-based wiki for documentation and shared knowledge.

- Listing: https://launchinyourcloud.com/directory/dokuwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: DokuWiki web application with persistent wiki pages, configuration and attachments.
- 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://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version.

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

DokuWiki web application with persistent wiki pages, configuration and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: File-based wiki for documentation and shared knowledge.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/dokuwiki (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/dokuwiki.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/dokuwiki
  DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes splitbrain, selfthinker, Klap-in, 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/dokuwiki/dokuwiki/graphs/contributors

- Upstream project: https://github.com/dokuwiki/dokuwiki

### Sources

- Cloudron Store: https://www.cloudron.io/store/dokuwiki.html

- Railway: https://railway.com/deploy/dokuwiki

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg

- GPL-2.0 COPYING: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

- Releases 2026-07-14c: https://github.com/dokuwiki/dokuwiki/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

### Infrastructure sources

- https://www.cloudron.io/store/dokuwiki.html

- https://railway.com/deploy/dokuwiki


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: DokuWiki selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg (reviewed 2026-11-19). Offer prodview-h7wozgfyl3vfg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The maintainer-provided oauth plugin implements login through OAuth services. It is a separately installed authentication plugin, not a guarantee that the default wiki has corporate SAML/OIDC configured; validate provider-plugin and DokuWiki release compatibility. Scope: CosmoCode DokuWiki OAuth plugin integration. Source: https://raw.githubusercontent.com/cosmocode/dokuwiki-plugin-oauth/master/README (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 upstream DokuWiki container repository documents a non-root image, persistent /storage volume and a Compose example. Configure the initial wiki securely, set writable storage ownership and pin a supported release rather than a moving tag. Scope: Official DokuWiki application container packaging; not cloud-account HA IaC. Source: https://raw.githubusercontent.com/dokuwiki/docker/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dokuwiki/docker. Artifact reference: master (moving repository); choose a supported version-tagged image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/dokuwiki.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: DokuWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Etherpad

Self-hosted real-time collaborative text editor.

- Listing: https://launchinyourcloud.com/directory/etherpad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- 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: Cloudron package; Application platform deployment
- Architecture: Etherpad application, database and persistent plugins and settings.
- 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://etherpad.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

Etherpad application, database and persistent plugins and settings. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted real-time collaborative text editor.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/etherpad (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/etherpad.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/etherpad
  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.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/ether/etherpad/graphs/contributors

- Upstream project: https://github.com/ether/etherpad

### Sources

- Cloudron Store: https://www.cloudron.io/store/etherpad.html

- Railway: https://railway.com/deploy/etherpad

- Apache-2.0 LICENSE: https://github.com/ether/etherpad-lite/blob/develop/LICENSE

- Releases v3.3.19: https://github.com/ether/etherpad-lite/releases

- Etherpad | Cloudron Docs: https://docs.cloudron.io/packages/etherpad/

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

- Etherpad authentication and author-token advisories: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh

### Licensing sources

- https://github.com/ether/etherpad-lite/blob/develop/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/etherpad.html

- https://railway.com/deploy/etherpad


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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 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. Scope: Embedded identity issuer and host API integration are distinct from external-IdP federation. Source: https://raw.githubusercontent.com/ether/etherpad/develop/settings.json.template (reviewed 2026-11-20). Supporting source: Official host-user/API integration design — https://docs.etherpad.org/api/http_api.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream Etherpad container deployment and configuration. Source: https://docs.etherpad.org/docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/ether/etherpad/blob/develop/doc/docker.md. Artifact reference: develop (moving branch); pin application and compatible plugins.

- Minimum footprint / sizing: Documented. 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/etherpad.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Etherpad; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ether/etherpad-lite/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Etherpad upstream application; verify compatibility with the selected package. Source: https://github.com/ether/etherpad/releases/tag/v3.3.19 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Etherpad authentication and author-token advisories (security-advisory): 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. Conditions: 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. Source: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh; reviewed 2026-11-19. Supporting source: Author-token isolation advisory — https://github.com/ether/etherpad/security/advisories/GHSA-746x-9w89-7xv6.




## Indico (CERN)

CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- Listing: https://launchinyourcloud.com/directory/indico/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files.
- 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://getindico.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite. Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin.

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

Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- board-committee-governance: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/indico (checked 2026-11-19). 


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/indico
  Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ThiefMaster, pferreir, OmeGak, 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/indico/indico/graphs/contributors

- Upstream project: https://github.com/indico/indico

### Sources

- Railway: https://railway.com/deploy/indico

- Template Repo: https://github.com/aalfath/indico-railway-template

- Dockerfile (`3.3.14`): https://raw.githubusercontent.com/aalfath/indico-railway-template/main/Dockerfile

- MIT: https://raw.githubusercontent.com/indico/indico/master/LICENSE

- Releases (`v3.3.14`): https://github.com/indico/indico/releases

- v3.3.14 Changelog: https://raw.githubusercontent.com/indico/indico/v3.3.14/CHANGES.rst

- Indico offline-copy path traversal: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x

### Licensing sources

- https://raw.githubusercontent.com/indico/indico/master/LICENSE

### Infrastructure sources

- https://railway.com/deploy/indico


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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. Indico uses Flask-Multipass authentication/identity providers, with documented SAML and Shibboleth configurations and extensible providers. Configure the actual provider and identity/group mapping; LDAP directory authentication alone is not labelled federated SSO. Scope: Indico 3.3 stable production authentication; provider-specific configuration required. Source: https://docs.getindico.io/en/stable/config/auth/ (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. Official production guides install Indico, Celery, Redis and PostgreSQL on supported Debian/Ubuntu or Alma/Rocky systems. The nginx guide directs Shibboleth SSO deployments to Apache; configure the chosen web/authentication stack rather than treat all recipes as interchangeable. This is a single-machine installation procedure, not a cloud HA template. Scope: Indico 3.3 stable production installation; Apache is required for the documented Shibboleth integration. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Deployment artifact: https://docs.getindico.io/en/stable/installation/production/deb/nginx/. Artifact reference: Stable 3.3 guide; match supported package versions and web/authentication configuration. Supporting source: Production Apache alternative — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

- Minimum footprint / sizing: Sources checked — unresolved. The full production instructions describe Indico/Celery/Redis/PostgreSQL and worker/reload settings but do not establish a complete CPU/RAM/storage floor or 100-user/1-TB HA capacity. Worker RSS thresholds are not host sizing. Confirm attachment storage, background jobs and concurrency. Scope: Production install and process settings; quantitative workload/HA sizing remains open. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Supporting source: Production Apache installation settings — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Indico offline-copy path traversal (security-advisory): The upstream advisory identifies local file disclosure in offline-copy generation. Scope: Indico <3.3.14; fixed in 3.3.14 (GHSA-h57f-c9j4-577x / CVE-2026-107398). Conditions: Exposure depends on the ability to generate the affected offline copy; verify the exact upstream advisory. Action: Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin. Source: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x; reviewed 2026-11-19.




## Nextcloud Server

Self-hosted file synchronization and sharing server for team document collaboration.

- Listing: https://launchinyourcloud.com/directory/nextcloud-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Server core; review selected applications separately
- Licensing model: open-source
- Installation: Official Nextcloud AIO or documented Linux/PHP server installation
- Architecture: Persistent web application, SQL database and file storage; the documented manual installation uses a Linux, Apache, MariaDB and PHP stack.
- Operations: Customer operates the server, storage, backups and upgrades; select a supported release and deployment method.
- Product website: https://nextcloud.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted Server and file-sharing capabilities. The installation manual distinguishes official AIO from community Snap, VM and Docker options, which Nextcloud GmbH does not officially support. Review separately selected applications, integrations and enterprise support terms.

This classification covers Nextcloud Server, whose repository provides the GNU Affero GPL version 3. It does not classify every separately installed application or commercial service.

The official manual documents a persistent Linux web/database installation and an official AIO deployment.


### Category fit

- document-management: File synchronization, sharing and collaborative file workspaces; this entry does not establish regulated records-management capabilities.

- collaboration: Shared file workspaces for teams, with additional collaboration applications available in the Nextcloud ecosystem.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/nextcloud (checked 2026-11-12). 


### Cloud deployment evidence

- Nextcloud Server community deployment on Railway (railway): https://railway.com/deploy/nextcloud
  The community template deploys the official Nextcloud container with PostgreSQL, a persistent application volume and bucket storage in a customer Railway project. Review the selected release, trusted domains/proxies, background jobs, object-storage configuration and backups. Optional Office, Talk and third-party apps can require additional services; they are not implied by this server deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official case studies describe self-hosted or on-premise deployments at Milieudefensie, CSIC and Sorbonne University. The official changelog records the 35.0.3 maintenance release on November 12, 2026. These are product adoption and maintenance signals, not a claim that each adopter uses the same edition or installation method.

Reviewed 2026-11-13.

- Organizational deployments and customer stories: https://nextcloud.com/customers/

- Server maintenance releases: https://nextcloud.com/changelog/

### Sources

- Linux installation and deployment options: https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html

- Nextcloud Files capabilities: https://nextcloud.com/files/

- Nextcloud Server license: https://raw.githubusercontent.com/nextcloud/server/master/COPYING

- Nextcloud maintenance changelog: https://nextcloud.com/changelog/

- Official customer implementation stories: https://nextcloud.com/customers/

### Licensing sources

- https://raw.githubusercontent.com/nextcloud/server/master/COPYING

### Infrastructure sources

- https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. The Nextcloud-maintained SSO/SAML app supports SAML 2.0 and environment-based authentication. Enable a compatible app release and configure the provider; the repository distinguishes tested providers from theoretical protocol compatibility. Scope: Nextcloud SSO/SAML application; server/app compatibility must be checked. Source: https://github.com/nextcloud/user_saml (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. Nextcloud AIO publishes a multi-container application bundle. Review its host/volume/port requirements and enabled optional services; the bundle has a different footprint from a minimal PHP server installation. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nextcloud/all-in-one (reviewed 2026-11-14). Deployment artifact: https://github.com/nextcloud/all-in-one. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The versioned manual lists 128 MB minimum and 512 MB recommended RAM per PHP process. This is not a total host/AIO minimum: database, concurrent processes, apps, previews and storage need additional resources. Scope: Nextcloud 33 per-process memory, not whole-server sizing. Source: https://docs.nextcloud.com/server/33/admin_manual/installation/system_requirements.html (reviewed 2026-11-14).

- License pricing: Documented. The Server core is AGPL-3.0. This does not price Enterprise support, optional applications, hosting or operating labour; review those separately for the selected deployment. Scope: Nextcloud Server core; applications and commercial subscriptions excluded. Source: https://raw.githubusercontent.com/nextcloud/server/master/COPYING (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v33.0.11, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream nextcloud/server release record; commercial editions and deployment packages may differ. Source: https://github.com/nextcloud/server/releases/tag/v33.0.11 (reviewed 2026-11-14).







## Penpot

Self-hosted collaborative interface design and prototyping platform.

- Listing: https://launchinyourcloud.com/directory/penpot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Penpot frontend, backend, exporter, PostgreSQL, cache and object storage.
- 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://penpot.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.

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

Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted collaborative interface design and prototyping platform.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/penpot (checked 2026-11-19). 


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/penpot
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes niwinz, Alotor, superalex, 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/penpot/penpot/graphs/contributors

- Upstream project: https://github.com/penpot/penpot

### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

- Railway: https://railway.com/deploy/penpot

- MPL-2.0 LICENSE: https://github.com/penpot/penpot/blob/develop/LICENSE

- Releases v2.19.3: https://github.com/penpot/penpot/releases

### Licensing sources

- https://github.com/penpot/penpot/blob/develop/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

- https://railway.com/deploy/penpot


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. The self-hosted configuration guide documents generic OIDC and named OAuth providers. Configure the backend credentials, enabled-login flags and callback URL; LDAP and the application admin surface are separate considerations. Scope: Penpot self-hosted application-user identity configuration. Source: https://help.penpot.app/technical-guide/configuration/ (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 self-hosting guide supplies a Compose file with frontend, backend, exporter, PostgreSQL and persistent assets. Replace the example master secret/database credentials and pin compatible images. A single PostgreSQL container is not database HA. Scope: Upstream Penpot Compose deployment; verify compatibility with the selected provider package. Source: https://help.penpot.app/technical-guide/getting-started/docker/ (reviewed 2026-11-20). Deployment artifact: https://raw.githubusercontent.com/penpot/penpot/develop/docker/images/docker-compose.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The upstream settings guide describes 4 CPUs/16 GB RAM as a reference and recommends an elastic 50–100 GB database starting point for up to ten editors, with growth driven by files and usage. These are vendor guidelines, not a validated 100-user/1-TB HA configuration; add database/asset backups and replicas separately. Scope: Upstream reference settings and elastic database guidance; not a guaranteed capacity benchmark. Source: https://help.penpot.app/technical-guide/getting-started/recommended-settings/ (reviewed 2026-11-20).

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Penpot; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/penpot/penpot/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Rallly

Self-hosted group scheduling polls and meeting coordination.

- Listing: https://launchinyourcloud.com/directory/rallly/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Rallly application, PostgreSQL, persistent storage and outbound email.
- 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://rallly.co
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.

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

Rallly application, PostgreSQL, persistent storage and outbound email. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group scheduling polls and meeting coordination.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/rallly (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/rallly.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/rallly
  Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lukevella, snyk-bot, jonas-hoebenreich, 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/lukevella/rallly/graphs/contributors

- Upstream project: https://github.com/lukevella/rallly

### Sources

- Cloudron Store: https://www.cloudron.io/store/rallly.html

- Railway: https://railway.com/deploy/rallly

- AGPL-3.0 LICENSE: https://github.com/lukevella/rallly/blob/main/LICENSE

- Releases v4.17.1: https://github.com/lukevella/rallly/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/lukevella/rallly/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/rallly.html

- https://railway.com/deploy/rallly


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. The self-hosting guide documents Google, Microsoft Entra ID and generic OIDC login from v3.4 onward. Configure callback URLs, verified email claims and linking policy; multi-user licence entitlements are a separate consideration. Scope: Rallly self-hosted user identity; review the selected v4 deployment and license. Source: https://support.rallly.co/self-hosting/single-sign-on (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 installer provisions a Compose stack, generates secrets and supports external database, object storage and reverse-proxy settings. Review the downloaded script before execution, pin compatible images and plan backups; this is not a production HA template. Scope: Current official self-hosting stack and installer. Source: https://support.rallly.co/self-hosting/installation/docker (reviewed 2026-11-20). Deployment artifact: https://get.rallly.co. Artifact reference: Moving official installer; inspect and pin the selected application/stack release.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/rallly.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The current self-hosting guide states free personal use and asks multi-user installations to purchase a licence key. It lists Plus at $49, Organization at $499 and Enterprise from $999; keys cover Rallly v4.x with tier/user/space limits. Activation requires the licensing service. These runtime-plan terms add detail beyond the repository’s AGPL notice. Scope: Published Rallly v4 self-hosting licence-key tiers; confirm applicable user/space allocation and quote. Source: https://support.rallly.co/self-hosting/licensing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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






