Skip to main content
Workshop · AK AI SDLC

AI tooling without an operating-model change is a faster way to ship the same mistakes.

The conversation goes the same way every quarter. The operating partner asks what the AI bill is buying. The CTO points at PR throughput, agentic tool usage, ticket velocity. The number that matters, cycle time on shipped product, looks like it did before. We embed the solution architects who validate, test, and fix what your AI tools produce. That's the work that makes the rest pay back.

FREE AK-LED ONE DAY STAGES 2-4 SWEET SPOTAWS FUNDING ELIGIBLE
Trusted by teams shipping production AI on AWS
Santander
HSBC
JP Morgan
NHS Wales
the identity platform
Award-winning LMS provider for enterprises and mid-size organizations
One of the largest cinema networks in the U.S.
A leading premium wildlife stock footage platform
The Reframe

Tools don't compound. Operating models do.

Teams with clear ownership, working test coverage, and discipline about what gets shipped move faster than teams without, with or without AI. A team with the operating model in place turns throughput into cycle-time wins. A team without it ships a backlog nobody trusts. The engineering work AI doesn't do, verification, testing, the fixes that only land when someone reads the code, is what we install. The workshop is where your team learns to install it themselves.

The AI-DLC map

Every engineering team using AI is somewhere on this map.
The places teams get stuck are predictable.

Every engineering team using AI sits somewhere between Stage 1 (copy-paste from a chat tab) and Stage 5 (an internal software factory). Two stage transitions stall almost every team that hits them: the move from IDE autocomplete to agentic IDE, and the move from agentic IDE to terminal agents with their own permissions. The workshop names the stage per team, picks the target at twelve months, and walks the two transitions in between.

Five pillars, applied live

From "we have AI tooling" to "AI is paying back."

Each stage names a specific working pattern and the two stage transitions where PE-backed teams reliably stall.

Stage 1 - Manual
Stage 2 - Assisted
Stage 3 - Agentic IDE
Stage 4 - Terminal agentic
Stage 5 - Agent fleet / factory
Pillar 01 · OWASP T1

Stage 1 · Manual

Engineers copy/paste from a chat tab. AI is not in the workflow. The cost is invisible to the operating partner - hours per engineer per week in a window the CTO can't see. Most teams pass through this stage quickly once they install tooling. The ones that don't have a culture problem, not a tooling problem.

IAM · Access Analyzer · Verified Permissions · Bedrock AgentCore Policy

Pillar 02 · OWASP T2

Stage 2 · Assisted

IDE completions, semantic search, refactor tools. AI as autocomplete. PR throughput climbs because typing is faster. Cycle time on shipped product is unchanged because the operating model is unchanged. This is where the operating partner asks the AI ROI question for the first time, and where the honest answer is "wait six months and see."

Bedrock Guardrails · CloudTrail · Amazon GuardDuty

Pillar 03 · OWASP T3

Stage 3 · Agentic IDE

Cursor compose, Claude Code editor mode, VS Code agents. The agent is writing blocks, not lines, and the engineer is reviewing. Verification practice is the new bottleneck. Teams that scale here usually have written-down review heuristics or pair-programming patterns adapted for agent-pair work. Teams that don't ship a backlog of generated work that someone will have to read in six months when something breaks.

Bedrock Evaluations · Bedrock AgentCore · Step Functions

Pillar 04 · OWASP T4

Stage 4 · Terminal agentic

Claude Code, Aider, OpenHands, agentic Bedrock workflows. The agent runs from the terminal with its own permission scope. The first time a team gets here, the blast radius changes. So does the audit trail. Engineering leadership now owns governance decisions that didn't exist at Stage 3: which agents touch production, which need approval gates, which run unattended.

Bedrock AgentCore Memory · KMS · Step Functions

Pillar 05 · OWASP T5

Stage 5 · Agent fleet / factory

Ten or more agents managed by hand, or running through an internal software factory. The highest-blast-radius decisions in the maturity model sit here. The Five AK Principles, especially Observable by Default and Reversible by Requirement, become non-negotiable. Armakuni's role at this stage is governance and security advisory. Not building the factory. Installing the controls that determine whether running it is safe.

Bedrock AgentCore Policy · Verified Permissions · Lambda · Step Functions

What we bring · 5 shipping solutions

These aren't ideas. They're shipping. You'd run them inside the engagement.

Four solutions ship in customer environments today. The assessment that prices the tech debt. The orchestration layer that runs the modernization. The reviewer that reads architecture, not style. The deployment pattern for agents you can actually audit. The workshop names which two you'll lean on first.

Compass

A roadmap built from your codebase, not opinion
Two to three weeks, fixed fee. Five-layer assessment: static complexity, architectural coupling, test verifiability, change risk, AI readiness. Tech debt expressed in dollars and engineering time per sprint. Output is a sequenced roadmap your CFO can fund and your engineers can execute. AWS MAP eligible.
Compass

Evolve

Agentic modernization in your AWS account, under AK Way gates
Eight to twelve weeks, fixed scope, MAP-eligible. AK Way foundation in first, agentic orchestration layer second, agents modernize in priority order under hard gates. The orchestration layer stays in your AWS account when we leave. Repo, runbooks, commit history transferred to your engineers.
Evolve

Architecture & AI Code Reviewer

Reviews every PR against your service architecture
Reads your service architecture and runs against it on every PR. Flags reviews that need human judgment versus auto-merge eligible. Audit trail per decision, reasoned and traceable. Customised to your codebase during the POD. Hooks into GitHub, GitLab, or CodeCommit.
App & Product Dev with PODs

Agentic AI Deployment

Production agents with audit, IAM, and tool-use scoped to your environment
Bedrock AgentCore for cloud-native, OpenClaw for operational. Custom skills, enterprise integration, governance around every autonomous action. OWASP Agentic Top 10 enforced as baseline, not promised as aspiration. 88% of agents never reach production. The ones we ship do, with IAM-scoped tool use and a CloudTrail entry per autonomous action.
Gen AI & Agentic AI
How the engagement runs

One day to see it. Under ninety days to install it.

Most engineering teams don't need a six-month roadmap. They need to see the operating model land, watch a sprint run under it, and decide. The assessment is one day. The follow-on workshop is two. The forward-deployed engagement that does the work runs under ninety days, with the duration scoped to the specific stage transition the team is crossing.

Day 1
Assessment workshop
One day, AK-led, AWS-funding-eligible. Maturity-stage diagnosis per team and target stage at 12 months.
Week 1-2
Proposal and SOW
Scoped to the stage transition the team is crossing. Fixed fee. AWS MAP funding applied where eligible.
Week 3-4
2-day AIDLC workshop
Hands-on rollout of the AK Way operating model with the team that will run it. Verification, governance, and review practice installed.
Under 90 days
Forward-deployed engineer engagement
Solution architect plus offshore squad by default, single embedded architect optional. Duration scoped to the break, not the calendar.
What You Leave With

A custom path. A lens to walk it.
An engagement scoped to the first break.

Governance architecture diagram with control plane mapped per agent

Your custom path

A document plus diagram. The dominant maturity stage per engineering team. The target stage at 12 months agreed with leadership. The two stage transitions named in the order they happen. Calibrated to how your engineers split across product-facing teams and platform teams.
The Five AK Principles in Terraform and policy JSON

The Five AK Principles

Accountable by Design. Observable by Default. Reversible by Requirement. Governance as Enablement. Ownership Before Automation. Applied to every stage on your map as the working principles your verification, review, and governance practice will be measured against.

A pre-scoped FDE engagement

Five to eight weeks default, up to twelve when the stage transition is bigger than scoped. Solution architect plus offshore squad by default, single embedded architect optional. A Week 2 checkpoint to adjust shape if the team distribution shifts.

AWS funding mapped

Custom AWS funding mapped with per-control evidence collection wired to CloudWatch Gen AI Observability. Compliance becomes the side effect of the telemetry.

Discovery questionnaire output

Ten to twenty self-scored questions filled in before the workshop. Evidence-led, behaviour-based, not opinion-based. AK uses the answers to walk in with the maturity distribution and target-stage hypothesis already calibrated to your environment.

Team-level maturity snapshot

A stage score per engineering team in the room. Split by product-facing versus platform teams. The two stage transitions named per team with the order they hit them. Honest enough to put in front of the PE operating partner without footnoting.
Who Runs It

Run by a solution architect from the Gen AI Delivery Lab.
Fourteen years shipping engineering operating models.

12YRS
AK Way under audit

The AK Way refined across regulated and PE-backed engagements since 2012. Engineering operating-model practice across BFSI, healthcare, public sector.

1,300+
Engineers

AI-native delivery since LLM tooling landed in production. Agentic systems shipped in financial services, healthcare, public sector.

AgentCore
Early Access
Bedrock AgentCore Policy

Early-access partner for Bedrock AgentCore Policy, GA March 2026. We were wiring it in preview.

Premier
Security · SCA
AWS partner tier

AWS Premier tier, Security Competency, Strategic Collaboration Agreement for enterprise Gen AI.

The solution architect who runs your workshop is the same one who would audit your agent inventory. We have shipped production controls with Santander, HSBC, and NHS Wales, under FCA, PRA, and Caldicott pressure, on live systems with live auditors in the room.

What customers say

When governance is the workshop output,
the conversations afterward sound different.

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 · OWASP T1-T5 controls live
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 · AK Way managed handover
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 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
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
Recent Results

Learn from teams already shipping governed agents in production.

More customer stories
Register

One day. Your engineering teams.
The stage they're at and the path to the next.

Pick a slot. Armakuni confirms your team distribution and current AI-DLC stage ahead of time via the discovery questionnaire. The workshop produces the map, the path, and the FDE scoping. Artefacts are yours to keep, regardless of follow-on engagement.

No commitment · AWS funding eligible · You own the artefacts

Continue exploring

AWS Premier Tier Services Partner

Ai Services Competency
Aws Lambda Delivery
Amazon Api Gateway Delivery
Amazon Dynamodb Delivery

Active Competencies and Service Delivery Programs relevant to this offering.