Ship QUESTPIE apps without owning the runway.
QUESTPIE Cloud is the deploy backend, build infrastructure, and customer surface for QUESTPIE projects. Connect a repo, get builds and digest-based rollouts on Kubernetes, and operate everything from one account.
deployments / production
api · 7e8c41a
Platform
Cloud owns the deploy lifecycle, end to end.
Target repos stay thin. Cloud builds, registers artifacts, applies runtime state through the Kubernetes API, and observes rollouts.
Cloud-owned deploys
Push to a configured branch. Cloud builds, pushes the image, applies Kubernetes desired state, and observes the rollout. Target repos stay clean.
Digest-based rollout
Cloud picks the production tag. Deploys identify themselves by image digest, so rollback reuses the exact artifact rather than re-running CI.
Kubernetes Apply Manager
Server-side dry-run, owner labels, namespace locks, and inventory-based pruning. Never `kubectl`, never blanket cluster admin.
Durable workflows
Build, provision, render, apply, and observe are workflow steps backed by Postgres + pg-boss. Process restarts resume in place.
Release flow
A push triggers a workflow, not a CI script.
Each step is durable, idempotent, and lives in Cloud DB. You can resume after a process restart, retry without re-running the whole pipeline, and roll back to any previous artifact.
Source
Connect a Git repo or push from the CLI.
Build
Cloud build executors (BuildKit, buildpacks, or Woodpecker bridge) produce an immutable image digest.
Apply
Render desired state from DB, dry-run, then server-side apply with owner labels.
Observe
Read pod and replica state. Mark deployed once health and digest match.
Ready when you are