# Google Compute Engine

Sedai continuously analyzes Google Compute Engine usage and safely resizes instances and machine families — with validation and rollback protection.

## Right-Size Every GCE Instance, Safely

Compute is usually the largest line item on a GCP bill, yet most VMs are sized for peak load and never revisited. Sedai continuously analyzes real usage across your fleet and safely resizes instances, switches machine families, and cleans up wasted storage — without manual effort or outage risk.

## Compute Is the Biggest Line on Your Bill. It's Also the Hardest to Safely Trim.

GCE instances are provisioned for the load they might see, not the load they actually carry — and revisiting that at scale is where teams get stuck.

### Instances are provisioned for peak, not typical, load.

This is especially wasteful for idle dev environments and latency-sensitive apps sized with heavy safety margin.

### Manual rightsizing carries real risk.

A single bad resize can cause an outage, so teams avoid touching thousands of VMs even when they know they're oversized.

### Waste doesn't stop at the VM.

Orphaned disks left behind after decommissioning, oversized storage tiers, and underutilized GPUs all keep costing money long after they stop being useful.

## How We Help

### VM Rightsizing & Family Optimization

Sedai analyzes real usage and recommends smaller instances, cross-family moves (like N2 to E2), or burstable types for workloads with low average but spiky CPU demand.

### Persistent Disk Optimization

Sedai matches disk types to actual I/O patterns to eliminate overpaying for unused performance, and automatically identifies orphaned disks left behind after VM deletion.

### Safe, Validated Execution

Every change runs through defined maintenance windows and is validated against system health afterward, with automatic rollback if anything looks wrong — no manual babysitting required.

## Your Biggest Bill Item Shouldn't Be Your Biggest Blind Spot.

## Frequently Asked Questions

### How does Sedai decide when to recommend a different machine family, versus just a smaller size in the same family?

Sedai first checks whether a smaller instance in the same family fits your usage. If a different family (like E2 instead of N2) offers better cost-performance for that workload's profile, Sedai recommends the cross-family move instead.

### What happens if a workload has occasional CPU spikes? Won't rightsizing hurt performance during those spikes?

Sedai looks for exactly this pattern and often recommends burstable instance types, which keep baseline costs low while still providing burst capacity when the workload actually needs it.

### How does Sedai avoid causing an outage when it resizes a live instance?

Changes run through defined maintenance windows and are validated against system health immediately after execution. If anything looks off, Sedai automatically rolls back the change.

### Does Sedai clean up orphaned disks automatically, or just flag them?

Sedai identifies orphaned Persistent Disks left behind after VM deletion and helps you remove them — eliminating a common, easy-to-miss source of ongoing waste.

### Does this work for VMs behind a load balancer?

Yes. Sedai's optimization applies to individual VMs, including those running as part of a load balancer's backend service.