Live runtime logs
Follow the website, every worker and Redis as it happens. Filter, show errors only, pause, download.
DeployPro builds, health-checks and ships your apps to a server you own. Previews for every branch, instant rollback, domains with HTTPS, logs and metrics, without the per-seat bill.
In production on DeployPro today
Detected automatically, or bring your own Dockerfile
Anatomy of a deploy
01 · Source
The GitHub App sees the commit, puts a pending check on it and queues a build. A pull request gets its own preview.
push · main · a1b2c3d
02 · Build
Your Dockerfile, or one written for the framework it detects. Secrets are mounted, never baked into a layer.
next build · 1m 52s
03 · Deploy
The new container starts beside the old one and must answer its health check. If it doesn’t, nothing changes.
healthy after 1.9s · 200 /
04 · Production
The router switches in one step: no dropped requests. The previous release stays ready for a one-click rollback.
live · blog.acme.com
Collaborate
Open a pull request and DeployPro builds it at its own address, puts the link on the PR and a ✓ on the commit. Review the real thing, not a screenshot. Merge, and production follows.
Operate
Follow the website, every worker and Redis as it happens. Filter, show errors only, pause, download.
CPU, memory and network for each project over an hour, a day or a week, sampled every minute.
Releases switch only after a health check passes. Earlier ones stay ready, so going back is one click, not a rebuild.
New · AI assistant
One click on a failed deployment. Claude reads the end of the build log and your settings, then says what broke, why, and exactly what to change, with how sure it is.
Next.js could not load its compiler on Alpine. high confidence
The node:22-alpine image needs the musl build of SWC, which your lockfile doesn’t include because it was made on macOS.
npm i -D @next/swc-linux-x64-musl and commit the lockfile.node:22-slim in your Dockerfile.Explained by Claude · secrets hidden
The real thing
Screens from DeployPro itself: the Overview with the server’s memory and CPU and every project’s share, and a project’s live logs.
Platform
Add a domain; DeployPro creates the DNS records through Cloudflare and the certificate through Let’s Encrypt.
Queue consumers, schedules and background services beside your site, with replicas, pause and resume.
A private Redis per project for BullMQ, Celery or Sidekiq, kept running and backed up.
Viewer, developer, admin and owner roles, two-factor sign-in, API tokens and an audit log of every change.
Deploy results and outages to Slack, Discord or Microsoft Teams, per project.
Daily backups of the database, volumes and Redis, with an off-site copy to a Hetzner Storage Box.
Variables are encrypted at rest, passed to builds as secret mounts that never reach an image layer, and shown only when someone with the right role asks. Paste a whole .env to move from another host in one go.
Ownership
Rent one server from Hetzner or anyone else. Run your sites, APIs, workers and queues on it with the workflow you’d expect from a hosted platform, and keep the data, the logs and the bill.
Self-host
On a fresh Ubuntu or Debian server with a domain on Cloudflare. The installer sets up Docker, the secrets, the firewall, HTTPS and the dashboard, then checks everything works. Run it again to upgrade.
# on the server
git clone https://github.com/ICOFCUCAM/deploygenus.git /opt/deploypro
cd /opt/deploypro
DEPLOYPRO_DEPLOY_DOMAIN=deploys.example.com \
DEPLOYPRO_ACME_EMAIL=you@example.com \
CF_DNS_API_TOKEN=… bash scripts/install.sh
✓ Docker ready ✓ TLS issued
✓ Database migrated ✓ doctor: all clear
Already running DeployPro? Your dashboard is at app.deploypro.us.
deploypro bot · commented
DeployPro preview for
a1b2c3dis ready.