RATIVERA
Know what the assessment covers.
Clear capability boundaries for an AKS evaluation.
| Area | What to expect | Boundary |
|---|---|---|
| Azure AKS | Resource configuration and supported monitoring data inform CPU and memory request assessment. | No broad claim of support for every Kubernetes provider, controller, or workload type. |
| Agentless | No RATIVERA agent in your AKS cluster. | Azure Managed Prometheus and retained metrics remain prerequisites. |
| Workload selection | Choose workloads for assessment within the agreed evaluation scope. | Discovery is separate from selection and from usable evidence; no collection-isolation guarantee is made here. |
| Recommendations | Review current and proposed requests, reasoning, timestamps, and gaps. | No guaranteed savings, performance, availability, or recommendation for every workload. |
| Customer decisions | Accept, reject, or defer where the decision is available. | Acceptance does not merge, deploy, or directly change a running workload. |
| Git workflow | Repository reading, source mapping, and draft change preparation are separate capabilities. | Execution requires separate authorization and verified environment availability; it is not generally promised. |
| Managed workloads | Review ownership and advisory context. | No claim that Microsoft-managed workloads are protected by a universally enforced exclusion. |
| Verification | A cluster check can describe what was observed at a particular time. | No promise of continuing drift detection. |
| Trial and paid access | Controlled evaluation; planned 14-day public trial; separately confirmed paid access. | No public activation, live checkout, or guaranteed history continuity. |
Outside these claims
This site does not offer node-shape optimization, automatic workload changes, guaranteed savings, or SOC 2/ISO certification claims. Broader capabilities require their own verification and agreement.