Containers
Run container images without operating schedulers yourself,scaling, routing, and upgrades included.
Why teams use it
Container instances with explicit compute, memory, and storage inputs.
The verified surface covers compute, memory, persistent storage, and replica count. Use it when you want container capacity modeled clearly before runtime behavior is described elsewhere.
Built like infrastructure, priced like infrastructure.
The verified local services currently show pricing inputs for vCPU, memory, replica count, storage, and registry storage. Tower Registry is verified separately as a Nexus-backed registry with pull-secret integration.
Verified surface
Container capacity is shown without adding unlisted runtime behavior.
Container pages show what is present today: pricing services for compute, memory, replica count, and persistent storage.
Compute, memory, replica count, and storage are represented in pricing services.
vCPU, memory, and replica count define the container capacity envelope.
Attached storage is modeled as a separate billable input.
Provisioning, health checks, rolling updates, and load balancing are intentionally not shown on this page today.
What you get on Day One
Verified today: pricing inputs and registry integration.
Pricing model
Compute, memory, replica count, storage, and registry storage are represented in pricing services.
Registry integration
Tower Registry supports hosted Docker repositories and Kubernetes pull secrets.
Persistent storage
Persistent storage is modeled as a billable input alongside compute, memory, replica count, and registry capacity.
Runtime status
Container runtime provisioning, health checks, rolling updates, and load balancing require implementation evidence before they should be visualized.
Configuration & Platform Details
A concise map of currently verified Container Instances evidence.
Platform specifications
- Runtime evidence
- A runtime provisioner was not found in the local Desktop service repositories during this audit, so runtime behavior is not shown as a verified capability.
- Compute pricing
- The pricing calculator supports Container Instances compute with vCPU and replica counts.
- Memory pricing
- The pricing calculator supports memory usage multiplied by replica count.
- Storage pricing
- The pricing calculator includes Container Instances storage as a billable input.
- Registry integration
- Tower Registry provisioning is verified separately through the Nexus-backed registry service and Kubernetes dockerconfigjson pull secret creation.
Pricing
Loading SKUs...