Software on LumaDock
Software with a documented deployment path in a customer environment on LumaDock.
18 listings, including 18 from other publishers. Search and filter LumaDock listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- LumaDock account and VPS
- Network
- Customer server networking, DNS and firewall rules
- Identity & access
- Cloud account access, server root/SSH access and application administrators
- Deployment tooling
- Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-13. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- VPS firewall controls
- LumaDock documents that a new VPS firewall has no blocking rules by default. Review an allow-and-block policy while preserving console recovery and administrative access; installing Cloudron does not itself establish those network controls. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Browse by category
7 categories on LumaDock. Counts show matching listings; a listing can appear in more than one category.
Business operations1 category
Governance & industries1 category
Content & collaboration4 categories
Developer platforms & operations1 category
No categories match your search.
Documented software
Deployment evidence and qualifications
Self-hosted community questions, answers and knowledge content.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted wiki and documentation organized into books, chapters and pages.
- LumaDock customer VPS Cloudron template ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Operations: Customer manages administrators, registration roles, identity, content permissions, mail, database and file backups, recovery and upgrades. Cloudron manages package services on the customer server.
Scope: Reviewed Cloudron 2.3.1 contains upstream 26.09.3 and its access-control fixes. Change the initial local administrator credentials. With Cloudron SSO, change the default registration role before admitting users: the package initially grants administrator status. Back up the database, configuration, uploads, storage and custom themes. Only the latest upstream release is supported. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.
License: MIT application; third-party components retain their licenses.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- LumaDock customer VPS Cloudron template ↗
Deployment evidence and qualifications
Community office editing server for integration with a document platform.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package.
License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- LumaDock customer VPS Cloudron template ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Operations: Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
Scope: Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.
License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- LumaDock customer VPS Cloudron template ↗
Deployment evidence and qualifications
File-based wiki for documentation and shared knowledge.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: 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.
License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted real-time collaborative text editor.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: 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.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted flat-file content management system.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: No relational database is required by the base system; plugins and themes can introduce their own dependencies and licences. Cloudron package and upstream versions can differ.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Personal-use self-hosted synchronization server for Joplin notes.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: The Server Personal Use License permits personal non-commercial use and restricts use by business entities and commercial sharing without written permission. This is not a default option for a 100-user business deployment. Desktop/client licences and releases do not establish server rights or Server 3.7.6 publication dates.
License: Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted photo gallery, albums and image sharing.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Public, protected and private album modes must be configured deliberately; hosting the server does not make every gallery private.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted lightweight notes, documents and knowledge timeline.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Digital collections publishing for libraries, archives, museums and research institutions.
- LumaDock customer VPS Cloudron template ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Operations: Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.
Scope: Reviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.
License: GPLv3 application; the packaged OIDC module is GPL-3.0-or-later.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- LumaDock customer VPS Cloudron template ↗
Deployment evidence and qualifications
Community browser-based office document editing and co-authoring server.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. The supplied Vultr article installs DocSpace rather than Docs; the Vultr badge here comes from the reviewed Cloudron Docs package instead.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted video publishing and federated media platform.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: PeerTube 8.3.2 includes a sharp/libvips security update. Federation and optional peer-to-peer playback share metadata or traffic outside the host; review those settings for confidential media. Update PeerTube and its bundled image-processing dependencies through the compatible 8.3.2-or-later upgrade process.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted photo management, albums and media gallery.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Plugins, storage and published album permissions require separate review; package versions and upstream releases can differ.
License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted group scheduling polls and meeting coordination.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Open-source agile project, issue and team planning application.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.
License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted hierarchical personal notes and document knowledge base.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: The server is primarily a single-user knowledge base; published notes and sharing do not establish a multi-user enterprise collaboration suite.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Deployment evidence and qualifications
Self-hosted multi-user collaborative whiteboard.
- Cloudron Store ↗
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.
Application boundary: Customer VPS account. An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
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.
Scope: Review board visibility and authentication before exposing it. A private VPS does not automatically make every board private or give the app enterprise SSO.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloudron Store ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings