Overview
Industry: Network Automation (SaaS)
Geography: Global
Technologies: AWS Fargate, ECS, GP3 Storage, Reserved Instances
The Situation
Criterion Networks builds and operates a SaaS platform in the network automation space and its entire infrastructure runs on AWS. Growth brought scale, but it also brought a familiar problem: cloud costs were climbing, and not all of that spend was earning its place.
The AWS environment had grown organically. Project environments stayed running after projects ended. Storage volumes sat on legacy tiers that were never revisited. Compute was sized for peak demand that rarely materialised. And without a consistent tagging framework, there was no clear picture of what was driving costs or who owned it.
For a SaaS company, infrastructure efficiency directly affects unit economics. Every dollar of unnecessary cloud spend is a dollar not available for product investment or margin. Criterion needed immediate savings and the operational discipline to sustain them.
What Codincity Did
Codincity audited the Criterion AWS environment and structured the optimisation work across four areas:
Mapped all running resources against active business need and decommissioned redundant environments test setups, staging replicas, and forgotten deployments without impacting live services.
Migrated legacy EBS volumes to GP3, delivering higher baseline IOPS at a lower price point and an approximately 20% reduction in storage costs with no service disruption.
Transitioned compute workloads to Amazon ECS with AWS Fargate, shifting from fixed EC2 provisioning to a consumption-based model aligned to variable SaaS demand. Reserved capacity commitments on steady-state workloads delivered a further 20% reduction in compute costs.
Implemented a smart tagging framework across the AWS environment, attributing every resource to a team, project, or cost centre replacing guesswork with accountability.
Business Impact
20% reduction in overall AWS spend through the combined effect of environment consolidation, storage migration, compute optimisation, and reserved capacity.
Improved platform performance from GP3 storage better IOPS at lower cost than the legacy volumes they replaced.
Full cost attribution across teams and projects through the tagging framework, giving leadership clear, ongoing visibility into spend.
A scalable, governed infrastructure that grows with the business without proportional cost increases.
What It Means Going Forward
The 20% saving translates directly into resources Criterion Networks can redirect toward product development and growth. More importantly, the governance framework Codincity put in place means those savings are sustainable not a one-time event that erodes as new resources are provisioned.
Criterion now manages cloud costs as a discipline, not a reactive exercise. The visibility and controls are in place to keep it that way.
Conclusion
Sustainable cloud optimization requires more than cost-cutting—it requires visibility, accountability, and governance. By combining infrastructure modernization with FinOps best practices, Codincity helped Criterion Networks reduce AWS spend, improve operational efficiency, and establish the controls needed to manage cloud costs as the business scales. The result is a more efficient, future-ready platform that supports growth without unnecessary expenditure.
