HivePaaS
github.com/hivepaas/hivepaas- Category
- Developer Tools
- Rank
- No. 1149Tools index
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Deployment & Operations
- GitHub
- 333 stars
- Latest release
- v1.0.0-beta6
- Date
About
A lightweight, self-hosted Platform-as-a-Service built on Docker Swarm, positioned as an open-source alternative to Heroku, Render and Coolify. It deploys apps from a Docker image or Git repository, with generated Dockerfiles for 15+ languages and frameworks, deploy on push and pull request previews.
What it does
HivePaaS turns one or more Linux servers into your own hosting control panel. A single install script sets up the cluster, a Postgres database, Redis and the Traefik web proxy, then serves a dashboard where you ship services, attach domains with automatic certificates, schedule jobs and run small serverless functions. A Go agent on every machine does the hands-on work: building containers, running backups, scanning for known vulnerabilities and reading node metrics, while the central server talks to it over gRPC, a remote procedure call protocol.
Why it's ranked here
The breadth is real and so is the care. Releases must carry two independent signatures, one classical and one post-quantum, and both the app and the installer refuse anything less; the signing keys never touch CI, so a compromised build pipeline cannot push code onto installed servers. Settings that could lock you out are applied on trial and reverted unless confirmed. The code base shows the same discipline: a written layering rule, custom linters, race and vulnerability checks in the build. Against that, it is self-described beta, and the free tier caps a cluster at two nodes and twenty apps.
What's good
Secrets are masked in every API response by default, and revealing one needs three things at once: server config that allows it, a specific permission, and an audit log entry. The command line tool states which API version it was built for, and the server refuses its writes with an explicit error if it is older, so a stale client cannot silently erase fields it never knew about. Importing a Compose file reports every option it drops and why, rather than guessing. The license key is checked offline and the project says it sends no telemetry.
Tradeoffs
It is Docker Swarm only, so teams standardised on Kubernetes get nothing here. The security policy calls the project beta and supports only the latest release. Without a paid key the Bee plan allows 2 nodes, 2 users, 20 apps, 20 functions and 2 previews at once; limits block creating, not running. The per-node agent has root on your servers by the project's own description. Compose import skips any service that only builds from source and has no image, and drops proxy and orchestrator labels. The control plane needs Postgres, Redis and Traefik, with 4 CPUs and 8 GB of memory recommended.
How to use it well
Fit: a small team or solo developer who wants a hosted-platform experience on servers they rent, with backups, logs and vulnerability scans included, and who is comfortable with Swarm. Start on one server with ports 80 and 443 open and try the read-only demo first. Keep each Compose service pointed at a prebuilt image before importing, and update promptly, since only the newest release gets fixes. Use the MCP server or REST API to let scripts and AI assistants drive deployments. It does not cover Kubernetes clusters, and a fleet above two nodes means paying.
Technical notes+
Two binaries share one dependency-injection graph built with uber fx: hivepaas_app/cmd/app/main.go boots config, a data key, the task queue, a settings-probation watcher (the lockout rollback) and the updater in a fixed, commented order, while hivepaas_app/cmd/agent/main.go registers twelve gRPC services on one AgentServer (artifact, container, Docker API, file, function, image build, image scan, node, node cleanup, repo server, volume, agent) in hivepaas_app/interface/agent/server/server.go. docs/ARCHITECTURE.md fixes the import direction handler to dto to usecase to service to repository to entity. tools/releaseverify/main.go caps the signed envelope at 4 MiB and emits the release manifest only when both the Ed25519 and ML-DSA-65 signatures verify. hivepaas_app/service/composeservice/composeserviceimpl/app.go drops traefik., hivepaas. and com.docker.* labels and maps restart unless-stopped to Swarm's any.
Observed
- License
- Apache 2.0 (LICENSE)
- Language
- Go module, Go 1.27 toolchain (go.mod); React and TypeScript dashboard per README.md
- Install surface
- curl-to-sudo-bash installer for Debian, Ubuntu, Fedora, RHEL, Alpine and other Linux distributions; Docker 29.5 or newer (README.md)
- Interfaces
- Web dashboard, REST API with OpenAPI description, MCP server, separate CLI (README.md, docs/ARCHITECTURE.md)
- Orchestration
- Docker Swarm only, with Traefik v3 ingress, PostgreSQL and Redis required (README.md)
- Free plan limits
- 2 nodes, 2 users, 20 apps, 20 functions, 2 concurrent previews without a license key (README.md)
- Release integrity
- Ed25519 and ML-DSA-65 signatures both required before an install accepts a release (tools/releaseverify/main.go, docs/RELEASING.md)
- Privilege
- Agent runs on every node with root on the host (SECURITY.md)
- Build checks
- Makefile targets for race tests, coverage, nilaway, govulncheck, Trivy and custom goroutine and error-code linters (Makefile)
Read from README.md, go.mod, LICENSE, Makefile, docs/ARCHITECTURE.md, SECURITY.md, hivepaas_app/cmd/app/main.go, hivepaas_app/cmd/agent/main.go, hivepaas_app/interface/agent/server/server.go, hivepaas_app/service/composeservice/composeserviceimpl/app.go, docs/RELEASING.md, tools/releaseverify/main.go.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.