Two hundred and forty-seven applications. Three datacenters. Twelve quarters. Panaptico runs the portfolio as a live graph — every app classified, every wave overlapped by design, every domain strangled instead of rewritten, every outcome traced back to the budget that paid for it.
From · on-prem
VMware · 3 datacenters
Program state
112 / 247 apps
Migrated
112
In flight
95
Queued
40
To · cloud
AWS · 2 primary + 1 DR
Current quarter
Q7 of 12 · 58% done
DC Dallas
offline · Q6 ✓
Cost run-rate
$18.2M → $11.4M
Board sign
Q4 2026 · next
The gap
01
‘We’re moving 247 apps to the cloud.’ Eighty of them are duplicates nobody’s admitted to. Twenty belong on-prem for regulatory reasons. The spreadsheet doesn’t know.
02
The product keeps shipping while the foundation gets rebuilt. Every wave ships into live traffic. Modernization without a strangler-fig plan becomes a slow rewrite that the market eats alive.
03
Year one is landing zones. Year two is moving the easy apps. Year three is the hard architectural calls — and by then the sponsor is gone, the team has rotated, and nobody remembers why.
Portfolio disposition
Panaptico classifies the full portfolio against the 6-R framework — rehost, replatform, refactor, rebuild, retire, retain. Each decision is bound to the systems still depending on it.
Lift-and-shift · minimal change
Lift-tinker-shift · managed services
Re-architect within the same bounded context
Decompose · cloud-native from scratch
Decommission · duplicate / end-of-life
Stay on-prem · latency / regulatory
Program roadmap
Foundation first, then waves overlapping by design. Every stream is tied to signed outcomes and to the datacenter retirements they unlock. The current quarter marker advances with the graph, not with the slide deck.
Foundation
Wave 1 · rehost
Wave 2 · replatform
Wave 3 · refactor
Wave 4 · rebuild
Retire · decom
Strangler-fig decomposition
The checkout monolith couldn’t be rebuilt as a single cutover. Panaptico decomposed it into bounded contexts, routed traffic domain by domain, and preserved the transaction graph across the seam.
System under modernization
checkout-monolith · 2014 · Java 8 · MSSQL
Catalog
Rehosted · Q3 · RDS Aurora · read replicas
Pricing
Refactored · Q5 · stateless · API Gateway
Inventory
Refactored · Q6 · event-sourced warehouse
Payment
Rebuilding · Q7 · Lambda + DynamoDB · PCI scope re-scoped
Orders
Queued · Q9 · Step Functions · saga pattern
Fulfillment
Queued · Q10 · EKS · warehouse plugin SDK
Traffic · monolith vs new services
Outcome ledger
Every quarter, the graph reports against the outcomes the budget was signed for — not velocity, not activity. Lead time, cost, resilience, capability. If a wave doesn’t move the number, it doesn’t ship.
Was
14 days
Now
2.3 days
Target
1 day
deploy frequency 2/mo → 23/wk
Was
$18.2M
Now
$11.4M
Target
$9.1M
DC Dallas offline · 64% utilization target
Was
4h 12min
Now
47 min
Target
15 min
observability stack · automated runbooks
Was
8 hours
Now
22 min
Target
<15 min
multi-region active · chaos-tested Q6
Was
3 DCs
Now
2 DCs
Target
1 DC (Amsterdam · retain)
regulatory hold on EU workloads
Was
31%
Now
58%
Target
85%
curriculum + pairing · Platform team sponsors
Panaptico binds every wave, every decision, every decommission to the outcomes the board signed for — so the program is legible from quarter one to quarter twelve.