Push to your branch. It builds, checks, and ships itself.
Point an application at a repository and the platform clones it, builds it, runs it, and health-gates the result before it takes traffic. Every push to the deployed branch arrives through a signed webhook and deploys on its own.
What you get
Any Git host
The platform generates an Ed25519 deploy key and shows you its public half. It works against GitHub, GitLab, Bitbucket, and self-hosted hosts with nothing registered anywhere.
Optional GitHub App
Connect the GitHub App for the two things a deploy key cannot do: a repository picker, and the deployment’s status reported back onto the commit.
Dockerfile, Compose, or neither
A Compose file is used first, then a Dockerfile. A repository with neither but a recognised manifest is built with Nixpacks, run as a pinned container.
Rollback in one click
Every deployment records the image it produced and the commit that caused it. Rolling back re-applies a previous image with no rebuild, and the history keeps both entries.
Live build logs
Watch the build stream as it happens. Values from your configuration are scrubbed out of every line before it is stored or shown.
Monorepos welcome
Watch paths let one repository hold several applications, so a push deploys only the ones whose files changed.
In detail
- Push webhooks from GitHub, GitLab, Bitbucket, or a generic sender, each checked against an HMAC signature before any work starts.
- Prefer not to connect anything? Upload a ZIP of your source instead.
- Deploys recreate by default. Blue/green is an opt-in per application, gated on a free-memory check so a small box is never pushed over.
- Host keys are trusted on first use and pinned afterwards: a Git host whose key changes makes the next clone fail loudly.
- Deploy keys and webhook secrets are stored encrypted and never returned by any endpoint; a webhook secret is shown once, when you generate it.
- Named volumes, resource limits, and the number of images kept for rollback are set per application.
- The deployment history filters by application, project, environment, server, status, trigger, and date.
Works well with
Domains and HTTPS
Add a hostname, create the record it shows you, and HTTPS arrives on its own.
Environment variables
Encrypted, write-only configuration that never touches the disk.
Alerts
Alerts that open and resolve themselves — in the portal, email, webhook, or Telegram.
Your server is ready when you are
Create an account, connect a VPS, and ship your first application.