Portable OCI images
Pin any compatible public or private-registry image reference and its start command.
A template is a private, reusable workload definition: Docker image, start command, container disk, local volume, mount path, exposed ports and non-secret environment variables.
Transparent baseline
No extra fee
template records are workspace-scoped
Pod
GPU and cluster mode
Serverless
Worker mode
3
NVIDIA · AMD · CPU
Why GPURento
Pin any compatible public or private-registry image reference and its start command.
Save disk sizes, mount path, HTTP/TCP ports and non-sensitive environment settings.
Reuse one Pod template when creating clusters so every node starts from the same image.
From code to capacity
Choose workload type
Create a GPU Pod / Cluster template or a Serverless worker template.
Save the runtime
Enter image, command, disks, ports and non-secret environment variables.
Reuse and update
Select the template during cluster creation, edit it later or delete it without removing existing resources.
await fetch("/api/templates", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
name: "pytorch-workspace",
workloadType: "pod",
category: "NVIDIA",
image: "pytorch/pytorch:2.6.0-cuda12.6-cudnn9-runtime",
startCommand: "sleep infinity",
containerDiskGb: 50,
volumeGb: 100,
volumeMountPath: "/workspace",
ports: "8888/http\n22/tcp",
environmentVariables: "NCCL_DEBUG=INFO"
})
})Included
Every workload gets the same API, identity, billing and observability layer.
Configure resources directly in the dashboard. Prepaid usage uses wallet credit; monthly rentals have a separate checkout.
No. A template stores a reusable configuration. Compute is allocated only when a resource is created from it.
No. The environment field is for non-sensitive values only. Passwords, private keys and API tokens need a dedicated secret store.
Yes. Pod templates appear in the cluster creation form and provide the image used by every node.
Ready when you are