Managed Kubernetes. Up in 2 to 5 minutes.

A managed control plane with ingress and certificates already running. You pay for worker nodes only.

Nodes from $0.024 an hourControl plane included⁠[1]

On your own devices or ours, inside your private cloud's own network. Billed by the hour, no minimum term.

What you get

Four things to know.

  • Microservices
  • SaaS back ends
  • CI runners
  • Stateless APIs
  • Up in 2 to 5 minutes

    New nodes join in 1 to 2 minutes. Scale a node pool up or down over the API.

  • Ingress and certificates included

    NGINX ingress and Let’s Encrypt renewal run from day one. Point a CNAME and ship.

  • Bring a cluster you already run

    Import registers it from its kubeconfig. It stays where it is.

  • Conformance, 428 of 428 tests

    Standard Kubernetes, not a fork. kubectl works as it does anywhere.

Price

Worker node rate card

SizevCPUMemoryNVMePer hour
dc2.small24 GB50 GB$0.024
dc2.medium48 GB100 GB$0.048
dc2.large816 GB200 GB$0.096
dc2.xlarge1632 GB400 GB$0.192
dc2.2xlarge3264 GB800 GB$0.384
dc2.4xlarge64128 GB1.6 TB$0.768

No control-plane line on the bill. The default two-node cluster runs about $35 a month.⁠[1]

Not yet
  • Persistent volumes are not yet documented: keep state in managed databases or object storage.
  • Node pool autoscaling is not yet on.
  • Ingress routes HTTP; TCP and UDP load balancers are not yet offered.
Where it runs

On our nodes or your own devices, inside your private cloud's own network. If a node fails, work moves across the network under the policy you set.

The four tiers and the price index

Get started

Start on the free tier today.

Or talk to Triple X about running it on your own devices.

  1. 01

    Join the waitlist.

    Tell us what you want to run and where. No credit card.

    TakesTwo minutes

  2. 02

    Create a cluster.

    Two nodes by default. kubectl works as it does anywhere.

    Takes2 to 5 minutes

  3. 03

    Bring your own servers.

    Triple X sets up your private cloud on them.

    WhoTriple X

We never ask for your root credentials, API keys or bank details by email.

All products

At a glance

The numbers a buyer asks for.

Timings, prices and standards for a managed cluster, each with where to check.

WhatTriple X CloudWhere to verify
Cluster up2 to 5 minutesDocs, August 1, 2026
New node joins1 to 2 minutesDocs, node groups
Control planeIncluded; no line on the billPricing page
Worker nodeFrom $0.024 an hourRate card, docs
Default two-node clusterAbout $35 a monthPricing page
Conformance428 of 428 tests on v1.34.0CNCF listing, in progress
IngressNGINX and Let's Encrypt includedDocs, ingress
Bring your own clusterImport from its kubeconfigDocs, cluster import
Exit costTransfer from $0.01 per GB, no feePricing page and your contract

Questions

What buyers ask before they sign.

In the order they come up. Every answer ends with where to check it.

Show questions about

10 answers

All questions
Is it standard Kubernetes?

Yes. The platform passed 428 of 428 conformance tests on v1.34.0, and the public CNCF listing is in progress. kubectl, Helm and your manifests work as they do anywhere. It is not a fork.

Proofthe conformance run, listing with CNCF in progress.⁠[2]

What does a cluster cost?

You pay for worker nodes only, from $0.024 an hour each, on the same six sizes as virtual machines. There is no control-plane line on the bill. The default two-node cluster runs about $35 a month.

Proofthe worker node rate card and the no-control-plane rule in the documentation, August 1, 2026.⁠[1]

What does it cost to leave?

Outbound transfer from $0.01 per GB and nothing else. Your manifests, Helm charts and images are standard, so they apply to any conformant cluster. No exit fee, no minimum term.

Proofthe transfer bands in the published pricing and the no-exit-fee clause in your contract.⁠[3]

Who can see what runs in my cluster?

You and the people you add. The platform underneath sees that nodes exist, their size and their cost, not the contents of your pods. Cluster traffic stays inside your private cloud's own network unless you publish an ingress route.

Proofthe access table on the Security page and the SOC 2 Type II report under NDA.⁠[4]

Can worker nodes be my own servers?

Yes. Devices you own join your private cloud and take work from the managed control plane. You can also import a cluster you already run; it stays where it is. Triple X quotes the platform charge in writing.

Proofthe cluster import guide in the documentation and a written quote from Triple X.⁠[1]

Where does the control plane run?

On the platform underneath, inside your private cloud, in the region you pick at launch. Worker nodes run where you place them, hosted or on your devices. There is no published region list; the CLI returns the live one.

Proofthe create-cluster flow in the documentation, August 1, 2026.⁠[1]

What happens when a node fails?

Pods reschedule onto the remaining nodes, and the node itself is replaced under the policy you set, inside your private cloud first. Keep state in managed databases or object storage, because persistent volumes are not yet documented.

Proofthe failover rules on the Reliability page and the node group guide in the documentation.⁠[1]

How fast can I be running?

A new cluster reaches Running in 2 to 5 minutes. New nodes join in 1 to 2 minutes. NGINX ingress and Let's Encrypt renewal run from day one, so a CNAME is all a public service needs.

Proofthe timings in the create-cluster guide, August 1, 2026.⁠[1]

What do I need on my side?

An account, kubectl and your kubeconfig. Starter accounts begin with 2 clusters and 8 cores; increases are reviewed in 1 to 2 business days. A private registry for your images is a separate product in the same private cloud.

Proofthe account limits in the published pricing, August 1, 2026.⁠[3]

What is not included yet?

Persistent volumes are not yet documented. Node pool autoscaling is not yet on. Ingress routes HTTP; TCP and UDP load balancers are not yet offered. There is no Terraform provider; use the CLI or the SDKs.

Proofthe Not yet list on this page and the Developers page, checked October 2026.