Introduction
Deploys.app is a container platform-as-a-service. You bring a container image; it runs, routes, scales, and bills it — on managed Kubernetes you never have to touch.
What Deploys.app does#
Deploys.app turns a container image into a running, internet-reachable service without asking you to operate a cluster. You hand it an image and a little configuration — CPU, memory, port, environment — and the platform takes care of scheduling, rollout, TLS certificates, routing, autoscaling, logging, metrics, and usage-based billing.
It is built on Kubernetes, but Kubernetes never leaks into your day. There are no nodes to patch, no ingress controllers to wire up, no manifests to template. The unit you work with is the deployment, not the pod.
Who it’s for#
- Developers ship and observe their apps — deploy an image, read logs, watch metrics, roll back a bad release.
- Platform / DevOps engineers manage the surrounding infrastructure — domains, routing, disks, registries, roles, and billing.
- Project owners manage membership and project-level settings.
- Automated systems deploy on behalf of humans through the REST API or the GitHub Action, authenticating as a service account.
How work is organized#
Everything you create lives inside a project — a workspace that groups your deployments and the resources they depend on. Within a project you run deployments, attach domains and routes, mount disks, and store images in a private registry.
Access is governed by roles with granular permissions, so each member — human or machine — sees and changes only what they should. Costs roll up to a billing account that can span several projects.
gke.cluster-rcf2. You pick a location per deployment, and your public hostname
inherits that location’s domain suffix.What you can run#
| Workload | Use it for |
|---|---|
| Web service | Internet-facing HTTP apps and APIs, with autoscaling and a managed hostname. |
| Worker | Long-running background processes with no inbound traffic. |
| Scheduled job | Cron-style tasks that run on a schedule and exit. |
| TCP service | Non-HTTP protocols, exposed internally or externally. |
See Deployment types for the full breakdown.
Three ways to drive it#
You can operate Deploys.app however fits your workflow — the console,
the deploys CLI, and the REST API all
speak to the same backend and the same set of functions.