Vertically integrated bare metal AI
Run Saturn Cloud on Spectro Cloud Palette
Palette handles the layers from BMC to Kubernetes: immutable OS builds with Canvos and Kairos, cluster lifecycle, and fleet management, all as one vendor-supported product. Saturn Cloud installs into the clusters Palette manages and gives tenants self-service workspaces, jobs, deployments, and per-tenant billing.
Why Spectro Cloud + Saturn Cloud
One vendor for the metal. One vendor for the platform.
Spectro Cloud is the rare project that owns provisioning, immutable OS, and cluster management as a single product. That makes the layer below Saturn Cloud straightforward: one API, one support contract. Saturn Cloud takes care of what tenants see and how you invoice them.
Bare metal to Kubernetes, one product
Palette uses Canvos to build Kairos-based immutable OS images, boots servers from them, enrolls the nodes, and assembles clusters via Cluster Profiles. Saturn Cloud lands on top via Helm and never has to think about the layer below.
Immutable OS, A/B upgrades
Kairos gives every node an immutable root filesystem. Upgrades replace the image instead of patching it in place. Tenants get servers that reboot fast, roll back cleanly, and never drift from the configuration they were built with.
Allocation ledger Palette already keeps
Saturn Cloud snapshots Palette's host inventory to bill tenants for the hardware they hold. Cluster-attached or standalone, the ledger is the same.
Tenant platform without a build-out
Self-service signup, AI workspaces, distributed training, model deployment, SSO, and per-tenant invoicing. Saturn Cloud provides all of that on top of Palette-managed clusters.
How it works
The Spectro Cloud + Saturn Cloud stack
Palette owns the stack from BMC to Kubernetes
Palette uses Canvos to produce Kairos images preloaded with its agent, boots physical servers from the image, registers them, and binds them to a cluster via Cluster Profiles. The result is a working Kubernetes cluster with no per-customer Terraform.
Saturn Cloud installs into Palette-managed clusters
Saturn Cloud deploys via Helm into clusters Palette provisions. Tenants get JupyterLab, VS Code, jobs, deployments, and SSO. The cluster details are abstracted away.
Allocation-based billing against Palette's host inventory
Saturn Cloud reads the Palette API on a fixed cadence to capture which host belongs to which tenant. That history is the audit trail behind every invoice. Standalone hosts, cluster-attached hosts, and storage all bill the same way.
Or run Palette in CAPI mode
Palette also supports Cluster API providers as an alternative to its Canvos/Kairos path. Saturn Cloud's integration is the same. The allocation ledger still comes from Palette.
What changes when you add Saturn Cloud
Palette gives you the stack. Saturn Cloud gives you the product.
| Palette alone | Palette + Saturn Cloud |
|---|---|
| Bare metal provisioned, OS built, clusters running | All of that, plus a tenant-facing portal customers log into |
| Cluster-level fleet view in Palette | Per-tenant view in Saturn Cloud, sliced the way tenants ask for it |
| No tenant signup or self-service workspace flow | Signup, payment, and first workspace running in minutes |
| Bring your own MLOps tools and YAML | JupyterLab, VS Code, jobs, deployments, experiment tracking out of the box |
| No tenant billing layer | Allocation-based invoices generated from Palette's host inventory |
| Operator emails tenants their kubeconfig | Tenants self-serve from the portal |