opensourceprojects.dev

A broadsheet for software that doesn't ask for your email

SwiftWave: a self-hosted, open-source PaaS alternative to Heroku for any server
GitHub RepoImpressions3

Project Description

View on GitHub

SwiftWave: A Self-Hosted Heroku Alternative That Actually Works on Any Server

If you've ever tried to deploy apps the "Heroku way" but wanted to keep full control of your infrastructure, you know the struggle. Heroku is great until you outgrow its pricing or need custom server configurations. Self-hosting options like CapRoco and Dokku exist, but they often come with steep learning curves or lock you into specific server setups.

Enter SwiftWave — an open-source, self-hosted PaaS that brings the simplicity of Heroku to any server you own. No vendor lock-in, no complex Kubernetes clusters, just a clean interface and a CLI that lets you deploy apps with git push.

What It Does

SwiftWave is a Platform-as-a-Service (PaaS) you run on your own infrastructure. Think of it as Heroku, but you choose the hardware. It handles:

  • One-click app deployments from Git repos or Docker images
  • Automatic SSL via Let's Encrypt
  • Database provisioning (PostgreSQL, MySQL, Redis)
  • Environment variable management per app
  • Log streaming and monitoring right from the dashboard
  • Custom domain support with automatic DNS verification

The cool part? It runs on a single VPS or any Linux server with Docker installed. No cluster orchestration, no weird system dependencies.

Why It's Cool

Here's what makes SwiftWave stand out from the crowded PaaS landscape:

  1. Truly any server — It works on DigitalOcean droplets, Linode instances, your home lab, or even a Raspberry Pi (yes, really). The only requirement is Docker.

  2. Simple interface — The web dashboard is clean and responsive. You can manage all your apps, databases, and deployments without touching a terminal (unless you want to).

  3. Database as a service — Need a PostgreSQL database for a side project? Click "Create Database", pick the version, and get connection details in seconds. It handles backups too.

  4. Heroku-like DX — The swiftwave CLI mirrors heroku commands. swiftwave create my-app, git push swiftwave main, done. If you've used Heroku, you'll feel right at home.

  5. No lock-in — Everything is open source (MIT license). Your apps run in standard Docker containers. You can migrate away anytime without rewriting anything.

How to Try It

Getting started is surprisingly straightforward. You'll need:

  • A Linux server (Ubuntu 20.04+/Debian 11+ recommended)
  • Docker installed
  • A domain pointing to your server's IP

Quick install (one-liner):

curl -fsSL https://get.swiftwave.org | bash

After installation, access the dashboard at http://your-server-ip:3000, set up your admin account, and you're ready to deploy.

Deploy a simple Node.js app:

swiftwave create my-node-app
git remote add swiftwave swiftwave@your-server-ip:my-node-app.git
git push swiftwave main

That's it. The dashboard will show logs, expose the app on a subdomain (with optional SSL), and let you scale it with a slider.

For more detailed instructions, check the official README.

Final Thoughts

SwiftWave isn't trying to replace production-grade solutions like Kubernetes. But for personal projects, internal tools, or small team deployments, it hits a sweet spot. It gives you the convenience of a managed PaaS with the flexibility of self-hosting.

The project is still relatively new (v0.2.x), so expect some rough edges. But the core functionality works well, the community is responsive, and the roadmap looks promising. If you've been looking for a way to self-host apps without the complexity of Docker Compose or the overhead of full-blown orchestration, give SwiftWave a try.

You might find yourself wondering why you didn't do this sooner.


Originally shared on Twitter by @githubprojects

Back to Projects
Project ID: c35a1456-3df1-4f94-b459-60893c604e2fLast updated: July 12, 2026 at 05:45 AM