Compute
Containers on infrastructure that stays in Indonesia.
Deploy an image into a namespace and let the platform place it. The same console, quotas and audit trail whether the capacity is ours or yours.
Workloads
Deploy from a registry
Give it an image, a command and an environment. The platform schedules it onto a cluster and holds it there.
Reach it over HTTPS or SSH
A workload can take a public HTTP endpoint, or a shell session for the times a log line is not enough.
Watch what it costs
Usage meters against your balance while the workload runs, per machine type, visible in the console rather than at the end of the month.
Two ways to get a cluster.
Both are managed the same way. The difference is whose hardware it runs on, and that is a procurement decision rather than a technical one.
Capacity we operate
The Batam campus, once it is serving. You get a namespace on it and never see the cluster itself.
A cluster you already run
Register your own Kubernetes cluster and use the same console, quotas and audit trail across both.
A registered cluster keeps its credentials encrypted at rest and is reachable either by the platform dialling it or by an agent inside it dialling out — for clusters with no inbound route. How that is secured.
What we will not put on this page.
GPU models, node counts and interconnect topology, until the campus is serving them. Those numbers move while a datacentre is being built, and publishing a forecast as a specification is how buyers end up planning against something that was never committed. Ask us and you will get the current state, including the parts that are not ready.
Ask what is available