Today
Purpose: Action-first summary of what to approve or fix next.
Inputs: Recoverable spend, action queue state, verification status, and trend snapshots.
Outputs: Today priorities, owner-ready decisions, and links into execution workflows.
Product map
Modules and Pages
Detailed module map showing how each workflow supports one goal: recover cloud and AI spend, then prove the outcome.
Core surfaces
4 surfaces
Savings workflows
4 workflows
Risk context
3 supports
Proof artifacts
2 exports
Savings
Purpose: Prioritize and execute cost recovery opportunities.
Inputs: FinOps findings, savings summary, receipt checkpoints and reservation candidates.
Outputs: Opportunity ranking, action requests, verified receipts and savings history exports.
VM Scheduling
Purpose: Customer-defined VM start/stop policy for off-hours optimization.
Inputs: VM inventory, selectedResourceIds, schedule window and timezone.
Outputs: Projected savings and persisted scheduling policy.
Costs
Purpose: Monitor budget burn and forecast overrun risk.
Inputs: Current cloud spend, AI usage, unit economics, trend assumptions and scope constraints.
Outputs: Budget status, forecast deltas, cost attribution and overrun alerts.
Risk Guardrails
Purpose: Protect savings execution with strong controls and safe defaults.
Inputs: Exposure findings, policy checks, role telemetry.
Outputs: Risk-prioritized issues and guardrailed remediation context.
Ownership & Allocation
Purpose: Keep ownership and allocation data clean so savings stay attributable.
Inputs: Required tags policy, scope inventory, saved policy profiles.
Outputs: Missing tag analytics, remediation flows, and improved allocation accuracy.
Resources
Purpose: Global inventory and context hub.
Inputs: Normalized multi-cloud resource records + metadata.
Outputs: Provider/type distribution, carbon and reservation insights, business context.
Supporting Findings
Purpose: Unified detection queue feeding Today and Savings decisions.
Inputs: Scanner detections and rule metadata.
Outputs: Filtered decision queue and action entry points.
Scans
Purpose: Run and track inventory/finding scans.
Inputs: Active cloud scopes and scanner jobs.
Outputs: Scan job history, status, and detection refresh.
Actions
Purpose: Manage request/approval/execution/rollback lifecycle.
Inputs: Action requests, provider adapters, readiness baseline.
Outputs: Execution status, rollback metadata, readiness evidence.
Evidence
Purpose: Maintain immutable evidence that validates executed savings work.
Inputs: Logs, findings, receipt context, policy snapshots, action trails.
Outputs: Receipt evidence, downloadable bundles, and immutable history.
Connections
Purpose: Manage cloud credentials and scopes securely.
Inputs: Provider credentials, scope configs, key mapping policy.
Outputs: Connected inventory sources and secret posture telemetry.
Integrations
Purpose: Bridge TurboFinOps with enterprise systems.
Inputs: Jira/ServiceNow/webhook/AI provider configuration.
Outputs: Ticket handoff, alert routing, AI-assisted context surfaces.
Settings
Purpose: Tenant administration and security controls.
Inputs: Users, roles, domains, SSO, key mapping settings.
Outputs: Policy governance, access controls, billing readiness and tenant routing reliability.
Get started
Find recoverable spend before the next invoice lands.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.
Read-only scan first. Approval gates before remediation.