Open-source Vercel 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.

Sealos describes itself as an AI-native cloud operating system built on Kubernetes. It aims to cover the whole application lifecycle in one platform, from development in cloud IDEs to production deployment and day-to-day management, and it targets teams building AI applications, SaaS platforms, managed databases and microservice architectures.

Core pieces include Devbox cloud development environments that can be opened from editors such as VS Code and Cursor, managed MySQL, PostgreSQL, MongoDB and Redis databases, S3-compatible object storage, and an App Launchpad for deploying Docker images. An app store offers one-click deployment of larger applications, and workspace-based multi-tenancy supports enterprise use. Full Kubernetes remains accessible underneath.

Sealos is written mainly in TypeScript and Go and runs on Kubernetes. Repository topics point to cluster installation features such as high-availability Kubernetes through kubeadm, and the project offers a hosted cloud at sealos.io. The repository lists the license as 'Other', so check the license file for the exact terms.

Openship is an open-source deployment platform that you can host yourself. You point it at a repository and it builds the app, ships it to a server, routes traffic to it and terminates TLS, with CI/CD built in so that pushes to a repository can trigger new deployments.

You can drive it from a desktop app, a web dashboard or a command-line tool. The desktop app runs the control plane on your own machine while it is open and connects to a server over SSH, which suits solo use. A self-hosted server started with the openship up command adds push-to-deploy and team access. Applications can run on that same machine, on another server, or on Openship Cloud, a managed option based on sandboxes.

The project is licensed under Apache-2.0 and written in TypeScript. Its tagline stresses owning your infrastructure, and the repository lists AI agents among its themes. It fits individuals and small teams that want a self-run alternative to managed deployment platforms.

Kubero, pronounced Kube Hero, is a self-hosted platform as a service that lets developers deploy applications on Kubernetes without specialized knowledge. It follows the twelve-factor app principles and can run applications from existing containers or from source code. It is presented as a free alternative to Heroku, Vercel and Netlify, and the tagline also compares it with Coolify, Dokku and Portainer.

Features listed in the README include Docker deployments on Kubernetes without Helm charts, more than 160 app templates for popular software such as WordPress and Grafana, and CI/CD pipelines with several staging environments. It runs as a Kubernetes operator with a web interface, and topics mention GitOps and internal developer platforms. A demo instance and a video walkthrough are available.

Kubero is written in TypeScript and licensed under GPL-3.0. You run it on your own Kubernetes cluster. It suits small teams and developers who want push-to-deploy convenience on infrastructure they own.

Tau is the open-source core of Taubyte, described as a fullstack workspace for humans and machines. It is a cloud platform written in Go that spans the development environment, building applications, and deploying and running them. Topics place it in serverless computing, WebAssembly, peer-to-peer distributed systems, CDN, and cloud-native platform-as-a-service. It is released under the BSD-3-Clause license.

The quickest way to try it is to start a local cloud with the dream tool. For real use, you deploy Taubyte to your own servers or VMs, either manually or with the automated Spore Drive tool, and the documentation at tau.how covers the platform, deployment, and getting started. A video series called the Hitchhiker's Guide to Taubyte provides guided demos.

The project welcomes contributions through a standard fork, branch, test, and pull request workflow, with good first issues labeled. Tau suits developers and platform teams that want to run their own cloud-like environment, avoid dependence on a single hyperscaler, and experiment with a WebAssembly-based serverless model.

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.

Temps is an open-source, self-hosted platform written in Rust that aims to replace a stack of separate services. Its description positions it as an alternative to Vercel, Sentry, PostHog, Pingdom, Resend and E2B, covering deployments, web analytics, session replay, error tracking, OpenTelemetry, email, sandboxes and an AI gateway in a single binary.

It is built to be driven by AI agents as well as people. Every dashboard action is also a CLI command, with more than 440 operations in 69 groups, and the project ships skills for Claude Code, Codex and OpenCode so an agent can deploy, inspect traces or add a domain. An AI chat answers questions from your own telemetry, read-only by default, and an AI gateway exposes OpenAI, Anthropic, xAI and Google Gemini models through one OpenAI-compatible endpoint using your own keys.

Other built-in pieces include web analytics with funnels and rrweb session replay, uptime monitors with alerts for failed deploys and expiring certificates, and Sentry-compatible error tracking. Temps is licensed under Apache-2.0, and the latest tagged release is an early 0.0.x version, so expect rapid change.

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.