Managed Platform.
Managed Platform is Todea's long-term partnership for production Kubernetes: we install, operate, upgrade, and evolve your platform under a 12-month contract. You choose one of two support tiers at signature (Essential or Enterprise), and your engineers go back to shipping product.
- 12-month term
- Two support tiers
- Architecture ownership
What it is
Your platform, run by the people who build platforms.
Under a Managed Platform contract, Todea builds (or takes over) your Kubernetes platform, then owns its operation, upgrades, and evolution within the agreed scope. This is not a ticket queue or on-call insurance: it is a senior platform team that works alongside your engineers, makes the architecture decisions, and helps your application teams get the most from the platform.
Your team owns the workloads; we own the platform. The service runs at a fixed annual fee based on your platform footprint and chosen tier, and routine cloud changes are included.
Embedded platform team
Senior engineers alongside yours, not a ticket queue
Operations and upgrades, handled
Day-to-day operations, version upgrades, and security patches, on a planned cadence
Architecture ownership
We own platform and infrastructure architecture decisions within the agreed scope
Fixed annual fee
A predictable cost at the tier you choose, reviewed at each renewal
What's in
Three streams of work, every year, inside the agreed scope.
Every contract year runs three streams of platform work, all within the scope agreed at signature.
Operation
The day-to-day work of keeping the platform running, tracked and delivered inside your tier.
Requests run through Todea's shared tracking system: authorized users submit changes directly, and every request carries owner, priority, status, and resolution. One shared history for compliance, incident review, and planning.
Incident response at your tier's coverage window and response SLA: incidents are logged, triaged, and reviewed after resolution.
Version upgrades and security patches across the contracted product set, on a planned cadence aligned to your change policy: real engineering work, performed by us.
Operational changes within the contracted scope (deployments, namespaces, RBAC, policies, dashboards, secrets, scaling, alert tuning) across whichever cloud-native tools your stack uses, with no separate invoicing.
Evolution
Keeping the platform current and improving it over time: engineering, not just upkeep.
Lifecycle management: upgrade strategy, addon currency, deprecation handling, migration planning.
Continuous refinement: alert tuning, dashboard improvement, runbook updates, cost optimization, security-posture hardening.
Roadmap reviews on your tier's cadence, so platform work stays aligned with where your product is going.
Platform-team work
We embed with your engineers and take ownership of the platform's architecture.
We join your regular engineering rituals (standups, design reviews, incident retrospectives) on a schedule agreed at signature.
We take responsibility for platform and infrastructure architecture: cluster topology, tool adoption, region expansion, the evolution of the observability stack. You state the need; we decide how the platform meets it.
Who this is for
Teams that want to ship product, not run Kubernetes.
Managed Platform fits organizations where Kubernetes is essential infrastructure but not the product. Common situations:
Only need the build, and you'll operate it yourself? That's an Implementation Project. Don't yet know what you need? That's a Platform Readiness Review.
Teams slowed by platform work
Engineers should be on the product
The platform has become the bottleneck, and the people maintaining it were hired to build product.
Teams that cannot hire seniors
The market for platform engineers is thin
Hiring, training, and retaining an in-house platform team is slow and expensive; delegating it to specialists is neither.
Teams that want predictable cost
One fixed annual budget
A fixed annual fee with a yearly review, instead of hourly billing or open-ended engagements.
Teams launching a new platform
Built and run by the same team
A production-grade platform built and then operated by the people who built it.
Teams that inherited a platform
Work your team cannot staff
The platform needs sustained senior attention that your current team cannot provide.
Teams leaving a legacy system
One partner, end to end
Move off the legacy system with one partner who builds, transitions, and then operates the new platform.
How we work
A long-term partnership, scoped annually, operated at the tier you choose.
Five phases from scoping through renewal, the same shape every year.
Phase
01
Scoping
We confirm the platform footprint and the support tier. The statement of work fixes the all-in annual fee for the contract year.
Phase
02
Build or takeover
We build the platform inside the contract, or take over an existing one with Year-1 discovery and gap remediation.
Phase
03
Operate
Day-to-day operations at your tier: coverage window, response SLA, and on-site allowance per the comparison below.
Phase
04
Evolve
Roadmap reviews on the tier cadence, plus operational changes as they arise.
Phase
05
Renew
Sixty days before each anniversary we reconcile footprint and tier against actual usage; the fee adjusts up, down, or stays flat depending on what changed.
Choose your tier
Two tiers. 12-month terms.
The tier sets your coverage window, response SLA, and on-site allowance. Support is part of the Managed Platform contract: there is no separate support product to buy.
Best for
Production platforms where an incident raised outside the coverage window can wait until the next business day. If that is unacceptable, choose Enterprise.
Coverage window
Mon–Fri 09:00–18:00 KST*
Response SLA
Best-effort 24-hour target within the coverage window
Named engineer
Not included
On-site days included
On request, billed separately
Best for
Production-critical platforms where downtime is revenue-impacting in real time.
Coverage window
Mon–Fri 09:00–18:00 KST* + 24×7 paging for SEV1
Response SLA
SLA-backed; 4-hour initial response for SEV1
Named engineer
Named-engineer commitment
On-site days included
1 day/month; additional on request**
* 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.
Frequently asked
What teams ask before they start.
What does the Managed Platform service cover?
A 12-month partnership under which Todea installs, operates, upgrades, and evolves your production Kubernetes platform. It is full delegation: Todea's senior engineers run the platform end-to-end while your team stays focused on the product.
Do we need Kubernetes engineers in-house?
No. Operating the platform (upgrades, incidents, capacity, security patching) is Todea's job under this service. Everything is documented as it is operated, so your organization keeps full visibility and is never locked in.
What is the difference between the Essential and Enterprise tiers?
Essential covers Monday to Friday, 09:00–18:00 KST, with a best-effort 24-hour response target. Enterprise adds 24×7 SEV1 paging with an SLA-backed 4-hour initial response, a named-engineer commitment, and one on-site day per month. The tier is chosen at signature.
Can Todea take over a platform we already run?
Yes. Engagements over an existing platform 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.
Do you work on-site?
The service is remote-first, with on-site work available in the Seoul metro area. The Enterprise tier includes one scheduled on-site day per month.
Ready to hand off operations?
Let us run the platform. Your team ships product.
Other services
