Overview
Purpose: Executive summary of platform posture across domains.
Inputs: Scores, findings counts, provider/resource telemetry, trend snapshots.
Outputs: Command metrics, domain scorecards, quick links into operational modules.
Product map
Modules and Pages
Detailed module map with purpose, required inputs, and expected outputs so teams know exactly where each workflow lives.
Operate
5 modules
Optimize
4 modules
Govern
3 modules
Evidence
2 modules
Cost Savings
Purpose: Prioritize and execute cost recovery opportunities.
Inputs: FinOps findings, savings summary, reservation candidates.
Outputs: Opportunity ranking, action requests, realized savings tracking.
Cost Savings > 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.
Budgets
Purpose: Monitor budget burn and forecast overrun risk.
Inputs: Current spend, trend assumptions, scope constraints.
Outputs: Budget status, forecast deltas, overrun alerts.
Security
Purpose: Identify and remediate exposure and control failures.
Inputs: Security findings, region policy, rule coverage telemetry.
Outputs: Security score, active incidents, policy violation insights.
Governance
Purpose: Enforce ownership/compliance tagging and policy packs.
Inputs: Required tags policy, scope inventory, saved policy profiles.
Outputs: Missing tag analytics, remediation flows, governance findings.
Resources
Purpose: Global inventory and context hub.
Inputs: Normalized multi-cloud resource records + metadata.
Outputs: Provider/type distribution, carbon and reservation insights, business context.
Findings
Purpose: Unified triage queue across FinOps, Security, Governance, Audit.
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.
Audit
Purpose: Maintain immutable evidence and exportable compliance artifacts.
Inputs: Logs, findings, policy snapshots, action trails.
Outputs: Evidence artifacts, downloadable bundles, audit 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, tenant routing reliability.
TurboFinOps
Start with one cloud scope. Prove savings fast.
Connect AWS, Azure, or GCP and get actionable findings, score trends, and auditable remediation paths in minutes.
Built for FinOps, governance and audit workflows