OpsWerks
OpsWerks at KubeCon + CloudNativeCon North America | Salt Lake City | November 9-12, 2026

You ship production AI. We run your Kubernetes

AI workloads now run on the same Kubernetes clusters your team has to upgrade and patch. OpsWerks owns that work end to end, 24/7, so your engineers ship the AI roadmap instead of the maintenance queue.

Schedule a discovery call
Find us at KubeCon

Meet us in Salt Lake City

We’re at KubeCon November 9-12. If upgrades, patching, or on-call are holding up your AI roadmap, let’s find twenty minutes to talk through what we’d take off your plate.

Mike Lam, Strategic Accounts at OpsWerksMike LamStrategic Accounts
Asia Selke, Director of Sales at OpsWerksAsia SelkeDirector of Sales
Schedule a discovery call
Proven at enterprise scale
500+
Kubernetes clusters upgraded in 90 days
5,000+
EKS nodes patched in under a week
2+ years
running Kubernetes upgrades on a Fortune 100 AI data platform
Why we’re at KubeCon

This year, KubeCon is about running AI in production

The shift is from training models to serving them, on Kubernetes, at scale. Every one of those clusters still needs upgrades, patches, and someone on call, and that’s the work OpsWerks owns. Our team holds Certified Kubernetes Administrator (CKA) and Certified Kubernetes Application Developer (CKAD) certifications.

AI and Data Platforms

The data platform behind your AI, kept current

AI and data workloads run on fleets of Kubernetes clusters with hard deadlines on versions and vulnerability fixes. We keep those clusters upgraded and in service, so your SREs work on the platform, not the support queue.

Hundreds
of Kubernetes clusters upgraded in a single month on a petabyte-scale AI data platform
Read the case study
Platform Engineering

A platform team that builds, not maintains

An internal platform only pays off if someone keeps the pipelines and tooling underneath it running. We own that layer, so your platform engineers ship self-service instead of working the ticket queue.

24 months
earlier to general availability for the client’s new CI/CD platform, while OpsWerks ran the one it replaced
Read the case study
Security

Exploits don’t wait for the patch window

When a critical vulnerability is exploited in the wild, a 30-day patch cycle is a 30-day exposure. The fleet has to be closed in days, without an outage.

Zero
P0/P1 incidents caused by the rollout, with 5,000+ EKS nodes patched against a 30-day window
Read the case study
The operating boundary

What we take off your plate

OpsWerks owns

  • Kubernetes upgrades and version compliance across EKS, GKE, and AKS
  • Patching and vulnerability remediation across the fleet
  • Infrastructure for AI and data workloads, including Spark, Kafka, and Airflow pipelines
  • CI/CD pipeline management on Jenkins, GitLab, and GitHub
  • 24/7 monitoring, incident response, and post-incident follow-through
  • Runbooks, documentation, and automation

Your teams keep

  • Platform architecture and the roadmap
  • AI architecture, governance, and roadmap
  • The developer experience your platform offers
  • Security policy and access approvals
  • Workload and release priorities

We don’t bill hours; we own results.

How we take over

From handover to full ownership

After a structured transition, the same stable team manages the agreed scope and retains context over time. Knowledge compounds through documentation and runbooks instead of walking out the door with turnover.

01Engagement alignment. Define service scope, responsibilities, success measures, access requirements, and approvals.
02Discovery and planning (weeks 1-2). Review architecture, dependencies, tooling, operating procedures, risks, and current pain points.
03Team integration (weeks 3-4). OpsWerks engineers work alongside your team to validate access, monitoring, documentation, runbooks, and escalation paths.
04Gradual ownership (weeks 5-8). Shadow and reverse-shadow periods progressively transfer the agreed operational responsibilities.
05Managed operations. Operate the agreed scope 24/7 while continuously improving documentation, automation, monitoring, and remediation.
What customers say

“Thanks a lot for the amazing work this week. It was no easy feat to patch over 5,000 nodes within a week. Thank you for coming together as a team to make this happen on such short notice and within such a short time frame. Really appreciate it.”

Cloud Engineering leader, Fortune 100 technology company

Due to strict enterprise confidentiality requirements, customer names and organizations are anonymized.

Stop managing operational overhead. Start building competitive advantage

Whether we met in Salt Lake City or you’re finding us afterwards, tell us what your platform runs on and we’ll show you what OpsWerks would own.

Schedule a discovery call Email partnerwithus@opswerks.com
You define the outcomes. We own the delivery.