Post-Deploy Workflow

The complete FinOps loop: Scan → Find → Explain → Fix → Verify → Repeat.

The FinOps Loop

┌─────────────────────────────────────────────────────┐
│                  THE SOFE LOOP                        │
│                                                       │
│   ┌──────┐    ┌──────┐    ┌─────────┐    ┌──────┐  │
│   │ SCAN │ → │ FIND │ → │ EXPLAIN │ → │ FIX  │   │
│   └──────┘    └──────┘    └─────────┘    └──────┘  │
│       ↑                                      │       │
│       │           ┌────────┐                 │       │
│       └────────── │ VERIFY │ ←───────────────┘       │
│                   └────────┘                         │
│                       ↓                              │
│                  ┌──────────┐                        │
│                  │ SCHEDULE │ (repeat every 6h)      │
│                  └──────────┘                        │
└─────────────────────────────────────────────────────┘

Recommended Workflow (Step-by-Step)

1. Step 1.
   Connect your AWS account
   Docs: Connect AWS →
2. Step 2.
   Run your first evaluation
   Dashboard → evaluate. Or CLI: sofe evaluate --cloud
3. Step 3.
   Review findings in /history
   Click the evaluation → see all findings with severity badges
4. Step 4.
   Explain critical findings with AI
   Click "🧠 Explain with AI" to understand WHY it matters. Docs →
5. Step 5.
   Copy remediation commands
   Click "🛠️ View Remediation" → copy CLI command → execute. Docs →
6. Step 6.
   Mark as Fixed (or Ignore)
   After applying the fix, click "✅ Fixed" on the finding. It dims and tracks your progress.
7. Step 7.
   Enable scheduled evaluations
   Set to every 6h. Next scan confirms your fix worked (finding should disappear). Docs →
8. Step 8.
   Set up Slack/email alerts
   Get notified only when NEW critical/high findings appear — no noise. Docs →

Best Practices for FinOps Practitioners