
Mamori · Kubernetes consulting & ongoing support
Kubernetes consulting: senior expertise without a full-time hire
Mamori supports your platform team for the long run: Kubernetes architecture, operations, GitOps, observability, security and compliance. Personal, vendor-independent and with clearly agreed response times.
10 years of Kubernetes · 11 years of containers · 14 years of Linux
Sound familiar?
Your team is fighting on too many fronts at once
Kubernetes, CI/CD, security, compliance. Complexity keeps growing, but the expertise on the team does not keep pace.
Missing expertise
Kubernetes knowledge sits with one person. Specialists are nearly impossible to hire. Every architecture decision becomes a risk.
Expensive trial and error
Without experienced guidance, infrastructure mistakes cost weeks. A full-time senior hire is hard to find, and no guidance at all is risky.
Compliance pressure
BSI-Grundschutz, NIS2, GDPR: requirements grow faster than your platform. Internal teams are overwhelmed by them.
What late-caught mistakes cost
Late mistakes are the most expensive mistakes
Independent industry reports show what is at stake.
of organizations reported misconfigurations in the past 12 months: the most common cause of security incidents, ahead of classic attacks.
full working days per year is what teams lose on average detecting and fixing Kubernetes issues.
is what one hour of downtime costs for over 90% of mid-size and large enterprises.
There is a better way.
The solution
Senior expertise on your team. Without a full-time hire.
Operations, responsibility and knowledge stay on your team. Mamori adds the missing senior experience, reviews decisions and supports you where uncertainty would otherwise lead to standstill or risk.
A single new hire usually closes only part of the competence gap. Mamori bundles architecture, platform, security and compliance experience into one ongoing engagement.
Direct access
Ticket system, chat and regular sparring sessions with senior engineers. No queue, no anonymous hotline.
Proactive support
Health checks, audits and strategic recommendations. Instead of waiting, we act before something goes wrong.
Enablement instead of dependency
Your team becomes more self-sufficient: we transfer knowledge, mentor junior engineers and gradually make ourselves obsolete.
Mamori is a fit if …
you run a production Kubernetes or container platform
your team needs recurring senior experience rather than one-off projects
you want to keep operations, responsibility and knowledge in-house
Mamori is not the right fit if …
you are looking for a fully managed service that takes over operations entirely
you need a one-off audit or project (our Kubernetes security audit or Shogun is a better fit for that)
How Mamori works
How Mamori works with your platform team
From kick-off to a steady routine: clear communication channels, reliable appointments, documented decisions.
Kick-off and ground rules
Goals and expectations, roles, communication channels and access are agreed together. From day one you know how the collaboration works.
Sparring, support and reviews
A steady routine of sparring sessions, ticket support and reviews. Your contact knows your environment and thinks ahead.
Reports, roadmap and knowledge transfer
Regular reports, documented decisions and a roadmap that makes your team more self-sufficient every month.
The first month: kick-off, assessment and first priorities. After that: a steady, plannable routine.
Covered stack
Kubernetes support for your entire DevOps stack
No hunting for specialists: from cluster to observability from a single source.
We support multi-cluster setups across dev, stage and prod: GitOps deployments with ArgoCD, autoscaling and self-healing, plus security policies aligned with BSI APP.4.4. Migrating from Ingress-NGINX to the Gateway API, moving clusters to new versions and running architecture reviews ahead of critical deprecations are part of it too.
As ongoing Kubernetes support, we stay with your platform team from migration to stable day-2 operations. That gives the team predictable operations with fewer false alarms, while operations remain in your hands.
Mamori is not an anonymous helpdesk. You work with engineers who know your platform and support your decisions.
Want your team to apply Gateway API confidently? The Kubernetes Gateway API training combines the resource model, controller comparison, and a reversible Ingress migration.
From ongoing engagements
Kubernetes experience that prevents mistakes before they get expensive
Prevent, catch, secure: three anonymized moments from ongoing engagements.
The decision
The team had planned a multi-cluster setup across three environments, including a dedicated operations crew per cluster. In the weekly sparring session we went through load and availability requirements together. What remained was a single cluster with cleanly separated namespaces, documented in the decision log. Half a year of operational complexity nobody would have needed never came into existence.
Decision log
3 clusters, 3 operations teams
1 cluster, separated namespaces
Deliberately decided, documented
The incident
Friday afternoon, just before the weekend, a cluster upgrade got stuck in a half-migrated state. Through the escalation path, a senior engineer was on the call within the agreed time. The node pool was rolled back in a controlled way and the cluster stabilized before anyone left for the weekend. A potential Monday-morning firefight turned into a quiet Friday evening.
Escalation
Upgrade gets stuck
Senior engineer on the call
Cluster stabilized
Within the agreed time
The audit
A BSI IT-Grundschutz audit was announced with only a few weeks of lead time. Because documented evidence on network policies, RBAC and hardening already existed from the quarterly reviews, nothing had to be reconstructed after the fact. Preparation became a matter of compiling what was already there instead of a night shift. The audit date lost its terror.
Audit evidence
Network policies
RBAC
Cluster hardening
Already on file from the reviews
Consulting · Workshops · Training
An average of 4.9 out of 5 stars from over 1,000 reviews. That standard applies to everything we do.
Support tiers
Which Mamori tier fits your team?
All three tiers cover the same Kubernetes and DevOps stack. They differ in availability, response time, personal continuity and proactive care. Mamori is not an hourly quota.
Your safety anchor
For self-sufficient platform teams
Shared engineering team · defined response times
- Weekly sparring session
- Ticket system + chat (fair use)
- Code reviews & architecture validation
- Structured kick-off
Your growth partner
For growing platform teams
Named primary engineer · prioritized support · health checks
- Everything in Base, plus:
- Named primary engineer
- Monthly health check + report
- Quarterly infrastructure audits
Your senior engineer
For business-critical platforms
Dedicated senior engineer · incident escalation · on-site
- Everything in Advanced, plus:
- Dedicated senior engineer
- Incident support with escalation
- On-site by arrangement (incl.)
Clearly agreed before we start
Monthly fee
Fixed monthly fee, in writing, no hidden costs
Term
Term and notice period clearly defined in the offer
Responsibility
Operations stay with you, responsibilities defined
Cover
Named cover for vacation and absence
NDA & access
Confidentiality and access model agreed
Fair use
Chat and ticket usage transparently documented

