Sedai already gives you deep visibility into individual resources, opportunities, and savings. Now we're providing a single place to step back and understand your entire environment at a glance.
The Resource Lifecycle dashboard gives you a real-time, 10,000-foot view of every resource managed by Sedai: where it is in the optimization pipeline, what's actively moving forward, and where you can take action to unlock more value.
A Bird's-eye View
Resources are surfaced across all your clusters, cloud providers, and accounts, organized into the stages of Sedai's optimization workflow. At the top level, they're grouped into three high-level states:
- Analysis and Execution — Resources Sedai is actively working through. This includes resources currently being analyzed, those queued up and ready to execute, and those actively being optimized right now.
- Pending Review — Resources where Sedai has found an optimization opportunity but needs your input before it can act. This is the human-in-the-loop stage. If you're running in Copilot or Datapilot mode, these resources are waiting on your review and approval.
- Blocked — Resources where something is preventing Sedai from proceeding. Blockers come in two types: actionable (resolvable directly within Sedai by adjusting settings or preferences) and external (requiring a change outside of Sedai, like updating permissions or environment configurations).
Understanding the Lifecycle Stages
Sedai's optimization process is a pipeline. Resources move through it in a predictable sequence, and Resource Lifecycle makes that sequence visible.
When a resource is first discovered, Sedai begins analyzing it. Once an opportunity is identified, what happens next depends on the resource's operation mode:
- Autopilot: Sedai moves the resource into a Ready state and picks it up in the next execution batch.
- Copilot: The resource enters the Review: Copilot queue, waiting for you to approve the change.
- Datapilot: Sedai surfaces its recommendation in the Review: Datapilot queue, but operates read-only. No changes are applied until you either make a change manually or enable a more active mode.
Once an execution batch is picked up, resources move through In Queue and into Executing. When complete, the optimization becomes a realized saving.
If Sedai can't complete its analysis — for example, because telemetry is missing — the resource is marked Analysis Blocked. If Sedai has found an opportunity but determines it's not yet safe to act, the resource is marked Execution Blocked. Common execution barriers include things like a recent deployment (Sedai backs off to gather more data after changes in the environment) or insufficient replica counts (Sedai won't act if it can't make a non-disruptive change).
Drill In, Don't Just Observe
Resource Lifecycle isn't a static summary. It's a starting point for action.
Clicking into any status card opens a detailed view of the resources in that state, with explanations of what the status means and what you can do about it. For blocked resources, Sedai breaks down barriers by type and frequency, so you can immediately see where the biggest bottlenecks are. Where a barrier can be resolved within Sedai, you'll see a direct action button. Where it requires an external fix, Sedai links to documentation explaining exactly what needs to change.
You can also filter the entire dashboard by cloud provider, cluster, region, or resource type. If you own Kubernetes workloads and want to see where those specifically stand in the pipeline, without wading through Lambda functions or ECS services, you can do exactly that.
Built for Everyone on the Team
Resource Lifecycle isn't just for account administrators. It's designed for any engineer or operator who owns a slice of the environment and wants to understand where their resources stand.
If you're running Copilot and want to know what is queued for your review versus still being analyzed, this is your dashboard. If you're trying to unblock execution and want to prioritize which barriers to tackle first, the barrier breakdown tells you exactly where to focus. And if you're responsible for the overall health of Sedai's operation, the optimization summary at the bottom of the page gives you a 30-day view of completed optimizations, cost savings realized, and cost avoidance from reclaimed CPU and memory.
Integration Health, Front and Center
One more thing: Sedai can only optimize what it can discover. If there's a problem with an integration — an AWS account connection, a Kubernetes cluster, an Azure subscription — Resource Lifecycle surfaces those issues at the top of the page, with a direct link to diagnose and resolve them. Fixing discovery issues upstream means more resources flowing into the optimization lifecycle downstream.
Available Now
Resource Lifecycle is available today — you can find it in the left navigation. Check it out and let us know what you think. And if you’re not already a Sedai customer, book a demo to learn more.
