One builder per build. No queues, no blocked teams, no QEMU.
Zeus runs dedicated build machines — on AWS, GCP, or your own hardware — one per concurrent build. The API build isn't waiting behind the frontend. ARM64 isn't waiting behind x86. Builds that used to block each other don't anymore.
Build infrastructure that matches how you actually ship.
Most CI systems give you a shared queue and call it a day. If your frontend build takes 12 minutes and your API needs to go out, it waits. Zeus gives you dedicated builders — one per concurrent build — so fast things don't wait for slow things and no single repo can starve the rest of your team.
Zeus builds natively for amd64 and arm64 in parallel on real hardware — not QEMU emulation. The same commit produces both architectures at once, at native speed. Built images go straight to Harbor for vulnerability scanning before any deploy is possible. From there, one action ships to a single cluster or every cluster you run.
| Repo | Branch / Commit | Arch | Duration | Status |
|---|---|---|---|---|
| api-gateway | a3f12c9 main | amd64 · arm64 | 1m 14s | Pushed · 2m |
| web-client | 7d4e1b0 main | amd64 | 62% | Building · now |
| worker | 9c1a55f main | arm64 | 0m 58s | Pushed · 14m |
| auth-service | b2e8d31 main | amd64 · arm64 | 1m 22s | Pushed · 31m |
| report-exporter | c9f1a44 main | amd64 | 0m 33s | Failed · 48m |
| image-processor | d7b3e10 release | amd64 · arm64 | 2m 01s | Pushed · 1h |
| scheduler | e4c2f88 main | amd64 | 0m 47s | Pushed · 2h |
From zero to running.
Connect GitHub
OAuth link to your repos. Zeus watches branches and builds on push. Tag conventions and pull secrets are handled automatically — nothing to configure per cluster.
Builders run in parallel
amd64 and arm64 build simultaneously on native hardware. Multiple services build at the same time — each on its own builder. No queue, no waiting for a slow build to free a runner.
Push to Harbor, scan with Trivy
Built images land in Harbor. Trivy vulnerability scans run automatically. An image that hasn't been scanned can't be promoted to production — the gate is enforced, not optional.
Promote and deploy globally
A scanned, tagged image can go to one environment or every cluster you run — EKS, GKE, k3s — in a single action. Watch the rollout live per cluster.
Built by people who run this in production.
No hand-waving. Here’s what’s actually under the hood: the kind of detail you’d expect from a platform you’re going to trust with production.
Questions you’d actually ask.
How many builds can run at once?
One per builder. Add a builder per service you want to keep unblocked, or run a shared pool. It's a simple model: more builders = more parallelism, with no queue configuration needed.
What happens if a spot instance is terminated mid-build?
Each builder has dedicated persistent storage that stays mounted across instances. When a spot is reclaimed, Zeus brings up a new instance and attaches the same volume — the build resumes from its cache rather than starting from scratch. You don't lose the layer cache, the intermediate artifacts, or the time already spent. Spot is the default precisely because the recovery is built in.
Is ARM64 actually native or just QEMU?
Native. Zeus provisions real arm64 instances — Graviton on AWS, Tau T2A on GCP, or your own arm64 Proxmox nodes — and builds directly on them. QEMU emulation is 4-10x slower and produces subtly different binaries. We don't use it.
Can I use my own hardware for builds?
Yes. If you're running Proxmox, Zeus can run builders on your own nodes at zero cloud compute cost. Switch to AWS or GCP builders for capacity bursts, or run a mix.
Does this replace GitHub Actions?
For the build-image-and-deploy path, yes. If you have test suites in Actions you want to keep, Zeus can consume the images they produce instead. Either way, multi-arch builds, Harbor scanning, and multi-cluster deploy come from one place.
What if an image has vulnerabilities?
Trivy flags it and the image is blocked from promotion. You see the CVEs in Zeus before anything reaches a cluster. You can configure severity thresholds — block on Critical only, or block on any High+.
Keep exploring.
All features →Where built images get deployed.
Explore →Follow every release.
Explore →Ship a build everywhere.
Explore →Start running it today.
Spin up your first cluster free, or get a guided tour from our team.