Your contact
Vincent Sturm
Key Account Manager
Looking for a partner who keeps a permanent eye on your platform instead of stepping in selectively? Vincent personally advises you on the three Mamori tiers: from the technical consultation to the right engagement, Base, Advanced or Strategic. Reach out to him directly.
A fair question with an honest answer: because a serious figure depends on your environment, not on a table. How many clusters, what criticality, which response time you need decides more than any list price. A flat rate would either overpromise or under-plan.
Mamori runs as a fixed monthly fee per tier, Base, Advanced or Strategic, not an hourly quota. Which tier fits, you can see under the support tiers.
After the free consultation you receive a written offer with a fixed monthly fee, including scope, response times, term and notice period. That way both sides know what they are committing to beforehand.
We support your team; we do not take over. Operations, responsibility and control stay with you: your team makes the changes, while we add senior experience, review decisions and transfer knowledge. That makes Mamori not a managed Kubernetes service that runs your clusters remotely.
We also replace neither your internal team nor your existing providers. We fit into what you already have and reinforce it where senior expertise is missing. You keep your hands on the wheel throughout and decide how deep the support goes.
Mamori is built for enablement instead of dependency: we transfer knowledge, mentor your engineers and gradually make ourselves obsolete. Depending on your tier, knowledge transfer happens directly in the sparring sessions, through focused deep dives or as a structured program.
Runbooks are created and reviewed together with your team, and the documentation stays with you. Regular reports and a roadmap make your team more self-sufficient every month.
If you want to broaden this knowledge build-up, our workshops complement the ongoing engagement in a targeted way.
A production outage or an acute security incident counts as critical. The agreed response time depends on your tier: next business day on Base, 4 hours on Advanced and 1 hour on Strategic, which also includes a 24/7 hotline.
This means the first qualified reply from an engineer with Kubernetes experience, not an automated acknowledgement. From there we support the analysis and decisions during the incident, while implementation stays with your team. You can find the exact figures per tier in the comparison table.
Only as far as you grant it. We agree the access model before we start and set it down in writing, together with confidentiality, in the agreement. Blanket admin access is deliberately not part of it: the scope and route of access follow the concrete need and your approval.
Operations, responsibility and control stay with you. We support analysis and decisions, while implementation is carried out by your team on your platform. You keep full authority over your environment at all times, and we contribute senior experience.
An NDA is a fixed part of the agreement, not an informal promise. We are familiar with air-gapped and sovereign environments from regulated organizations.
Mamori supports Kubernetes regardless of where your clusters run. We cover managed offerings such as AWS EKS, Azure AKS and GKE as well as self-managed setups on Hetzner, in your own data centre or fully on-premise, for example based on kubeadm.
What matters is not the provider but the operations: upgrades, GitOps with ArgoCD, observability and hardening follow the same principles. The covered stack spans 43 technologies, and all three tiers cover the same stack, whatever your environment.
As a rough guide: Base is aimed at self-sufficient platform teams, Advanced (recommended) at growing teams, and Strategic at business-critical platforms. All three cover the same stack and differ in availability, response time, and level of support.
We pin down the right fit in the technical intro call: afterwards both sides know which tier is the right place to start. Moving up a tier is always straightforward, and moving down is possible by arrangement. If short-term needs arise, for instance during a migration, we agree them upfront in a written add-on offer, with no hidden extra costs.
The support tiers give you an overview.
A fixed contract term means we commit just as you do. For the agreed period we reserve capacity and a named point of contact for your team, and turn down other requests to do so. This mutual commitment is what lets us offer a fixed monthly rate instead of fluctuating hourly billing.
Month-to-month options exist on the market, but they cost exactly that: no reserved person, no fixed price, just an interchangeable ticket pool. Fixed minimum terms are the norm for retainers, because continuity only takes effect over several months.
Everything stays transparent: contract term, notice period, scope of services and the named stand-in for absences are set out in writing in the agreement before you sign, with no hidden costs. The specific term for your tier we clarify in the first call and record in the offer.
Shogun is a time-boxed enablement program with a clear end: across four phases (analyze, design, implement, hand over) we enable your team to run the platform independently, on a daily-rate basis. By the end, we have made ourselves redundant.
Mamori is the ongoing engagement in a monthly retainer: a fixed contact, defined response times and proactive reviews, rather than a finished project. Operations stay with your team while we add senior experience for the long run.
The two combine well: many clients start with Shogun and then move into an ongoing Mamori engagement.
The consultation takes 30 minutes and is a technical stocktake, not a pitch. We get to know your platform, your team and your goals, and clarify which tier fits your criticality and required availability. Afterwards both sides know whether Mamori is a fit at all.
If you want to continue, you then receive a written offer with a fixed monthly fee that sets scope, response times and term in writing. Whether you accept it is your decision, taken at your own pace. A kick-off happens only once you say yes. There is no follow-up chain and no funnel, just a clear next step that you choose yourself.
Get started
Which engagement fits your platform?
In the technical consultation we clarify needs, criticality and ways of working. Afterwards both sides know whether Mamori fits and which tier is the right start.
Consultation (30 min)
We get to know your platform, your team and your goals.
Offer with a fixed monthly fee
Scope, response times, term: fixed in writing.
Kick-off & onboarding
Structured onboarding as the start of your ongoing engagement.

Vincent Sturm
Your contact · Key Account
In the call we clarify:
Which tier fits your criticality and team
Availability, response times and continuity
Ways of working, term and notice period
30 min · calendar opens directly · appointment can be moved anytime