Software on Render
Software with a documented deployment path in a customer environment on Render.
10 listings, including 10 from other publishers. Search and filter Render 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
- Render workspace, project and services; platform-managed infrastructure
- Network
- Private services with separately exposed public endpoints
- Identity & access
- Workspace membership and deployment credentials
- Deployment tooling
- Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. 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
- Services in the same region can use Render private networking. Free web services can send but cannot receive private-network requests. Review the actual paid service and endpoint requirements. 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
11 categories on Render. Counts show matching listings; a listing can appear in more than one category.
Business operations3 categories
Content & collaboration1 category
Data & analytics1 category
Developer platforms & operations3 categories
AI tools & infrastructure3 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
AI observability and evaluation server for traces, datasets and application experiments.
- Phoenix self-hosted Render Blueprint ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
Scope: The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.
License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Phoenix self-hosted Render Blueprint ↗
Deployment evidence and qualifications
Self-hosted no-code database for organizing, relating and collaborating on business data.
- Baserow Render application template ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provides a full application template using paid Render compute and PostgreSQL plans. Its published plan prices and repository branch examples can age; verify the current template, compatible release, resources and data persistence rather than assuming a free production tier.
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 Render application template ↗
Deployment evidence and qualifications
Self-hosted customer engagement and messaging orchestration platform.
- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
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: Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
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 →
- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- Vendor Render application blueprint ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound 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 →
- Vendor Render application blueprint ↗
Deployment evidence and qualifications
Open-source business operations platform for people, projects, time and financial records.
- Render 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 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 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 →
- Render Guide ↗
Deployment evidence and qualifications
Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- FusionAuth and PostgreSQL in customer Render ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
FusionAuth provides a Render blueprint deploying the full application and PostgreSQL in the customer’s account/project. Production needs paid resource capacity and a deliberate database/backup design.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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 and PostgreSQL in customer Render ↗
Deployment evidence and qualifications
Self-hosted LLM observability, evaluations and prompt-management platform.
- Langfuse v4 community Render Blueprint ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
Scope: Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.
License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Langfuse v4 community Render Blueprint ↗
Deployment evidence and qualifications
Self-hosted AI API gateway providing model routing, access controls and usage tracking.
- LiteLLM Railway and Render deployment options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
Scope: The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.
License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- LiteLLM Railway and Render deployment options ↗
Deployment evidence and qualifications
Self-hosted headless CMS with structured content, APIs and assets.
- Render Guide ↗
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 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 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 →
- Render Guide ↗
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: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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 ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings