Getting Started¶
This walks through the shape of deploying your first workload on CheesyServe's managed SaaS. Exact screens may differ slightly as the portal evolves — the concepts below stay the same.
Closed beta
The SaaS is currently invite-only. Request access at cheesyserve.com or by emailing [email protected].
-
The top-level container for your application.
-
Isolated instances — e.g. staging and production — each with their own quotas and configuration.
-
Point at a container image and decide how it's reached.
-
Optional — attach your own domain, with HTTPS handled for you.
-
Metrics, logs, and rollback, right from the platform.
1. Create a project¶
A project is the top-level container for your application. Everything you deploy lives inside one.
2. Add an environment¶
Inside a project, create an environment — for example staging or production. Each environment gets its own isolated namespace, quotas, and configuration, so changes in one never affect another.
3. Deploy a workload¶
A workload is a running instance of a container image. To deploy one, you'll need:
- A container image, in any public or private registry.
- Any environment variables or configuration your application needs.
- How the workload should be reached — internal-only, or exposed publicly over HTTPS.
Private registries
If your registry requires authentication, CheesyServe can store the credentials for you — add them once and reuse them across workloads.
Once deployed, CheesyServe takes care of running, scaling, and keeping the workload healthy.
4. Add a custom domain (optional)¶
If your workload is publicly exposed, you can attach your own custom domain instead of using the platform's default one.
5. Watch it run¶
From the environment, you can view metrics and logs for your workload, and roll back to a previous release if something goes wrong.
Next¶
See Features for the full list of what's available today.