Skip to content
Services · Managed Platform

Managed Platform.

Experienced engineers operate and improve your Kubernetes platform, so you don't have to build a dedicated platform team.

Opens a short form. An engineer replies within 1–2 business days; the proposal sets the scope, the tier, and the annual fee.

  • Operated by senior engineers
  • Responsibility across components
  • 12-month term

What it is

Your platform, run by the people who build platforms.

Our engineers maintain, upgrade, and configure your Kubernetes platform, investigate incidents, and keep improving it, so you have an experienced platform team without hiring one.

Your team runs its applications; we take responsibility for the platform, including how its components work together, at a fixed annual fee with routine changes included.

Who it's for

  • Teams whose engineers, hired to build product, are tied up maintaining the platform
  • Organizations that need senior platform engineers they cannot hire or staff
  • Teams launching a new platform that want it built and run by the same people
  • Teams caught relaying evidence between providers when something breaks across components

Only need the build, and you'll operate it yourself? That's an Implementation Project. Not sure yet what you need? Start with a Platform Readiness Review.

Responsibility

When a problem crosses components, we lead it to the end.

The components in your contract may come from different vendors and open-source projects. Whichever one the cause sits in, the work stays with us, and you always know who is moving it forward.

Todea is responsible for

  • Investigation across the network, the mesh, the cluster, the platform tools, and your workloads, wherever the evidence leads
  • Raising issues with cloud providers, vendors, and open-source projects, with the evidence, and following them up
  • Applying and validating the fix through the agreed change process, tested first and with a way back
  • Following through after service is restored: the cause fixed, the workaround removed, and an alert, test, or runbook step added

Your team keeps

  • Your applications, and the decisions about them
  • The platform's goals and constraints, and approval of significant decisions
  • Your infrastructure and accounts, including your vendor support contracts
  • Full visibility: every request, change, and incident in one shared history

Incident record

SEV2 · Load balancer, ingress, and service mesh

Illustrative example

Intermittent 502 errors on checkout after an ingress controller upgrade.

  1. Detect

    An error-rate alert fires on checkout. The load balancer, the ingress, and the pods all report healthy.

  2. Mitigate

    We roll the ingress controller back to the previous version as a temporary measure. Errors return to baseline.

  3. Find the cause

    Proxy logs show the new version keeps idle connections to services open longer than the mesh proxies do, so some requests reuse connections the mesh has already closed.

  4. Escalate and fix

    We report the changed default to the ingress project, align the idle timeouts in Git so each hop closes idle connections before the next one does, and reapply the upgrade through the change process.

  5. Prevent recurrence

    We add an alert on upstream connection resets and a timeout check to the upgrade runbook, then review the incident with your team.

Owner · Todea platform team, from alert to review

Your team · Kept informed at each step; approved the change window

Logged in the shared tracking system: one history for compliance, incident review, and planning.

Choose your tier

Two tiers. The same engineers.

The tier sets coverage, response, and on-site time. The engineers, the responsibility, and the engineering standards are the same in both, and support is part of the contract.

In both tiers

  • The same experienced platform engineers and engineering standards
  • Responsibility across every component in scope, and how they work together
  • Maintenance, upgrades, incident investigation, and continuous improvement
  • Roadmap reviews on a cadence agreed at signature

Essential

Business-hours coverage

Enterprise

Recommended

24×7 SEV1 paging

Best for

Platforms where an incident raised outside the coverage window can wait until the next business day.
Production-critical platforms where downtime affects revenue in real time.

Coverage window

Mon–Fri 09:00–18:00 KST*
Mon–Fri 09:00–18:00 KST*

Response

Best-effort first response within 24 coverage-window hours
24×7 paging for SEV1, with an SLA-backed 4-hour initial response

Named engineer

Served by the platform team, without a named engineer
Named-engineer commitment

On-site days

On request, billed separately
1 day/month; additional on request**

Response times measure an engineer's first response, not the time to resolve. Coverage-window hours count only Mon–Fri 09:00–18:00 KST.

* Issues raised outside the coverage window are picked up the next business day, except where 24×7 SEV1 paging applies.

** On-site days outside the Seoul metro area are available on request, with travel billed separately.

