Pier
In productionA self-hosted dashboard for putting projects on your own servers, with domains, HTTPS and deploys that roll back on their own when something fails.
- 350+
- services in the catalog
- v0.9.0
- Pier release
- ~200
- test files
Overview
Pier came from a practical frustration: managed deploy platforms get expensive fast, and running a VPS by hand is fragile. It gives you a platform experience ("put my project online") on servers you control.
It works at three levels on the same infrastructure: platform (applications, databases and a catalog of ready-made services), plain Docker (every container on the server, whether Pier created it or not) and optional Kubernetes, with imported clusters or a K3s that Pier creates.
What it does
- Safe deploys
- Each deploy waits for readiness before switching traffic and rolls back to the previous version if the check fails.
- Service catalog
- More than 350 ready-made services (databases, queues, tools), with generated passwords and automatic compose validation.
- Domains and HTTPS
- A managed Traefik proxy with automatic certificates; the panel itself is published over HTTPS.
- Monitoring
- CPU, memory, disk, swap, load and containers per server, with history. A collection failure shows as unavailable, never as zero.
- AI agents via MCP
- An MCP server lets Claude Code, Claude Desktop and Cursor list resources, read logs and deploy, with their own token and permissions. No tool deletes anything.
- CLI and backups
- pierctl does from the terminal everything the panel does. Instance backups are encrypted, with schedules and retention.
Architecture
Decisions and trade-offs
- No self-update, on purpose
- To update itself, the panel would need to control its own container through the Docker socket, which is equivalent to root on the server. I chose to show the notice and the commands instead.
- Operate over SSH
- Pier talks to servers over SSH. It can run on your computer and manage a VPS that only needs Docker.
- Kubernetes is optional
- Nothing in the application flow depends on a cluster. Those who need one import it; those who don't never see that complexity.
- Built to keep going without a dedicated maintainer
- CI validates, releases ship on their own from Conventional Commits (release-please) and dependencies update through automation.
Quality and operations
- About 200 Go test files and interface type checking in CI.
- Every catalog service validated with docker compose config.
- Images published to GitHub Container Registry for amd64 and arm64; one-script install.
- Documentation in Portuguese and English, with security, governance and code of conduct guides.
Status and next steps
- Beta (0.x), in production on a Linux VPS since Nov 11, 2026, with panel, proxy and five stacks validated.
- Next: more verified catalog services and teams with roles other than administrator.
Stack
GoSolidJSSQLiteDocker / ComposeTraefikKubernetes / K3sMCPGitHub Actions