Managed Kubernetes

A Kubernetes cluster,
without renting a Kubernetes cluster.

You get a kubeconfig, you run kubectl, you deploy. That's it. No proprietary console to learn. No months of onboarding. No surprise bill.

See pricing How it works →
Hosting
Finland · EU
Isolation
Capsule + per-tenant RBAC
Audit
Every mutation logged
TLS
Let's Encrypt, built in

Who is it for?

ho.ma is for teams where running your own K8s cluster is too much, and an opinionated PaaS is not enough.

Solo makers & small teams

You want kubectl apply without babysitting a control plane, and without a provider charging you for every idle hour.

Sandboxes & prototypes

A stable Kubernetes environment to test, demo and run POCs, without going through corporate ops.

Workloads that must stay in the EU

European hosting, run by a French company, with no operational dependency on a US cloud.

Pricing

You pay for what actually runs: only the resources in use. No subscription, no commitment, no tier to pick blind. A running pod is metered by the minute; nothing running → compute is 0 €, and you only pay a small space fee for as long as your tenant exists. Delete it → 0 €, immediately.

Resource Price excl. VAT
vCPU
Metered on the CPU your pods actually burn — a running but idle pod ≈ 0		0.010 € / vCPU·h
Memory
Metered on memory actually in use (working set)		0.004 € / GiB·h
Persistent storage
Longhorn volumes, snapshots included		0,0002 € / GiB·h
Space (namespace)
For as long as your tenant exists. Delete it → 0 €.		0.002 € / namespace·h

No hidden costs: no bill for network traffic, no bill for API requests, no egress fees. Details in the FAQ.

You set the cap — budget guardrail

No tiers. You pay for real usage, and you set a resource cap when you create the tenant — adjustable any time. You will never be billed beyond it.

Example cap
vCPU2
Memory4 GiB
Storage20 GiB

Monthly ceiling: ~29 € excl. VAT if everything runs 24/7.

Idle, it drops towards 0 € — you only pay for what really runs.

In every tenant
  • ✓ Isolated namespace(s), Capsule + RBAC
  • ✓ Self-service kubeconfig, kubectl straight to the API
  • ✓ Full audit log
  • ✓ Longhorn persistent storage + snapshots
  • ✓ Usage-based billing, adjustable cap
Create my tenant

So how does the billing actually work?

  • ⏱️ We measure what runs, sampled every minute: the resources of your active pods + storage. Nothing running → 0 €.
  • 🔧 It follows your activity in real time: start a pod, the meter goes up; stop it, the meter stops.
  • 🛑 Delete your tenant and everything stops — the bill only ever reflects what really ran.
  • 📅 Automatic charge every Monday morning, on the card on file, for the past week's usage. The per-resource breakdown is visible at any time.
  • 💸 No surprises: check the running total with homa tenant usage <your-tenant> or from your account area.

Need a cap above the default limits, or dedicated isolation? Let's talk.

How it works

No magic, no black box

The pipeline that hands you access is documented, scriptable, verifiable.

01 · PROVISIONING

Capsule isolates your tenant

We create a Capsule Tenant bound to your identity, with a namespace, quotas and a RoleBinding. You can't see what isn't yours.

02 · ACCESS

Kubeconfig, direct

You download your kubeconfig (short-lived token, stable ServiceAccount). Your kubectl talks straight to the Kubernetes API over valid TLS. No tunnel, no proprietary plugin.

03 · OPERATION

Everything is audited

Every mutation, every secret read is logged server-side. You can ask for your audit logs at any time.

$ kubectl --kubeconfig=my-tenant.kubeconfig get pods
NAME                          READY   STATUS    RESTARTS   AGE
my-app-7d8c9b6f-xz4qr         1/1     Running   0          12m
my-worker-5d4f7c8b-jk3lt      1/1     Running   0          12m
$ kubectl apply -f deployment.yaml
deployment.apps/my-new-service created

Common questions

Is my code isolated from other customers?

Yes. Namespace isolation through Capsule, per-tenant RBAC, and a ResourceQuota that stops your workload from starving the neighbours. Verifiable server-side through the admission webhooks.

What happens to my code if I leave?

You get a dump of your configmaps + secrets + manifests (kubectl get -o yaml across your whole tenant) and a tarball dump of your PVCs. Then everything is deleted. No hidden retention.

SLA, downtime, support?

ho.ma is run by one person (Vincent). No contractual SLA at this early stage. Maintenance announced by email 48 h in advance. Support by email, target response within 24 business hours.

Why not just use Hetzner / DigitalOcean / Scaleway?

Because there you pay for a whole cluster — control plane, nodes, load balancer — even if you use 5 % of it. And you carry the ops work yourself. ho.ma shares one cluster between tenants that don't need a whole one.

How does pay-as-you-go work in practice?

Every minute we sample what your tenant really consumes: CPU actually burned, memory in use (working set), plus provisioned storage. We integrate that over time; every Monday we charge the past week × published rates. A pod that is up but idle consumes almost nothing — so you pay almost nothing.

Concrete examples:

  • 2 vCPU + 4 GiB + 20 GiB running non-stop for a month (730 h) ≈ 29 € excl. VAT (+ 1.46 € of space).
  • The same pods active 8 h per business day (≈ 176 h) ≈ 7 € excl. VAT (+ space).
  • Tenant created but nothing started: you only pay for space (~1.46 €/month); deleted → 0 €.
Which payment methods do you take?

Card via Stripe: you register a card (0 € authorisation) when you create the tenant, then an automatic charge every Monday for the past week's usage. Invoiced by Ephais SAS, based in France.

Want to try it?

Pick a config, register a card, grab your kubeconfig. All self-service, done in a few minutes — pay for what you use, no commitment.

Create my tenant