The deploy platform on your own servers
Harblet is an alternative to Vercel, Render and Heroku that you host yourself. One command installs it on a fresh Ubuntu server. From then on you deploy Docker images, Git repositories and databases from the browser.
Run on a fresh Ubuntu server
curl -fsSL https://raw.githubusercontent.com/harblet/harblet/main/install.sh | sudo sh
From a fresh server to production in three steps
No Kubernetes to learn and no YAML to write. Everything after the install happens in the browser.
Everything a deploy needs
Harblet covers the path from code to a running service with a domain, plus the backups and updates that keep it running.
Add a server with one command
Harblet runs on k3s, the lightweight Kubernetes from the CNCF. It installs it, configures it and upgrades it for you. You never touch Kubernetes.
Servers → Add server shows a command with a token that expires after 24 hours. Harblet keeps no SSH keys.
Traffic between servers goes through WireGuard, and each project's services are isolated from other projects.
When a server fails, its image and Git services start on another one. Services keep running even while Harblet itself is down.
Run on the new server
curl -fsSL https://harblet.example.com/api/join-scripts/<token> | sudo sh
Deploy from your pipeline
Every image and Git service has a secret deploy URL. Call it at the end of your CI pipeline, after tests and linting pass.
A Git service builds the newest commit of its branch. An image service pulls the tag again.
If the deployment can't start, the hook answers with an error, so
curl --fail fails the pipeline..github/workflows/deploy.yml
- name: Deploy
run: curl --fail -X POST ${{ secrets.HARBLET_DEPLOY_HOOK }}
Questions
Harblet is source-available under the Business Source License 1.1. Production use is free while all your installs together manage one server and you don't offer Harblet to others as a hosted or managed service. For more servers, write to mail@harblet.com about a commercial license. Each version becomes available under the Apache License 2.0 four years after its release. See License.
A fresh server with Ubuntu 24.04 or 26.04, root access, at least 2 CPUs and 4 GB of memory, and internet access. Ports 80 and 443 must be open for your services, and port 3000 for Harblet until it has its own domain. See Installation.
No. The install script sets up k3s, and Harblet manages it from then on, upgrades included. You work in Harblet's browser interface.
You upload a certificate for your domains under SSL Certificates, and Harblet serves it for every domain it covers. Wildcard certificates work. Harblet doesn't request certificates from Let's Encrypt for you at the moment.
Its services start on another server, in tests about 80 seconds after the failure. Databases stay with the server that holds their data and come back when it does. The first server runs Harblet and receives all traffic, so keep a backup of Harblet to restore it onto a new server if it fails. See Servers.
Deploy on your own servers today
One command on a fresh Ubuntu server, then open the address it prints and create the first account.