Skip to main content

SaaS Platform Scaling and Cost Optimization on Amazon EKS

A Singapore CRM SaaS moved to GitOps on Amazon EKS with ArgoCD, Helm and GitLab CI: 38% lower cloud cost, zero-downtime deploys, 99.95% uptime.

  • Cost optimization
  • Enterprise SaaS
  • Singapore
  • AWS
Monthly cloud spendindexed to the starting month-38%Amazon EKS node poolrightsized and consolidated38% cost reductionZero deployment downtime99.95% uptime
Spend falls as the EKS node pool is rightsized and idle nodes are retired.
cloud cost reduction
38%
deployment downtime
Zero
uptime
99.95%

At a glance

Engagement
Cost optimization
Platform
AWS
Region
Singapore
Client
CRM and workflow automation platform, name withheld
Technologies
6 in the delivered stack

Before and after

A CRM and workflow automation SaaS suffered frequent downtime during deployments, had little visibility into cloud cost, and ran misaligned development, UAT and production environments.

Before

  • Make deployments safe enough to run without customer-facing downtime.
  • Bring dev, UAT and production onto one consistent, declarative setup.
  • Make cost visible and bring it down without hurting reliability.

After

  • 38% cloud cost reduction
  • Zero deployment downtime
  • 99.95% uptime

The solution

Solution path

  1. GitLab CI
  2. Helm
  3. Argo CD
  4. Amazon EKS

How it was delivered

  1. Phase 1

    GitOps architecture with ArgoCD, Helm and GitLab CI.

  2. Phase 2

    Amazon EKS with separate namespaces per environment.

  3. Phase 3

    Savings Plans, rightsizing and auto-scaling.

Technology stack

  • Amazon EKS
  • ArgoCD
  • Helm
  • GitLab CI
  • AWS Savings Plans
  • Kubernetes autoscaling

Questions about this project

How was the SaaS cloud bill reduced by 38%?

Through AWS Savings Plans, rightsizing of workloads and auto-scaling on Amazon EKS, combined with the cost visibility that came from consolidating environments.

What GitOps tooling did the SaaS platform use?

ArgoCD for continuous delivery from Git, Helm for packaging Kubernetes applications and GitLab CI for build and test pipelines.

Related technical articles

Planning something similar?

Whether you're migrating, cutting costs, securing your infrastructure or exploring startup programs, start with the Cloud Readiness Survey.

What happens next

  1. Answer six questions about your cloud setup, spend and priorities. It takes about three minutes.
  2. A Celestibia engineer reviews your answers within one business day.
  3. You get tailored recommendations and the AWS programs you are likely to qualify for.

Monday to Friday, 10 AM to 7 PM IST