A shared Kubernetes platform, with access and cost per team.
Broad permissions, a cost nobody can split and versions that expire every year. We design a shared Kubernetes platform, with access and cost per team defined in advance, and hand it over to you.
01 · Situation
Self-check
Tick the situations that apply to your company. Your selection stays in your browser: no data is sent.
Tick those that apply to your company.
Schedule a call02 · Why now
Dates worth keeping in mind
Official sources from the Kubernetes project and the EU. Follow each source to check them.
Each Kubernetes version gets about 14 months of support
After that, no patches. Upgrading once or twice a year is not optional: either it is a process, or it is a scare.
Source: kubernetes.io, Patch Releases · Every yearingress-nginx retirement
The most widely used ingress controller stopped receiving releases and security fixes. If your cluster uses it, the replacement needs planning.
Source: Blog oficial de Kubernetes · Mar 2026Cyber Resilience: reporting exploited vulnerabilities
If you sell software or products with digital elements in the EU, you must report actively exploited vulnerabilities. Without a pipeline that knows what is inside, that is hard.
Source: Reglamento (UE) 2024/2847, Cyber Resilience Act · 11 Sep 2026
03 · What changes
What changes when the platform is defined
Today: Every team, its own way.
With Nubyron: One pull-request deployment template for everyone.
Today: Everyone is an admin.
With Nubyron: Isolation and permissions per team, defined in advance.
Today: The cost belongs to everyone and no one.
With Nubyron: Tagging and a cost model to split it by team.
Today: A new team takes weeks.
With Nubyron: A step-by-step onboarding guide.
04 · What you receive
What we deliver
A fixed project, in a test environment of yours. This is what you take away:
- Architecture and decisions in writing
For your cloud’s managed Kubernetes: environments, team isolation, security and minimum observability.
- Reference code and GitOps
Infrastructure as code and a pipeline template with pull-request deployment.
- Onboarding guide
So a new team starts deploying without depending on anyone.
- Cost model per team
With explicit assumptions and tagging to split the spend.
- Handover to your team
The platform is yours: you run it, with us if you want.
05 · The seven areas
Seven areas, one focus
Kubernetes that is well designed, deployed and maintained on AKS, EKS or GKE.
Kubernetes platform design
Platform and cluster architecture shaped around how you work.
Multi-environment, networking, identity and multi-tenancy.
Deployment and workload migration
We bring your applications to Kubernetes, including from virtual machines or standalone containers.
Manifests, Helm, Kustomize, release strategies and migration of virtual machines and standalone containers to Kubernetes.
GitOps
The state of your environments in Git and under control.
Argo CD or Flux, environments as code and promotion between environments.
SRE and observability
Know what is happening in your cluster and be ready for when something fails.
SLI/SLO, autoscaling, observability, alerts, runbooks, backups and recovery.
Kubernetes security
Smaller attack surface and clearer access in the cluster and the delivery chain.
RBAC, policies, secrets, supply chain and hardening against the CIS Kubernetes guidance.
Related guide: Kubernetes security: why a “secure” cluster still lets the important things through, and how to audit it on AKS, EKS and GKE
Kubernetes upgrades
Updating without it being a gamble.
Versions, deprecated APIs and agreed windows.
Related guide: Kubernetes upgrades on AKS, EKS and GKE: what breaks and what to check first
Cluster cost optimization
Understand and tune what your Kubernetes costs.
Sizing, bin packing, spot and cost per team or per cluster service.
06 · How we work
How we work, step by step
- We understand your teams
We analyse how each team deploys today and what the platform requires.
- We design
Architecture and decisions (ADRs): environments, isolation, access and per-team cost.
- We test
Reference code and pipeline in a test environment of yours.
- We hand over
We document and explain the design to the people who will maintain the platform: your team or, if you engage us, ours.
07 · Other services
Complementary services
08 · Further reading
Recommended reading
- PLATFORM ENGINEERINGPlatform engineering: why your development teams need it
- KUBERNETES & SREKubernetes shouldn't give you mini-heart attacks
09 · FAQ
Frequently asked questions
Do we really need Kubernetes?
If you have few services and a single team, maybe not. We tell you on the first call before proposing anything.
Does it work with our cloud?
Yes: with AKS (Azure), EKS (AWS) and GKE (Google Cloud), and with plain Kubernetes. It is designed for the one you use.
Who maintains it afterwards?
Your team, with the documentation and the guide, or us: we run clusters (SRE and observability, upgrades and cluster cost) with the scope agreed in writing before we start, in agreed hours and with no on-call cover or SLA.
Do you run the platform afterwards?
Yes, if you engage us: besides designing and deploying it, we run clusters (SRE and observability, upgrades and cluster cost). Scope and hours are agreed in writing before we start. You can also run it yourself with your team.
What is a Kubernetes platform for teams?
A shared base where teams deploy through a common path, with isolation, security and per-team cost defined in advance.
Do we need Kubernetes?
Not always. With few applications a simpler managed service is enough. If it does not pay off, we tell you.
No 24x7 on-call or SLA · No zero-risk claims · No guaranteed savings · No testing without permission. See everything we do not promise →
Shall we talk about Kubernetes platforms for teams?
30 minutes with a technical member of the team. We review what you ticked, tell you where we would start and what can wait. No preparation is needed.
First step
Tell us about your case
Write to us about your environment and your question in general terms. We propose a written scope before any work begins.
- A technical person repliesYour message is reviewed by a technical specialist.
- Scope in writing before we startWhat is included, what is not and what it costs. You decide with the proposal in writing.
- Your data, only to reply to youNo advertising unless you agree.
Prefer to talk?
Talk to us for 30 minutes