What we do

Three streams of work, across the whole platform.

Your contract lists the components we cover, and coverage includes how they work together.

Stream 1

Operation

Keeping the platform running, tracked and delivered inside your tier.

  • Requests through a shared tracking system: authorized users submit changes directly, and every request carries an owner, priority, status, and resolution.
  • Incident investigation within your tier's coverage and response commitment: triage, mitigation, cause, fix, and review.
  • Upgrades and security patches for every component in scope, from Kubernetes to GPU drivers and serving runtimes, planned together and aligned to your change policy.
  • Configuration changes (deployments, namespaces, RBAC, policies, dashboards, secrets, scaling, alerts) with no separate invoicing.

Stream 2

Evolution

Keeping the platform current and improving it: engineering, not just upkeep.

  • Lifecycle management: upgrade strategy, add-on currency, deprecations, migration planning.
  • Continuous refinement: alerts, dashboards, runbooks, cost, and security posture.
  • Roadmap reviews on a cadence agreed at signature, aligned with where your product is going.

Stream 3

Platform-team work

Working alongside your engineers, responsible for the platform's architecture.

  • Your engineering rituals (standups, design reviews, incident retrospectives) on a schedule agreed at signature.
  • Platform architecture: cluster topology, tool adoption, region expansion, observability. You set the goals; we recommend options with their trade-offs and agree significant decisions with you.

How a contract runs

Onboarded once, operated and improved every year.

Scoping and onboarding happen once. Operating, improving, and renewing repeat every contract year.

Practical terms

Term
12 months, with footprint and tier reviewed before each renewal.
Fee
One fixed annual fee for the contract year, based on your platform footprint and tier. Routine changes are included, with no separate invoicing.
Existing platforms
A takeover usually starts with a Platform Readiness Review, so operations begin from a verified state; part of its fee is credited if the Managed Platform starts within 90 days.
On-site
Remote-first, with on-site work in the Seoul metro area. Enterprise includes one on-site day a month.
  1. Scoping

    We confirm the platform footprint and the support tier, and the statement of work fixes the annual fee.

    WhenOnce, at onboarding

  2. Build or takeover

    We build the platform, or take over the one you run, with discovery and gap remediation in the first year.

    WhenOnce, at onboarding

  1. Operate

    Maintenance, upgrades, configuration changes, and incident investigation, within your tier's coverage.

    WhenAll year, every year

  2. Evolve

    Continuous improvement, plus roadmap reviews on a cadence agreed at signature.

    WhenAll year, every year

  3. Renew

    Sixty days before each anniversary we reconcile footprint and tier against actual usage, and the fee adjusts up, down, or stays flat.

    WhenBefore each anniversary

Every year

Frequently asked

What teams ask before they start.

Do we need Kubernetes engineers in-house?

No. Operating the platform (upgrades, incidents, capacity, security patching) is Todea's job under this service. Your team stays focused on its applications, and approves the decisions that matter.

Are we locked in?

No. Everything is documented as it is operated, in your own systems: architecture decisions, runbooks, and the history of every request, change, and incident. The knowledge stays with you whether we keep operating the platform or hand it back.

Who handles problems that involve a vendor or an open-source project?

Todea does. We collect the evidence, raise the issue with the vendor or the project, follow it up, and apply and validate the fix through your change process. Where a vendor accepts cases only from its customer, we prepare the case for your support contract and work it through with you.

Can Todea take over a platform we already run?

Yes. Takeovers typically start with a Platform Readiness Review, so operations begin from a documented, verified state rather than assumptions, and part of the review fee is credited when the Managed Platform starts within 90 days.

Can we change tier later?

Footprint and tier are reconciled against actual usage sixty days before each anniversary, and the fee adjusts up, down, or stays flat with them.

Does the service cover GPU and AI workloads?

Yes, where they are in scope. Upgrades and security patches cover GPU drivers and serving runtimes along with Kubernetes and the rest of the platform, and incident investigation follows the same evidence wherever it leads.

Ready to hand off operations?

Let us run the platform. Your team ships product.

Request a proposal

Opens a short form. An engineer replies within 1–2 business days; the proposal sets the scope, the tier, and the annual fee.