Software on Vultr
Software with a documented deployment path in a customer environment on Vultr.
30 listings, including 30 from other publishers. Search and filter Vultr 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
- Vultr account and compute instances
- Network
- Instance networks and firewall rules
- Identity & access
- Cloud account access and server SSH keys
- Deployment tooling
- Provision compute through the console, API, CLI or Terraform, then install and operate the documented application.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. 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
- VPC provisioning
- Vultr documents isolated IPv4 VPC networks with console, API, CLI and Terraform provisioning. Configure the selected location, address ranges and routes; private application access is separate from public ingress. 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
13 categories on Vultr. Counts show matching listings; a listing can appear in more than one category.
Business operations3 categories
Governance & industries1 category
Content & collaboration5 categories
Data & analytics1 category
Developer platforms & operations3 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
Self-hosted community questions, answers and knowledge content.
- Cloudron Store ↗
Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
Application boundary: Customer 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
Self-hosted wiki and documentation organized into books, chapters and pages.
- Cloudron named-provider installation and Marketplace availability ↗
Package platform documentation · 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. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
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 named-provider installation and Marketplace availability ↗
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
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 named-provider installation and Marketplace availability ↗
Package platform documentation · 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. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
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 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 named-provider installation and Marketplace availability ↗
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
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
Self-hosted secrets-management platform with application and machine-identity access workflows.
- Vultr application deployment with Docker Compose ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Provider instructions install the application, PostgreSQL, Redis and TLS proxy on an operator-controlled Ubuntu server. Customer manages OS, application updates and data/key recovery; generic cloud integrations are not additional hosting 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 owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.
Scope: Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.
License: MIT core outside enterprise directories; enterprise features and third-party components have separate terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vultr application deployment with Docker Compose ↗
Deployment evidence and qualifications
Customer-operated content management and website publishing platform.
- Vultr Docs ↗
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 →
- Vultr Docs ↗
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 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
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
Commercial self-hosted gateway for controlled sharing of customer object storage.
- Cloud Platforms ↗
Vendor / upstream documentation · 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 →
- Cloud Platforms ↗
Deployment evidence and qualifications
Digital collections publishing for libraries, archives, museums and research institutions.
- Cloudron named-provider installation and Marketplace availability ↗
Package platform documentation · 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. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
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 named-provider installation and Marketplace availability ↗
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
Community collaborative LaTeX document authoring server.
- Vultr Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Overleaf web application, MongoDB, Redis, TeX toolchain and document storage. Community and Server Pro have different security and support entitlements. Treat TeX input as executable content and review compiler isolation; obsolete 2015 GitHub Releases are not current application snapshots. Sandboxed Compiles is documented as a Server Pro feature; do not expose Community to untrusted TeX authors on the assumption it has equivalent isolation.
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 and Server Pro have different security and support entitlements. Treat TeX input as executable content and review compiler isolation; obsolete 2015 GitHub Releases are not current application snapshots. Sandboxed Compiles is documented as a Server Pro feature; do not expose Community to untrusted TeX authors on the assumption it has equivalent isolation.
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 →
- Vultr Docs ↗
Deployment evidence and qualifications
Community document management with OCR, full-text search, metadata and ingestion workflows.
- Vultr-hosted Paperless-ngx application deployment guide ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Provider documentation installs the application, database, queue and HTTPS reverse proxy on an operator-controlled Linux server. Pin compatible current images, protect persistent document/database paths and manage VM updates. This establishes hosting guidance, not upstream vendor support.
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 permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.
Scope: Review used upstream 3.5.0. Pin a current image before importing documents and coordinate database/document backups. The canonical Railway template uses a mutable latest tag; its setup text does not certify production readiness. An older separately reviewed 3.0.5 template predates an AI-permission fix and is not the recommended package. Optional email, document converters and AI integrations need separate access and data-flow review. Release 3.5.0 moves bulk operations to asynchronous processing, adds manual workflow triggers, tightens configuration-view and descendant-tag permissions, clears sessions automatically, and fixes the default MFA trusted-authentication setting. Some installations must adjust PAPERLESS_ALLOWED_HOSTS before upgrading.
License: GPL-3.0; conversion tools and other bundled components have separate licenses.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vultr-hosted Paperless-ngx application deployment guide ↗
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
Self-hosted collaborative interface design and prototyping platform.
- Vultr Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
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: Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
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 →
- Vultr Docs ↗
Deployment evidence and qualifications
Customer-operated discussion forum and community application.
- Vultr Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
phpBB application, database and attachment storage. AWS TurnKey and the Vultr installation are separate delivery paths; the appliance label is not the phpBB release version.
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: AWS TurnKey and the Vultr installation are separate delivery paths; the appliance label is not the phpBB release 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 →
- Vultr Docs ↗
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 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-hosted headless CMS with structured content, APIs and assets.
- Install on Vultr | Squidex ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
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 application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
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 →
- Install on Vultr | Squidex ↗
Deployment evidence and qualifications
Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.
- Deploy the Supabase Marketplace application on Vultr Compute ↗
Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.
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 provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Scope: The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.
License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Deploy the Supabase Marketplace application on Vultr Compute ↗
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
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 visual conversation and form builder.
- Vultr Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that 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: Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
License: FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Vultr Docs ↗
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 content management system with documented customer-account deployments across major clouds and application-provider images.
- Vultr One-Click WordPress ↗
Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Vultr documents launching the full WordPress application on the customer’s selected server size/location and configuring its administrator, domain and TLS.
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 →
- Vultr One-Click WordPress ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings