Skip to main content

Before AI tools touch your code, know exactly what they'll find.

Compass is the five-layer assessment that sits between your codebase and your modernization business case. A fleet of specialist analysis agents runs across every application in the portfolio, inside your own AWS account. They map static complexity, architectural coupling, test verifiability, change risk, and AI readiness, then put a dollar figure on both your tech debt and your breach risk.

Two to three weeks. Fixed fee. The output is built for both the architect acting on it Monday morning and the boardroom funding the program, with a sequenced roadmap that feeds straight into Evolve.

2-3 weeks Fixed fee Five assessment layers Tech debt in dollars AI readiness per service Sequenced roadmap
Trusted by enterprises, banks, healthcare systems, and the world's biggest brands
Hyundai Glovis logo Pixis logo GORUCK logo Sweet Analytics logo Red Bull logo Gavel logo CarSaver logo Newton logo Reven AI logo SolvPath logo Virgil logo Ryno Strategic Solutions logo Hyundai Glovis logo Pixis logo GORUCK logo Sweet Analytics logo Red Bull logo Gavel logo CarSaver logo Newton logo Reven AI logo SolvPath logo Virgil logo Ryno Strategic Solutions logo

Most modernization programs fail because they start building
before they understand what they're building on.

70-80% of modernization programs fail to meet objectives. The failure mode is almost always the same. Teams start converting services before understanding the dependencies, the hidden business logic, the architectural coupling that turns a 3-month migration into a 14-month project.

The assessment phase gets compressed because "we already know our codebase." You don't. Nobody does. The knowledge lives in tribal memory, retirement-age developers, and code comments from 2014.

And the risk is no longer just budget and timeline. Point AI coding tools at code that isn't ready, with no tests, exposed secrets, or tangled boundaries, and they amplify every existing flaw at machine speed.

70-80%

of modernization programs fail to meet objectives

McKinsey 2025, Gartner 2026
60%

of cloud migration initiatives exceed budget, miss timelines, or fail to deliver expected outcomes

Hashroot enterprise analysis 2025
20-40%

of IT budgets consumed by technical debt before any new investment begins

Deloitte 2026

Five layers. Every application.
The picture that turns "we should modernize" into a funded program.

Compass doesn't give you a traffic light matrix. A fleet of specialist analysis agents runs all five layers across every service, and each layer is designed to answer a specific question your leadership team is asking. The output is structured so architects can plan, finance can budget, and leadership can sequence the work.

01 Layer One

Static Complexity

What's in the codebase. Lines of code, language breakdown, dependency graph, cyclomatic complexity, dead code percentage. This is the layer that tells you how big the job actually is, not how big someone estimates it to be. Every module mapped. Every dependency traced.

02 Layer Two

Architectural Coupling

How entangled the services are. Coupling score per service pair, shared database dependencies, synchronous call chains, and the size of the failure zone per change. This is the layer that predicts which "simple refactor" becomes a six-week investigation.

03 Layer Three

Test Verifiability

How safe it is to change. Test coverage per module, test quality score (not just line coverage but mutation testing where applicable), integration test dependency map. This layer tells you which services can be changed with confidence and which ones will break silently. AI agents need test contracts to operate safely. No tests, no safe AI.

04 Layer Four

Change Risk

How dangerous each change is. Change failure rate per service, deployment frequency, lead time, and incident correlation. The output tells you which services produce the most incidents when touched, so leadership can sequence them at the start or end of the program, not the middle of it.

05 Layer Five

AI Readiness

How ready, and how safe, each service is for agentic tooling. Scores each service against the prerequisites for safe AI operation: test coverage threshold, architectural isolation, observability instrumentation, dependency clarity. It also weighs the security hygiene that makes AI tooling dangerous in the wrong place, from secrets and exposed data sitting in source to missing authentication and AI-unsafe patterns. Services score "ready now," "needs foundation work first," or "retire." This is the layer that tells you where to point AI agents and where to keep them away until the foundation is in place.

Six deliverables. All in 2-3 weeks. All yours to keep.

A static analysis tool gives you a code-quality report. A security scanner gives you a CVE list. An architecture review gives you a slide deck. None of those is a decision artefact. Compass combines the five layers into one structured output your CTO uses to prioritize, your CFO uses to budget, and your architects extend on Monday morning. That is the part you cannot stitch together from off-the-shelf tools in 2-3 weeks without a team that has done it before. And because it runs inside your own AWS account, your source code never leaves your environment, which is the difference that lets regulated and high-stakes teams, banks, insurers, healthcare, and pharma, govern exactly how AI touches their software.

01

Five-layer assessment per application

Static complexity, coupling, test verifiability, change risk, AI readiness. Structured data your architects can query, filter, and prioritize from.

02

Tech debt quantified in dollars

Not a vague "high/medium/low." A number per sprint, per service. The figure that turns a technical conversation into a business case your CFO can act on.

03

AI readiness scores per service

Which services are ready for agentic tooling now, which need foundation work first, which should be retired. The map that tells you where AI will actually help and where it'll compound risk.

04

Dependency map

Every service-to-service connection, every shared database, every synchronous call chain. The map that prevents the "we didn't know these were connected" surprise at week 8 of the program.

05

Sequenced modernization roadmap

What to modernize first, what to batch, what to leave alone. Priority driven by business value, change risk, and AI readiness. Not gut feel.

06

Executive summary with business case

Tech debt cost and security and breach risk, both priced in dollars, alongside modernization investment and projected savings at 12, 24, and 36 months. Plus one overall readiness score for the portfolio. Written for leadership, not for architects.

Compass tells you what's actually in your codebase. Evolve modernizes the services Compass says are ready.

Compass is designed as the starting point, not a standalone assessment. The five-layer analysis produces the exact inputs Evolve needs to start modernizing on day one: which services to touch first, how coupled they are, and whether they're ready for AI agents.

You can run Compass without committing to Evolve. The assessment has standalone value. It answers questions your team has been debating for months with actual data. But if you do move to Evolve, Compass eliminates the discovery phase that typically adds 4-6 weeks to the front of every modernization program.

Compass → Evolve
  • Compass: 2-3 weeks. Fixed fee. Assessment and roadmap.
  • Evolve: 8-12 weeks. Fixed scope. Modernization with governed AI.
  • Compass deliverables feed directly into Evolve sprint planning.
  • MAP eligible. AWS funding available for qualifying engagements.

Seven portfolio realities Compass was built for.

You've been told modernization will take 18 months and $5M but nobody can explain exactly where the complexity sits.

You have AI tools deployed on your codebase but you're not sure they're operating on the right services first.

Your tech debt conversations stay qualitative because nobody has put a dollar figure on the cost per sprint.

You're preparing a business case for modernization and need data that finance and leadership can act on, not architecture diagrams.

You've had a modernization program stall or fail and need to understand why before committing budget again.

Your COBOL or mainframe team is approaching retirement and you need to know the real scope of what needs to move.

You've rolled out AI coding tools, but you can't yet say which codebases are safe to point them at.

The first thing we deliver isn't code. It's the picture of your codebase that nobody else has built. Every modernization decision after that is better because of it.
What customers say

When the engagement ends,
what's left in your AWS account is what counts.

JR
Jason Rackear
AWS Sr. Account Manager · the identity platform

Armakuni has been supporting the identity platform for the past 6 months and has exceeded all expectations. Charles loops me into the conversation right away. Armakuni is part of the One Team.

Identity verification · Six months of trusted delivery
EL
Engineering Leadership
Award-winning LMS provider for enterprises and mid-size organizations · Edtech

The Armakuni team demonstrated an impressive ability to earn customer trust and deliver against lofty expectations with the C-Suite. Ruben and team maintained consistent communication and delivery.

Modernization · Lifted onto AWS, owned by the customer
MS
Matt Suckel
Sr. Manager Application Integration · One of the largest cinema networks in the U.S.

Kudos to Armakuni for demonstrating the speed, precision, and partnership needed to turn a high-speed challenge into a success story.

Application integration · Speed under real pressure
TL
Technical Leadership
A Chicago-area media archive and licensing company · Media

Armakuni helped MPI build agentic AI capabilities that work inside our content pipeline. The orchestration layer sits in our AWS account, governed by our IAM, audited by our team. We own every piece of it.

Agentic AI · Owned, not rented
DT
Director of Technology
NHS Wales · Healthcare

NHS Wales needed data access measured in minutes, not days. Armakuni built the platform and transferred every piece of knowledge to our team. When they left, we ran everything.

Data platform · Full handover, no lock-in
EL
Engineering Lead
Santander · BFSI

The transformation at Santander wasn't about new tools. It was about engineering discipline that stuck after the engagement ended. 400 engineers, 40% faster time-to-market.

Engineering discipline · AK Way at scale
TD
Technology Director
Comic Relief · Public

When Comic Relief needed a payments platform for Red Nose Day that could not fail on live television, four Armakuni engineers built it. 500 transactions per second. Zero downtime.

High-stakes systems · Zero downtime delivery
Recent Results

Customers shipping in production with Armakuni.

More customer stories

Two weeks. Fixed fee.
The assessment that funds the program.

Ready to start?

Your codebase. Five assessment layers. Tech debt in dollars. In 2-3 weeks. Your first conversation is with the engineer who'd run the engagement. Not a sales exec.

Talk to an Engineer

Want to see it first?

90 minutes. Free. Compass running on a real codebase. Engineers run it. You walk away with a preliminary assessment and enough data to decide.

Book the Compass Workshop

AWS Premier Tier Services Partner

Migration And Modernization Services
Devops Consulting Competency
Amazon Eks Delivery
Aws Lambda Delivery
Aws Cloudformation Delivery
Aws Systems Manager Delivery

Active Competencies and Service Delivery Programs relevant to this offering.