Open-source Render alternatives

Coolify is an open-source, self-hostable alternative to Heroku, Vercel and Netlify. It manages servers, applications and databases on hardware you control, and the only requirement is SSH access, so a VPS, a bare-metal machine or even a Raspberry Pi can serve as a target. Your configuration stays on your own servers, and if you stop using Coolify the resources it deployed keep running.

Applications can be built from GitHub, GitLab, Bitbucket or Gitea using Nixpacks, Railpack, a Dockerfile, Docker Compose or a prebuilt image. Hundreds of one-click services and managed-style databases come with persistent storage and generated credentials. Deployments can run on every push, create pull-request previews, call webhooks and roll back to retained images. Custom domains, automatic HTTPS, reverse proxies and health checks cover networking, while logs, container terminals and resource monitoring help with operations.

Backups, scheduled tasks, secrets, environment variables and notifications are built in, and resources can be managed through the dashboard, an API, a CLI or MCP, with team-based access controls. Coolify is Apache-2.0 licensed and built mainly with PHP; a hosted Coolify Cloud option exists for people who prefer not to run the control plane themselves.

Dokploy is an open-source, self-hostable platform as a service that simplifies deploying and managing applications and databases. It is positioned as an alternative to Heroku, Vercel and Netlify, and it runs on a VPS you control, installed with a single command.

It can deploy apps in languages such as Node.js, PHP, Python, Go and Ruby, create and manage MySQL, PostgreSQL, MongoDB, MariaDB, libsql and Redis databases, and schedule database backups to external storage. Docker Compose is supported natively, and multiple nodes can be clustered with Docker Swarm or managed as remote servers. One-click templates cover open-source apps such as Plausible, PocketBase and Cal.com, Traefik handles routing and load balancing, and live monitoring shows CPU, memory, storage and network usage per resource.

A CLI and API allow automation, and notifications about deploy success or failure can go to Slack, Discord, Telegram or email. The license is listed as 'Other', so check the repository terms before redistribution. For people who want to skip installation there is a hosted Dokploy Cloud.

Kamal is a deployment tool for web applications that can run anywhere, from bare metal servers to cloud virtual machines. It uses a proxy component called kamal-proxy to switch requests between containers without downtime, and it works across multiple servers by running commands over SSH using SSHKit.

Originally built for Rails applications, Kamal works with any web app that can be packaged in a Docker container. Documentation on installation, configuration and commands is on kamal-deploy.org, and the documentation itself lives in a separate repository where improvements are welcome.

Kamal is written in Ruby, developed by Basecamp, and released under the MIT license. Because it deploys to servers you control, it suits teams who want a simple alternative to hosted platforms while still getting rolling, zero-downtime releases.

ZaneOps is an open-source, self-hosted platform for deploying and managing applications on your own servers. It can host static sites, web apps, databases, workers and prepackaged services such as Supabase, WordPress or Ghost, and it is positioned as a free alternative to Heroku, Railway and Render.

Under the hood it uses Docker Swarm for scalability and Caddy for routing, and it presents a dashboard with onboarding, project views, HTTP logs and runtime logs. Projects group related services together, and the documentation covers installation steps and further setup. The project says it was inspired by Plane for its contribution guidelines and by Coolify and Dokploy as other self-hosted deployment tools.

ZaneOps is written in Python, and its licence is listed as other, so review the repository terms before relying on it. It is installed on a server you control, with a milestone-based public roadmap. It suits solo developers, startups and teams that want a Heroku-style workflow without paying for a managed PaaS or giving up control of their infrastructure.

SwiftWave is an open-source platform as a service that you run on your own server. It lets you deploy and manage applications on a bare-metal machine, a Raspberry Pi or any VPS, giving a Heroku-like workflow without relying on a managed platform.

The project positions itself as an open-source alternative to Heroku, Netlify and Render. It uses Docker, with Swarm mode among its topics, and is described as lightweight. SwiftWave and its dependencies support AMD64, ARM64 and ARMv7 architectures and run on Debian, Ubuntu, Raspbian, Fedora, CentOS, AlmaLinux, Rocky Linux and similar distributions.

It can be installed on providers such as Hetzner, DigitalOcean, Linode, AWS or GCP following the guide on swiftwave.org, and it is released under the Apache-2.0 license. The team runs a community Slack channel and accepts sponsorship through GitHub Sponsors.

Zeabur is a platform for deploying services with one click, presented as an AI DevOps engineer that handles deployment work so developers can focus on code. Through natural language in an AI agent, it can deploy services, rent servers, manage domains, configure databases and troubleshoot issues.

It analyzes your code to detect the language and framework, so no Dockerfile or compose file is required, and builds and redeploys on every push to a connected repository. Deployment options include GitHub integration, Dockerfiles, Docker images, a CLI and a Chrome extension. AI-focused tools include an official Claude Code plugin, an MCP server for assistants such as Claude Desktop and Cursor, and a VS Code and Cursor extension. Infrastructure can be single servers, either bought from Zeabur or brought from providers like AWS, GCP and Hetzner, or clusters.

The repository is under MPL-2.0 and has docs-related topics, but Zeabur itself is a managed commercial platform with its own documentation, templates and community forum. It is relevant to teams that want a hosted PaaS rather than software they run themselves.

bex is an open-source alternative to Render, built so that both developers and coding agents control deployments through the same control plane. You push Git changes and bex builds and deploys to HTTPS on infrastructure you own, aiming for the Render, Heroku and Railway experience without operating Kubernetes by hand.

It deploys Dockerfiles or native Go, Node.js, Python, Ruby, Rust and Elixir projects, understands Render-style render.yaml Blueprints and offers a Render-compatible CLI and API. The dashboard, REST, GraphQL, MCP, CLI and Kubernetes resources all operate the same core, with no dashboard-only actions. Service types include web services, private services, workers, cron jobs, static sites, managed Postgres and managed Key Value, with logs, metrics, deploy history, rollbacks, domains, TLS and SSH. The same Go operator runs against Docker-container machines locally or Hetzner machines in production-style clusters, and compatibility claims are tracked in a Render parity ledger.

The README warns that bex is in active development and not ready for production workloads, and that APIs and configuration may change. It is licensed under Apache-2.0.