Modernization + FinOps.
On Forge, on AWS EKS.
A leading software and market intelligence company consolidates CloudBees CI, GitLab, SonarQube, and JFrog onto one FinOps-disciplined Forge Managed Runtime on AWS EKS — workload-separated, cost-controlled, and governance-ready for the AI workloads coming next.
CUSTOMER PROFILE
- Marketing Technology · Market Intelligence
- AWS EKS-resident DevOps toolchain
- Operating globally
THE ENGAGEMENT
Workloads separated. Cost controlled. Audit ready.
“Forge gave us one runtime, one SLA, and one audit trail across CloudBees, GitLab, SonarQube, and JFrog — modernized, FinOps-disciplined, and governance-ready.”
— Director of Platform Engineering(paraphrase, pending customer approval)
The toolchain before
Despite running a mature CloudBees CI environment on AWS EKS, the company’s broader DevOps toolchain — CloudBees controllers and agents, GitLab runners, SonarQube analysis pods, JFrog Artifactory — was sharing node capacity, scheduling logic, and FinOps fate. Cost analysis surfaced over-provisioning. Peak loads surfaced instability.
What the company needed
Not a platform replacement. A structured modernization within the runtime they already trusted — one that would let each workload class in the toolchain (controllers, build agents, SonarQube analysis, JFrog artifact services) scale and be governed on its own terms, with FinOps discipline applied uniformly.
How iTmethods engaged
Engagement began upstream — utilization review across all four tools, then staged modernization within the existing AWS EKS environment with no changes to instance types or Savings Plan commitments. A Forward Deployed Engineer owned design, staging validation, and production cutover. Zero disruption to live pipelines.
THREE MOTIONS ACROSS THE TOOLCHAIN
Modernization. Optimization. Governance-ready.
01 · MODERNIZATION
One managed runtime on AWS EKS
CloudBees CI, GitLab, SonarQube, and JFrog Artifactory + Xray consolidated under Forge Managed Runtime on AWS EKS. Kubernetes labels, taints, and tolerations route every workload class to the right pool automatically.
DELIVERED
- CloudBees on isolated controller pool
- Build agents — scale-to-zero pool
- GitLab runners — dedicated pool
- SonarQube analysis — on-demand pool
- JFrog Artifactory — stable pool
02 · OPTIMIZATION
FinOps as a property of the runtime
Workload separation identified through structured AWS architecture review. No changes to existing instance types, ARM64 node group, or Savings Plan commitments. Staged cutover with zero production disruption.
OUTCOMES
- Workload separation across the chain
- Agents + analysis scale to zero
- Savings Plan commitments intact
- Zero production disruption
03 · GOVERNANCE-READY
Evidence streams ready for Reign
The modernized toolchain emits structured evidence — GitLab MR audit, SonarQube quality gates, JFrog Xray vulnerability + SBOM, CloudBees release records — ingest-ready for Reign's Evidence Engine when deployed.
EVIDENCE STREAMS
- Change-management — GitLab MR audit
- Code quality — SonarQube gates
- Vulnerability + SBOM — JFrog Xray
- Release evidence — CloudBees
- All ingest-ready for Reign
NEXT STEPS
Modernize. Optimize. On Forge.
Take the next step toward governed AI. Every day without visibility is another day of unaudited AI actions and blind spend.
Assess
Architecture and FinOps review across CloudBees, GitLab, SonarQube, JFrog on EKS.
Modernize
Workload-separate the toolchain on Forge — zero disruption, Savings Plans preserved.
Govern
Deploy Reign over the same runtime — runtime policy + audit-grade evidence.
INCLUDED WITH FORGE
- Full audit trail of every AI agent action
- MCP connection governance and approval workflows
- Real-time cost dashboards with token-level visibility
- 24/7 enterprise support with dedicated TAM
SOC 2 Type II Certified · 100+ Enterprise Customers · 20+ Years Enterprise Trust