Technical overview
What the platform is
Percy’s Platforms is a managed EKS platform for AWS teams that want the control and reliability benefits of Kubernetes without building a full internal platform function.
The product is not just a cluster build. It is an operating model that includes:
- a private-by-default EKS landing zone and Kubernetes baseline
- controlled delivery and upgrade paths
- policy guardrails
- operational validation and evidence
- explicit platform and application ownership boundaries
What the platform owns
The platform owns the baseline lifecycle: cluster build, platform add-ons, upgrades, policy baselines, platform access posture, and the operational safety rails around change.
What the customer owns
The customer owns application code, release logic, runtime correctness, application-level on-call, and service-specific performance or reliability decisions.
Why the model matters
Most Kubernetes pain is not caused by the cluster existing. It is caused by unclear ownership, fragile change paths, and too many bespoke platform decisions. The product is designed to reduce those failure modes directly.
Security baseline
The current baseline is designed for teams with real security expectations, while staying honest about what has and has not been proven yet:
- private-by-default control plane
- encryption-backed secrets handling
- least-privilege access controls
- policy enforcement for platform safety baselines
- evidence-oriented workflow and runbook design
Service posture
The service starts with a pilot-first motion rather than a broad self-serve launch. Commercial qualification happens through discovery and pilot scope rather than a broad self-serve purchase path.
Use the security, evidence, and pilot pages together: security explains the guardrails, the evidence pack explains pilot completion, and pilot intake confirms whether the first workload path is a fit.