Push to deploy
Every push to your chosen branch queues a release. No pipelines to write, no runners to babysit.
BreezeCloud connects to your GitHub repository, builds every push into a container image, and rolls it out. If a release fails, the last good one keeps serving.
Sign in with GitHub.
Builds what you already have
Why BreezeCloud
You bring the repository. We take care of images, manifests, databases, cache, and secrets so every deploy looks the same. Apps run as standard Kubernetes workloads.
Every push to your chosen branch queues a release. No pipelines to write, no runners to babysit.
A failed release never replaces a healthy one. Config vars are encrypted at rest, and connection strings stay masked.
Attach Postgres or Breeze Cache to any app. Connection URLs land in the next deploy as DATABASE_URL and VALKEY_URL.
How it works
The same path for a weekend project and a production service.
Name your app and point it at a GitHub repository and branch. The app name becomes its hostname.
We detect your stack — a Dockerfile, buildpacks, or Node frameworks — and build a container image on every push.
The release rolls out to your app's URL. Watch it in the console, with full release history per app.
Features
GitHub push webhooks queue releases for the exact commit. Deploy the branch tip on demand from the console.
Dockerfile when you have one, Cloud Native Buildpacks when you don't, and first-class Next.js, Nuxt, and Astro.
One database per app on its own server. Detach without losing data; destroy only after a dump succeeds.
Secrets are encrypted at rest and reach your app, release command, and builds. Changes redeploy automatically.
A Redis-compatible instance for the workspace. Attach it to inject VALKEY_URL and REDIS_URL.
Point your hostname at the app. We show the DNS records and issue the certificate. It renews on its own.
Connect a repository and have a live URL before your coffee gets cold.