Software on DigitalOcean
Software with a documented deployment path in a customer environment on DigitalOcean.
69 listings, including 69 from other publishers. Search and filter DigitalOcean 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
- DigitalOcean team/account and project
- Network
- VPC and Cloud Firewalls; review public endpoints
- Identity & access
- Team roles, scoped API tokens and SSH keys
- Deployment tooling
- Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- Private networking
- DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls. 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
31 categories on DigitalOcean. Counts show matching listings; a listing can appear in more than one category.
Business operations7 categories
Governance & industries4 categories
Content & collaboration5 categories
Data & analytics4 categories
Developer platforms & operations8 categories
AI tools & infrastructure3 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
Commercial business communications and PBX platform installed into the customer's public-cloud account.
- 3CX in the customer's DigitalOcean account ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.
Scope: This entry excludes the Hosted by 3CX service. External SIP trunks, carriers, calling charges and endpoint hardware remain separate. Review provider sizing and media-network requirements before deployment. The AWS AMI is vendor-published package 20.0.10.1785 on Debian 12, with its 3CX licence billed outside AWS Marketplace. 3CX's November 2026 security-hotfix log updates V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest update through the Admin Console, restart as directed and verify the deployed package set; do not treat the application build number alone as proof that OS hotfixes are current.
License: Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- 3CX in the customer's DigitalOcean account ↗
Deployment evidence and qualifications
Self-managed data movement and ELT platform with customer-operated connectors and job execution.
- Airbyte-published v0.30.25 DigitalOcean Droplet image ↗
Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
DigitalOcean lists an Airbyte-published 1-Click Droplet image, version 0.30.25 on Ubuntu 20.04, and provides creation instructions for the customer account. This is legacy, version-specific application deployment evidence, not verification of the current Helm-based release or current vendor support. Confirm image availability, compatibility, upgrade paths and support before selecting this route.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.
Scope: This entry covers Airbyte Self-Managed, not Airbyte Cloud or the hybrid offering. Connector jobs communicate with configured external sources and destinations. Elastic License 2.0 permits internal self-hosting but restricts offering the software as a managed service and bypassing license-key functionality. DigitalOcean lists a separate legacy v0.30.25 Marketplace image on Ubuntu 20.04. That evidence does not establish current Helm-release compatibility or current vendor support; verify image availability, upgrade paths and support for the selected release.
License: Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Airbyte-published v0.30.25 DigitalOcean Droplet image ↗
Deployment evidence and qualifications
Workflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.
- Apache Airflow full application on DigitalOcean ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The provider catalog provisions Airflow on a customer Ubuntu 24.04 Droplet, with the application UI, local PostgreSQL and Redis, or customer-managed database services and Celery workers. This is full application hosting, not a database connector. The catalog does not identify the exact Airflow package release; verify the selected image, compatible dependencies, TLS, access controls, backups and upgrades.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.
Scope: The Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.
License: Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Apache Airflow full application on DigitalOcean ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
- Appsmith on a customer DigitalOcean Droplet ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.
Scope: Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.
License: Apache-2.0 Community core; commercial edition and plan-dependent features
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Appsmith on a customer DigitalOcean Droplet ↗
Deployment evidence and qualifications
Self-hosted backend services for authentication, databases, storage, functions and messaging.
- Appwrite self-hosting on digitalocean ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer configures the environment and handles software updates, scaling, security and backups.
Scope: This entry covers self-hosting rather than Appwrite Cloud. Official deployment guides document EC2/EKS, Azure VMs/AKS and Google Compute Engine/GKE. Configure external email, SMS and other integrations deliberately; enterprise support and compliance offerings have separate terms. Appwrite 2.7.3 includes the 2.7.2 security fixes across authentication, abuse limits, storage, realtime, messaging, functions, VCS, proxy handling, and vulnerable base-image packages. It additionally rebuilds appwrite/base and openruntimes/executor to clear remaining image vulnerability findings. Upgrading from 2.7.2 requires no schema changes; use the normal upgrade command and migration step.
License: BSD-3-Clause core; enterprise services and feature terms should be confirmed separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Appwrite self-hosting on digitalocean ↗
Deployment evidence and qualifications
Self-hosted no-code database for organizing, relating and collaborating on business data.
- Baserow on DigitalOcean App Platform ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor guide deploys the Baserow application container, managed PostgreSQL and Redis, and Spaces storage in the customer DigitalOcean account, with application URL and scaling configuration. The example image tag is version-specific; choose and test the intended supported release.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application, database and storage, applies updates and configures backups.
Scope: Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
License: MIT-licensed core with paid premium features and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Baserow on DigitalOcean App Platform ↗
Deployment evidence and qualifications
Self-hosted conferencing and virtual classroom platform.
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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: Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee. The maintained 4.0 installer also explicitly documents Scaleway and Azure behind-NAT deployments.
License: GNU LGPL licence 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 →
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Deployment evidence and qualifications
Self-hosted wiki and documentation organized into books, chapters and pages.
- Cloudron customer Droplet deployment ↗
Marketplace offer · 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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 →
- Cloudron customer Droplet deployment ↗
Deployment evidence and qualifications
Open-source browser-based web archiving and collection-management application.
- Browsertrix DigitalOcean Docs ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.
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 →
- Browsertrix DigitalOcean Docs ↗
Deployment evidence and qualifications
Build operational apps and automations on customer-hosted infrastructure.
- Budibase self-hosting on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project documents its one-click Budibase server in a customer DigitalOcean Droplet and requires at least 4 GB RAM. This is separate from Budibase Cloud. Keep the internal database port private and review backups, updates and the selected image before production use.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages containers, persistent storage, credentials, backups and upgrades; account/license connectivity remains relevant.
Scope: This entry excludes Budibase Cloud. Current documentation requires outbound HTTPS for license activation/validation, and some authentication/AI capabilities depend on vendor services. Package licenses differ; paid features are not covered by the core open-source license.
License: GPLv3 core, MPL client/component packages and BSL paid-feature packages; edition terms apply
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Budibase self-hosting on DigitalOcean ↗
Deployment evidence and qualifications
Self-hosted group chat and team conversation application.
- DigitalOcean Marketplace ↗
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
ONCE Campfire application and persistent message and upload storage on DigitalOcean. The current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.
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 →
- DigitalOcean Marketplace ↗
Deployment evidence and qualifications
Source-available customer-operated business, inventory and ERP application.
- DO Marketplace ↗
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Celerp application, database and persistent business records on a DigitalOcean Droplet. The BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.
License: Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- DO Marketplace ↗
Deployment evidence and qualifications
Self-hosted customer-support inbox combining live chat, email and messaging conversations.
- Chatwoot self-hosted deployment on digitalocean ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.
Scope: Community Edition excludes paid features such as SSO/SAML, SLA policies and Captain AI. Captain integrations may send data to external model providers. Official Azure and Google Cloud deployment guides are marked work in progress; validate their instructions against current requirements before production.
License: MIT Community Edition; proprietary enterprise features and paid self-hosted plans
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Chatwoot self-hosted deployment on digitalocean ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Open-source civic participation and participatory-budgeting platform.
- DigitalOcean Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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: Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
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 →
- DigitalOcean Guide ↗
Deployment evidence and qualifications
Self-hosted discussion and community platform for workplace collaboration and customer support communities.
- Discourse supported cloud server installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
Scope: This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.
License: GPL-2.0 core; review extensions separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Discourse supported cloud server installation ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- Cloudron customer Droplet deployment ↗
Marketplace offer · 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.
- Vendor DigitalOcean application specification ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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 →
- Cloudron customer Droplet deployment ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Open-source business operations platform for people, projects, time and financial records.
- DO Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
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 →
- DO Guide ↗
Deployment evidence and qualifications
Feature management platform for targeted rollouts and remotely configured application behavior.
- Flagsmith self-hosted platform architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor explicitly names AWS, Google Cloud, Azure and DigitalOcean for team-managed Docker or Kubernetes deployments. This is a self-hosted application compatibility statement, distinct from managed Flagsmith SaaS; configure the backing services, security and edition-specific entitlements.
Application boundary: Boundary not confirmed. Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Operations: Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.
Scope: The local Compose guide is an evaluation path requiring production hardening. Point SDKs to the self-hosted endpoint; experimentation can add warehouse and ingestion services with separate operational requirements. Flagsmith v2.291.0 fixes existing authentication tokens remaining valid after a password change or reset, an identities search that could bring down the database, a security update to oauthlib, and trust in compromised eMudhra certificate authorities. Self-hosted operators should upgrade so password changes invalidate existing dashboard tokens and the database-search safeguards are present. Flagsmith v2.292.0 adds SSRF allowlisting, scopes nested writes correctly, exposes organization audit logs, and updates dnspython for security. Review outbound destinations and nested-resource authorization after upgrading.
License: BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Flagsmith self-hosted platform architecture ↗
Deployment evidence and qualifications
Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- FusionAuth in customer DigitalOcean Kubernetes ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor and provider document a full FusionAuth 1-Click Kubernetes application. The provider catalog packages 1.53.3, older than the reviewed upstream release; validate upgrades and production database/HA design.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer configures application releases, plan features, database/search, networking, TLS, secrets, backups and capacity. Kubernetes operations apply to cluster deployments; Render operates its platform while the customer configures the web service and managed database.
Scope: This is self-hosted FusionAuth, not FusionAuth Cloud. The AWS Marketplace guide sells hosted Cloud service; EKS remains a separately documented customer-hosted path. DigitalOcean’s 1-Click package is 1.53.3, distinct from upstream 1.71.0. SCIM and paid air-gap/FIPS options have Enterprise conditions; Render uses a customer-owned application/database blueprint.
License: FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- FusionAuth in customer DigitalOcean Kubernetes ↗
Deployment evidence and qualifications
Open-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.
- Official Ghost production deployment on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Ghost documents creating its Marketplace Droplet in the customer DigitalOcean account, connecting by SSH and completing Ghost-CLI, domain, TLS and mail configuration. Confirm the image and upstream runtime versions before production.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the Linode server or DigitalOcean Droplet, operating system, MySQL, reverse proxy, TLS, mail, storage, backups, monitoring and Ghost upgrades.
Scope: This entry covers self-hosted Ghost, not Ghost(Pro). The official Linode guide requires a secured Ubuntu server and hands ongoing software maintenance to the customer. Verify the current supported Node.js, MySQL and Ubuntu versions before installation.
License: MIT
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Official Ghost production deployment on DigitalOcean ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Customer-operated HR records, leave, attendance and people-management application.
- IceHrm Linux VPS Docs ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
IceHrm application, database and persistent employee documents. The listed open-source edition differs from Enterprise and paid modules. The vendor Linux guide names AWS and Linode as possible VPS hosts and provides a worked DigitalOcean path.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 listed open-source edition differs from Enterprise and paid modules. The vendor Linux guide names AWS and Linode as possible VPS hosts and provides a worked DigitalOcean path. Apply the IceHrm application corrections and recreate Docker containers from the corrected image when using that deployment mode.
License: GNU GPL-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 →
- IceHrm Linux VPS Docs ↗
Deployment evidence and qualifications
Open-source digital repository and collections platform with a community DigitalOcean deployment.
- Islandora-Devops/sandbox ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. The named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.
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 →
- Islandora-Devops/sandbox ↗
Deployment evidence and qualifications
Customer-operated content management and website publishing platform.
- DO Marketplace ↗
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
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 →
- DO Marketplace ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- Kestra on DigitalOcean Droplets with Managed Database and Spaces ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents creating a customer Droplet, installing Docker and Kestra, and connecting DigitalOcean Managed PostgreSQL and Spaces storage. The customer operates the application and configures network access, credentials, persistent storage and backups.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.
Scope: Vendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.
License: Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Kestra on DigitalOcean Droplets with Managed Database and Spaces ↗
Deployment evidence and qualifications
Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
- LibreChat deployment on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
Scope: The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.
License: MIT
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- LibreChat deployment on DigitalOcean ↗
Deployment evidence and qualifications
Commercial self-hosted appliance for controlled external file delivery and shared files.
- DigitalOcean Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- DigitalOcean Guide ↗
Deployment evidence and qualifications
Self-hosted customer live chat and support communications.
- LHC DigitalOcean Docs ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
PHP application and database on a customer DigitalOcean Droplet. Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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: Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.
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 →
- LHC DigitalOcean Docs ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Commercial self-hosted email marketing application.
- MailWizz DO ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- MailWizz DO ↗
Deployment evidence and qualifications
Self-hosted marketing automation for email campaigns, lead nurturing, forms and landing pages.
- Mautic production and staging instances on AWS EC2 ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The official project guide names AWS, DigitalOcean and Linode as hosts of the Mautic production application, then describes cloning that application to staging; the worked snapshot examples use EC2 and a DigitalOcean Droplet. This is a project hosting compatibility statement rather than a storage integration. Follow current Mautic, PHP/database and production security requirements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the web/database servers, scheduled jobs, updates, backups and email-delivery integration.
Scope: Install the production package or documented Composer distribution rather than the GitHub development checkout. Email marketing still requires configured delivery infrastructure or an external provider. Self-hosting does not by itself establish privacy compliance, consent or deliverability.
License: GPLv3-or-later core; separately selected integrations, hosting and support may carry their own terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Mautic production and staging instances on AWS EC2 ↗
Deployment evidence and qualifications
Self-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- Meilisearch Community Edition on a DigitalOcean Droplet ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents installation on a customer DigitalOcean Droplet using its official binary installer, persistent service configuration and production security steps. This is a customer-operated Droplet, not a managed Meilisearch Cloud deployment.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.
Scope: The reviewed provider guides deploy a customer-operated server rather than a managed Meilisearch service. Meilisearch Cloud is the vendor-recommended production option, but the Community Edition is explicitly available for independent hosting. Community Edition does not include Enterprise-only sharding, so the documented VM paths do not establish a highly available or horizontally sharded topology. Configured remote embedders or LLM providers can receive indexed or query content; user-provided vectors and customer-selected local endpoints can produce a different data boundary. Meilisearch 1.56.1 and 1.55.1 were security maintenance releases; current 1.57.0 includes those fixes. Affected deployments should move to 1.57.0 or an appropriate later supported patch and review the vendor's branch guidance.
License: MIT License for Community Edition. Enterprise Edition uses a BUSL license, cannot be freely used in production and requires a commercial agreement for production self-hosting.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Meilisearch Community Edition on a DigitalOcean Droplet ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Business intelligence and dashboards on your infrastructure.
- Metabase production hosting compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.
Application boundary: Boundary not confirmed. Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Operations: Your team manages hosting, upgrades and the application database.
Scope: Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.
License: Open-source and commercial options
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Metabase production hosting compatibility ↗
Deployment evidence and qualifications
Automate integrations and business processes with a customer-hosted workflow editor and runtime.
- n8n self-hosted deployment on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope: This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.
License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- n8n self-hosted deployment on DigitalOcean ↗
Deployment evidence and qualifications
Open-source zero-trust networking control plane self-hosted on a customer cloud VM.
- NetBird self-hosted control plane on a cloud VM ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Community Edition. Vendor support commitment: not assessed; confirm the selected release and contract.
The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
Scope: This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.
License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- NetBird self-hosted control plane on a cloud VM ↗
Deployment evidence and qualifications
Commercial self-hosted gateway for controlled sharing of customer object storage.
- DO Marketplace ↗
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- DO Marketplace ↗
Deployment evidence and qualifications
Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
- NocoDB community cloud installation methods ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Scope: The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.
License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- NocoDB community cloud installation methods ↗
Deployment evidence and qualifications
Digital collections publishing for libraries, archives, museums and research institutions.
- Cloudron customer Droplet deployment ↗
Marketplace offer · 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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 →
- Cloudron customer Droplet deployment ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 enterprise search and AI assistant platform with connectors and retrieval infrastructure.
- Onyx on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
Scope: This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.
License: MIT Community Edition; Business and Enterprise features use separate commercial terms.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Onyx on DigitalOcean ↗
Deployment evidence and qualifications
Self-hosted health-financing software supporting health-insurance claim submission, review and reimbursement.
- openIMIS production server deployment on named VPS providers ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project wiki explicitly names AWS, Azure, Google Cloud and DigitalOcean for a VPS deployment of the Django/Gunicorn backend and Nginx frontend. Review the current distribution and modules, database and TLS configuration. Harden example settings such as debug mode, service users and credentials before handling production or health data.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Scheme operator and implementation partner host, configure and maintain the installation.
Scope: A sector-specific claims product for health-financing and social-protection programs. Workflows include automated checks, medical review and reimbursement calculations. General property-and-casualty claims functionality was not established. Follow the official production and security guidance when implementing the Docker distribution.
License: Open-source; official distribution licensed under AGPL v3
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- openIMIS production server deployment on named VPS providers ↗
Deployment evidence and qualifications
OpenTelemetry-based AI tracing and evaluation platform for model and agent operations.
- OpenLIT deployment on DigitalOcean Kubernetes ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
DigitalOcean documents the OpenLIT Kubernetes add-on, Helm installation verification and access to the application in the customer cluster. Review the included application and ClickHouse versions, persistent storage and access controls; this is the observability platform, not just its instrumentation SDK.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages telemetry collection, analytical storage, capture policies, access controls, retention and upgrades.
Scope: Configure instrumentation to send telemetry to the self-hosted receiver. Optional LLM-based evaluations and integrations can call external services; hosting the observability platform does not host every model being observed.
License: Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- OpenLIT deployment on DigitalOcean Kubernetes ↗
Deployment evidence and qualifications
Node.js application backend for data APIs, users, permissions and server-side application logic.
- Parse Server cloud hosting options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide explicitly lists AWS, Google Cloud, Azure and DigitalOcean as hosts for the Parse Server application and provides installation guidance. This compatibility statement is separate from the DigitalOcean Spaces file adapter; select current Node.js/database versions and secure the deployed server.
Application boundary: Boundary not confirmed. Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
Scope: Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.
License: Apache License 2.0 for upstream Parse Server.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Parse Server cloud hosting options ↗
Deployment evidence and qualifications
Open-source PAYGO loan, asset-finance, customer and payment operations platform.
- DigitalOcean App Spec ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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 publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.
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 →
- DigitalOcean App Spec ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Commercial centralized version-control server deployed from Perforce's cloud quickstarts into customer infrastructure.
- P4 Server on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Perforce documents a P4 Server Droplet in the customer's DigitalOcean account.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.
Scope: Helix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.
License: Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- P4 Server on DigitalOcean ↗
Deployment evidence and qualifications
Self-hosted photo library indexing, search and album management.
- PhotoPrism DO Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
PhotoPrism application, database and persistent original photos and previews. Community AGPL-3.0 and paid editions have different features. External maps or configured services may receive requests; archive photos and the database consistently.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 AGPL-3.0 and paid editions have different features. External maps or configured services may receive requests; archive photos and the database consistently.
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 →
- PhotoPrism DO Guide ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 enterprise content management and publishing platform.
- plone-in-a-box ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
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 →
- plone-in-a-box ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Self-managed team messaging and collaboration platform deployed on customer cloud infrastructure.
- Rocket.Chat self-managed deployment on DigitalOcean ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
The current publisher installation page explicitly names DigitalOcean for self-managed deployment. The older Marketplace one-click guide is unsupported and is not presented as a supported one-click method.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates MongoDB, application instances, storage, TLS, monitoring, backups, scaling and upgrades; plan entitlements govern enterprise capabilities.
Scope: New self-managed deployments receive the Starter plan, intended for evaluation or small non-critical teams and limited to 50 users. Commercial, Government, Defense and air-gapped capabilities require the applicable plan. Push notifications normally require Rocket.Chat Cloud registration and outbound access unless an alternative gateway is configured. Launchpad excludes Omnichannel and federation workloads and includes a closed-source operator. The documented DigitalOcean Marketplace one-click path is unsupported. Rocket.Chat 9.0.0 moves LDAP, SAML, and Custom OAuth to premium editions and removes several login integrations. It also fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure; verify at least one administrator login path before upgrading.
License: MIT Community Edition core; Enterprise Edition code and non-community plans use separate proprietary licensing.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Rocket.Chat self-managed deployment on DigitalOcean ↗
Deployment evidence and qualifications
Commercial self-hosted Linux threat-hunting and investigation platform.
- DigitalOcean 1-Click ↗
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Sandfly application services and database on a customer DigitalOcean Droplet. The reviewed provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 reviewed provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- DigitalOcean 1-Click ↗
Deployment evidence and qualifications
Self-hosted content management system with flat-file and database options.
- DigitalOcean Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Statamic Laravel application, persistent content and configured media storage. The per-site source-available licence and commercial Pro features require review; possession of public source does not permit unrestricted reuse on other sites.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 per-site source-available licence and commercial Pro features require review; possession of public source does not permit unrestricted reuse on other sites.
License: Statamic per-site source-available licence; Pro features have separate commercial terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- DigitalOcean Guide ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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
Build internal tools and business applications with a customer-hosted app builder.
- ToolJet on a customer DigitalOcean Droplet ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor guide creates an Ubuntu Droplet, configures its firewall and installs Docker and Compose, then follows the ToolJet Docker deployment. The current instructions include LTS and enterprise image guidance; license and AI endpoint requirements remain edition-dependent.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.
Scope: The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.
License: AGPL-3.0 open-source foundation; commercial self-hosted editions/plans
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ToolJet on a customer DigitalOcean Droplet ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 website and event analytics application with dashboards and PostgreSQL storage.
- Umami self-hosting on a DigitalOcean Droplet ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
Scope: Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.
License: MIT License for upstream Umami.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Umami self-hosting on a DigitalOcean Droplet ↗
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 cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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 ↗
Deployment evidence and qualifications
Open-source self-hosted wiki and knowledge-management content platform.
- Wiki.js-maintained DigitalOcean cloud image ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Wiki.js lists DigitalOcean under its maintained cloud-image installation paths. DigitalOcean separately documents the Marketplace image and deployment into a customer DigitalOcean project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the DigitalOcean project, Droplet or Kubernetes runtime, PostgreSQL, storage, TLS, identity, backups and upgrades.
Scope: The current installation documentation covers Wiki.js 3.x and warns against the unversioned latest container tag. Pin a supported release, replace default administrator credentials, use a production PostgreSQL deployment and confirm the DigitalOcean image version and upgrade path.
License: AGPL-3.0
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Wiki.js-maintained DigitalOcean cloud image ↗
Deployment evidence and qualifications
Run scripts and workflows with customer-operated execution workers and an app builder.
- Windmill upstream self-hosting provider compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
Application boundary: Boundary not confirmed. Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
Scope: This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.
License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Windmill upstream self-hosting provider compatibility ↗
Deployment evidence and qualifications
Open-source content management system with documented customer-account deployments across major clouds and application-provider images.
- WordPress DigitalOcean 1-Click application ↗
Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
Scope: This entry covers WordPress.org self-hosting, not WordPress.com SaaS. Provider blueprints accelerate installation but do not replace application hardening, backup, patching and plugin review. Provider packages can lag upstream. The current recommended PHP/database versions and application/plugin stack need a separate patch and HA review. WordPress 7.1.5 is a security release fixing multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Security fixes were backported to eligible older branches. Update immediately, and verify provider images that still advertise 7.1.4 or earlier rather than assuming the platform package is current.
License: GPLv2 or later; themes, plugins and provider packaging may have separate terms.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- WordPress DigitalOcean 1-Click application ↗
Deployment evidence and qualifications
Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.
- Official Zabbix DigitalOcean image ↗
Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
DigitalOcean lists full Zabbix Server Droplet packages, including 6.0.17 (image 131398452, slug zabbix-zabbixserver60). These older images require supported-branch/patch/OS review; they are not current upstream 8.0 packages.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.
Scope: Provider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.
License: AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- Official Zabbix DigitalOcean image ↗
Deployment evidence and qualifications
Topic-organized team chat with a documented self-hosted server.
- Zulip server installation options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current server installation documentation explicitly offers a preconfigured DigitalOcean Droplet as a self-hosting option, separately from Zulip Cloud. Operate the server, backups and upgrades yourself; mobile push notifications use a separately configured external service.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Operate server security, email delivery, backups, upgrades and any optional external notification services.
Scope: This listing covers the self-hosted server; review mobile notification and support service terms for your deployment. Zulip 13.2, released November 13, 2026, fixes new installations failing when PostgreSQL cannot start because postgresql-common 294 leaves the PostgreSQL log directory owned by root; upgrades are unaffected.
License: Apache License 2.0; hosted services and commercial support plans are separate.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Zulip server installation options ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings