KaaS
Kubernetes, fully managed.
Production Kubernetes clusters from approved templates — deployed in minutes. A managed control plane, worker node groups you size yourself, autohealing and monitoring add-ons, and preflight checks before every launch. No control-plane babysitting, no upgrade weekends.
Managed control plane
Launch in minutes
Autohealing + monitoring
One-click kubeconfig
First control plane free for 30 days on new Kubernetes clusters — use code KUBE30
Kubernetes as a Service
Kubernetes clusters
Create and operate tenant clusters from approved templates.
Production · v1.30
nebula-lab
- Kubernetes
- v1.30
- Control plane
- standard-2
- Workers
- 3 × medium
- Created
- 2d ago
Standard · v1.29
atlas-staging
- Kubernetes
- v1.29
- Control plane
- standard-2
- Workers
- 2 × small
- Created
- 9d ago
Production · v1.30
orion-batch
- Kubernetes
- v1.30
- Control plane
- standard-4
- Workers
- 5 × large
- Created
- just now
Recent activity
- Provisioning orion-batch · reconciling node groups
- Resized nebula-lab workers to 3 × medium
- Cluster atlas-staging reached Ready
Kubernetes create
Create Kubernetes cluster
Choose a template, size the topology, review preflight, and launch.
Template and intent
Name the cluster and choose an approved template.
Production Kubernetes
v1.30- Control plane
- standard-2
- Node size
- medium
Standard Kubernetes
v1.29- Control plane
- standard-2
- Node size
- small
Topology and size
Control plane and worker node groups.
Fixedworkers
- Node size
- medium
- Number of nodes
- 3
Add node groups to mix machine sizes. Autoscaling node groups arrive next release.
Add-ons and access
Enable the essential services.
AutohealingEnabled
MonitoringEnabled
IngressOptional
Kubeconfig is generated once the cluster is provisioned — download it from the cluster page.
Schedule and cost
Preflight estimates resources before launch.
Worker capacity3 machines
Quota estimate8 vCPU · 24 GB
Wallet checkReady
Expiration scheduling is feature-gated and validated again server-side.
Review and launch
Confirm the request summary.
Namenebula-lab
TemplateProduction · v1.30
Workers3 × medium
Add-onsAutohealing + monitoring
Ready to launch
Create your real Kubernetes cluster in WECORE Hub
This page is an interactive product preview. Open hub.wecore.ir to provision and manage a live cluster.
99.95%
Control-plane SLA
5-step
Guided create wizard
v1.30
Latest Kubernetes
24/7
Engineers on call
Your clusters, production-ready.
Three pillars of a managed Kubernetes platform
01
Managed
Control Plane
A highly available, version-pinned Kubernetes control plane managed end to end. Catalog-approved templates lock in supported versions; we run etcd, API server, scheduler, and orchestrate upgrades with no tenant downtime.
Learn more →02
Elastic
Worker Node Groups
Size fixed worker node groups by name, machine size, and desired count — or mix several groups for heterogeneous workloads. Resize from the dashboard; autoscaling node groups land next release.
Learn more →03
Built-in
Add-ons & Access
Autohealing and monitoring ship as one-click add-ons, with ingress on the roadmap. Download a scoped kubeconfig the moment provisioning finishes — no manual certificate wrangling.
Learn more →Why engineering teams choose Kubernetes-as-a-Service
The power of Kubernetes without the operational tax of running it yourself
No control-plane ops
We run, patch, and upgrade etcd and the control plane. You never page yourself at 3am for a failed API server — the managed control plane carries a 99.95% SLA.
Approved templates only
Every cluster starts from a catalog-approved template, so Kubernetes versions, control-plane sizes, and worker defaults are always supported and security-reviewed.
Preflight before launch
Catalog, quota, wallet, and runtime health are checked before any cluster is created. You see resource and cost estimates up front — no surprise capacity failures mid-provision.
Node groups you control
Add, duplicate, resize, and remove worker node groups by name, machine size, and count. Run one group or several — your topology, validated server-side on every change.
Autohealing by default
Unhealthy nodes are repaired automatically when the template supports it. Pair it with built-in monitoring to keep workloads online without manual intervention.
One-click kubeconfig
A scoped, refresh-safe kubeconfig is generated as soon as the cluster is ready. Download it, point kubectl, and ship — credentials never touch your draft.
Create workflow
From template to running cluster in five guided steps
The same workflow you see in the live demo above — every field validated server-side before a single resource is provisioned
1 · Template
Name the cluster and pick an approved template. Versions and control-plane sizes come straight from the catalog.
2 · Topology
Choose the control-plane size and define fixed worker node groups — name, machine size, and desired count.
3 · Add-ons & Access
Toggle autohealing and monitoring. Kubeconfig access is generated automatically once the cluster is live.
4 · Schedule & Cost
Preflight estimates worker capacity, quota, and wallet readiness before you commit to a launch.
5 · Review & Launch
Confirm the immutable summary, acknowledge, and launch. Success appears in activity and opens a refresh-safe details page.
Live dashboard
Track Total, Ready, Reconciling, and Failed clusters with auto-refreshing status while long operations reconcile.
Status projection
Pending, Reconciling, Upgrading, Ready, Deleting, and Needs-attention states stream into the inventory and activity feed.
Resize & repair
Resize node groups and let autohealing repair unhealthy nodes — operations land in the activity timeline as they happen.
Side-by-side with our other products
Every WECORE product serves a different workload pattern
| Plan type | Best for | Infrastructure | Orchestration | Billing |
|---|---|---|---|---|
| KaaS Managed Kubernetes |
Microservices, CI/CD, web platforms, container workloads, autoscaling apps | Managed control plane + worker node groups | Kubernetes, templated & preflighted | Per cluster + nodes |
| CaaS | SaaS hosting, compliance, dev/staging, big data, VMware migration | Dedicated bare metal, single tenant | OpenStack + Ceph | Fixed monthly |
| Cloud HPC | Scientific compute, simulations, research, batch jobs | Slurm-managed bare metal | Slurm scheduler | Hourly, pay-per-node |
FAQ
Kubernetes questions, answered
What KaaS is, how the create wizard works, and what you operate vs. what we run
KaaS delivers managed, multi-tenant Kubernetes clusters created from approved templates. You get a highly available managed control plane, worker node groups you size yourself, autohealing and monitoring add-ons, and a one-click kubeconfig. We run the control plane and orchestrate upgrades; you run your workloads.
Through a 5-step guided wizard: ① choose a template, ② size the control plane and worker node groups, ③ enable add-ons (autohealing, monitoring) and access, ④ review the schedule and cost/quota estimate, and ⑤ confirm and launch. Every step is validated again server-side, and preflight runs before any resource is provisioned. You can try the full flow in the live demo above.
Yes. You define worker node groups by name, machine size, and desired count, and resize them from the dashboard at any time. Release 1 supports fixed node groups (run one group or several); autoscaling node groups are on the roadmap for the next release.
WECORE manages: the Kubernetes control plane (etcd, API server, scheduler), version upgrades, node autohealing, and 24/7 monitoring and incident response. You manage: your workloads, namespaces, deployments, services, and the worker node group sizing. The managed control plane carries a 99.95% SLA.
A scoped kubeconfig is generated automatically the moment provisioning finishes. Download it from the cluster page, point kubectl at it, and you are ready to deploy. Credentials are never embedded in the create draft and the download is refresh-safe.
Autohealing (automatic repair of unhealthy nodes) and monitoring ship as one-click add-ons when the selected template supports them. Ingress is on the roadmap. Add-on availability is surfaced in the create wizard so you only see options the catalog actually supports.
Only catalog-approved, non-deprecated versions are offered — currently up to v1.30. Because every cluster starts from an approved template, you never run an unsupported or unreviewed version, and we orchestrate version upgrades with no tenant downtime.
The request is validated server-side, preflight confirms catalog, quota, wallet, and runtime health, and only then is the cluster provisioned. A successful launch appears in the activity feed and opens a refresh-safe details page where you can watch the cluster move from Reconciling to Ready in real time.
Ready to ship?
Launch your first Kubernetes cluster in minutes.
A managed control plane, worker node groups you control, autohealing and monitoring built in. Try the live demo, then create the real thing in WECORE Hub.