Hybrid AI Architecture
FinOps Guard — How it actually works
4
Scenarios
Operate · Optimise · Govern · Inform
16
Hybrid AI Agents
4 per scenario · constrained LLM
0
Auto-Executions
HITL gate on every scenario
Human Goal — any of 4 scenarios
16 Hybrid AI Agents — 4 per scenario
A1 → A2 → A3 → A4Detect
Anomaly Scanner
Investigate
Root-Cause
Simulate
Impact Model
Remediate
API Proposal
Analyse
Usage Scanner
Compare
Cost Simulator
Optimise
Right-Size ID
Draft
RI Recommender
Audit
IaC Scanner
Infer
Owner Attribution
PR
Terraform Injector
Notify
Slack DM Composer
Track
Burn-Rate Monitor
Forecast
Scenario Engine
Triage
Workload Finder
Draft
Finance Memo
Bounded Agentic Autonomy
These 16 agents are not free-roaming chatbots — they operate within mathematical and logical guardrails. No open-ended reasoning loops. No hallucinated numbers. No runaway API spend.
The LLM Doesn't Do the Math — It Calls the Calculator
When an agent reaches the Simulate phase, it hands off to a deterministic math engine (OR-Tools / SciPy). The LLM feeds the inputs, waits for the mathematically exact answer, then reads the result. Savings figures are never guessed — they are calculated.
OR-Tools · SciPy · deterministic output
The LLM Doesn't Do the Routing — It Follows a State Machine
Agents don't loop endlessly and burn API tokens. The pipeline is a Deterministic State Graph (LangGraph / custom state machine): Step 1 must complete before Step 2 fires, Step 3 validates before Step 4 reaches the Human Gate. Every transition is code — not LLM intent.
LangGraph · state machine · no open loops
Complete Security & Privacy Boundary
Database lookups, git history parsing, and IAM log queries run on deterministic local code — sensitive infrastructure credentials and proprietary repo contents never leave your environment or reach a third-party LLM provider. The LLM only sees what you explicitly pass it.
local execution · zero credential leak · air-gappable
Your Hybrid AI FinOps team — that can't act without you
Four autonomous Hybrid AI agents — combining deterministic rules with contextual reasoning, never guessing — continuously monitor your cloud spend, trace root causes, model impact, and prepare remediation. Then they stop dead until a human signs the manifest. No cloud API call, no GitHub PR, no Slack message fires without your signature.
4
Scenarios
16
Hybrid AI Agents
0
Auto-Executions
Scenario Inputs — edit to match your environment
Anomalous Spend RemediationAgentic Workflow — Anomalous Spend Remediation
Detect
Scan billing telemetry, flag exact resource & anomaly score
Investigate
Cross-reference GitHub commits that triggered the cost spike
Simulate
Calculate daily burn rate, monthly impact & RI savings gap
Remediate
Propose cloud API calls to terminate or downgrade rogue resources
