Plexivo Kubernetes

Apply your manifests with kubectl in your own namespace; Plexivo runs the cluster and bills what your pods use.

Plexivo Kubernetes gives you a namespace of your own on a cluster Plexivo runs. You bring Deployments, StatefulSets, Jobs, Services and Ingresses, and apply them from the console or with kubectl. You never size, patch or pay for servers: you pay for what your running pods request, by the hour.

Create a workloadA container in a few fields, or your own YAML, Helm chart or Git folder. Use kubectlA short-lived kubeconfig for your namespace. Manifests and limitsWhat you can run, and the few rules it follows. BillingWhat your pods request, hour by hour.

What you get#

A workload: your namespace, with the CPU, memory and storage each pod may request and how many pods it may run.
Isolation: every pod runs in its own sandbox. Other customers can never reach your namespace, and your pods cannot reach theirs.
HTTPS: workloads are private until their manifests include an Ingress. Plexivo then serves it over HTTPS with a certificate it issues and renews.
Autoscaling: a HorizontalPodAutoscaler scales your pods within the workload’s maximum.
Your data: connect Plexivo Postgres, Plexivo MySQL and Plexivo Cache, and attach Plexivo Secrets, from the console.
Live view: CPU, memory and storage in use against what your pods request, every controller and pod, events and pod logs.

Plans and limits#

Plexivo Kubernetes is included from the Startup plan.

	Startup	Business	Enterprise
Workloads per organisation	2	8	Set in your contract

These are the defaults; your own limits are in Settings → Limits & quotas. Every workload, on every plan, can have:

up to 50 pods;
up to 16 vCPU and 64 GB of memory per pod;
up to 500 GB of persistent storage.

The total vCPU and memory of everything in your organisation is held to your plan, too.

Billing at a glance#

Each hour, Plexivo reads your running pods and prices the vCPU and memory they request, a small amount per pod, and the storage they use. Each day’s total comes from your wallet once the day ends. A workload scaled to zero costs nothing that hour. See Billing.

For developers If you have one container and want an HTTPS address, Plexivo App Runner needs no YAML at all. Choose Plexivo Kubernetes when you already have manifests or a Helm chart, or need StatefulSets, Jobs and CronJobs.

Next steps#

Create a workloadYour first deploy, step by step. Pods and scalingRequested capacity and autoscaling.

Updated 27 October 2026