Beta Release
Perch is now publicly available in beta — one pane over your whole stack, fully self-hosted.
Perch is officially out in public beta. This is the first build anyone can pull and run: feature-complete enough to live on your homelab, but expect rough edges.
This is a beta
Perch is stable enough for day-to-day use, but you will hit bugs. Don’t make it your only source of truth just yet, and please report anything broken on GitHub.
Highlights
- One pane over your stack. Live host metrics, Docker stats and logs, and HTTP health checks in a single self-hosted dashboard.
- Bring your own sources. Point Perch at existing Prometheus, Loki, InfluxDB, or Graphite and view them next to everything else.
- Status pages. Public, themeable status pages with custom-domain support.
- SSO. GitHub, Google, Microsoft, GitLab, Discord, Okta, and any custom OIDC provider.
- Alerting. Health-check and container rules routed to Discord, Slack, or ntfy.
What’s new in 1.3.10
- Initial public beta of the hub + agent architecture.
- Overview console with at-a-glance agents, containers, and health-check counts.
- Live WebSocket dashboard — numbers update without a refresh.
- One-command Docker Compose deploy, plus Swarm and Portainer guides.
Known issues
Note
These are tracked and being worked on. If you hit something that isn’t listed here, open an issue so it can be triaged.
- Kubernetes and Podman monitoring are shown as “coming soon” and are not functional yet.
- Occasional reconnect delay on the live dashboard after a hub restart.
- Status-page custom-domain certificate issuance can lag on the first request.
› How to install the beta
The fastest path is Docker Compose:
docker compose up -dSee the getting-started guide for the full .env and compose file, or generate your own with the setup configurator.
Feedback
Found a bug or have a request? Open an issue — beta feedback directly shapes what 1.4 looks like.