SaaS + embedded workflow adapters
Stride Rightsizing Studio
Pairs utilization telemetry with change tickets so rightsizing recommendations arrive with an owner, risk note, and rollback path.
₩4,100,000 per year (informational)
Overview
Stride watches compute and relational footprints against seasonal baselines. Recommendations land as Kanban-ready cards that reference the workload profile we observed, not generic percentages. Your SRE council can reject or snooze suggestions with reasons, which trains the model for the next cycle.
Capabilities
- Instance family heatmaps with purchase-option overlays
- Change windows that respect regional freeze calendars
- GPU vs CPU mix tracking for ML batches
- Linked CMDB hooks for service criticality
- Slack digest with diff links, not vanity scores
- Safety buffers tuned per environment class
- Post-change capture for realized savings notes
Outcomes teams track
- Rightsizing decisions carry accountable owners in Jira or Linear.
- Rejected suggestions explain risk, reducing repeat noise.
- Savings notes connect to finance recognition rules.
Plan questions
No. The product opens pull requests or tickets; humans approve. We avoid silent production mutations.
Experience notes
-
Cards cite the metric window they used—refreshing honesty when data is messy.
-
We still negotiate internally, but Stride stopped the ping-pong of contradictory spreadsheets.