---
title: "argo-cd"
lang: "en"
author: "Mohammad Abu Mattar"
canonical: https://mkabumattar.com/tags/argo-cd
---

[All Tags](/case-studies/tags)

# #Argo cd

[Home](/)›[All Case Studies](/case-studies)›[All Tags](/case-studies/tags)›[Argo cd](/case-studies/tags/argo-cd)

Tag

# #Argo cd

CategoryAllDevOps (5)Cloud Native (4)Cloud Computing (3)Architecture (2)Databases (1)Platform Engineering (1)Reliability (1)Security (1)TagAllKubernetes (3)Argo CD (2)EKS (2)GitOps (2)Active Active (1)Argo Rollouts (1)ArtifactHub (1)AWS (1)Backstage (1)Containers (1)Cosign (1)Cost Optimization (1)Cutover (1)Database Migration (1)Failover (1)FinOps (1)Golden Paths (1)Helm (1)High Availability (1)Idempotency (1)Internal Developer Platform (1)Logical Replication (1)Microservices (1)Migration (1)Multi Region (1)Payments (1)PostgreSQL (1)RDS (1)Rollback (1)RPO (1)RTO (1)Savings Plans (1)Self Service (1)SLSA (1)Strangler Pattern (1)Supply Chain Security (1)Terraform (1)Traffic Shifting (1)Trivy (1)Wolfi (1)Zero Downtime (1)SortNewest firstOldest firstA to ZShortest read first

[![Building an Internal Developer Platform on Backstage and GitOps](/_astro/hero.Dq3xrist_1gdSPN.webp)](/case-studies/post/internal-developer-platform-backstage-gitops)

## [Building an Internal Developer Platform on Backstage and GitOps](/case-studies/post/internal-developer-platform-backstage-gitops)

-   [DevOps](/case-studies/categories/devops)
-   [Platform Engineering](/case-studies/categories/platform-engineering)
-   03 Aug 2026
-   09 Mins read

Product teams were spending more time waiting on the platform team than building features. Spinning up a new service meant opening a ticket and waiting for someone to provision a repo, wire up CI, wri

[#Backstage](/case-studies/tags/backstage)[#GitOps](/case-studies/tags/gitops)[#Argo CD](/case-studies/tags/argo-cd)+4 tags

[Read Case Study](/case-studies/post/internal-developer-platform-backstage-gitops)

[![Cutting a SaaS AWS Bill 41% Without Slowing Delivery](/_astro/hero.DJTB593d_Z1iASgs.webp)](/case-studies/post/aws-cost-optimization-saas-case-study)

## [Cutting a SaaS AWS Bill 41% Without Slowing Delivery](/case-studies/post/aws-cost-optimization-saas-case-study)

-   [Cloud Computing](/case-studies/categories/cloud-computing)
-   [DevOps](/case-studies/categories/devops)
-   19 Jul 2026
-   10 Mins read

A growing SaaS ran on EKS with a full GitOps pipeline, and it was over its AWS budget nearly every month. The reflex from leadership was the usual one: freeze features until the bill comes down. That

[#AWS](/case-studies/tags/aws)[#EKS](/case-studies/tags/eks)[#Kubernetes](/case-studies/tags/kubernetes)+7 tags

[Read Case Study](/case-studies/post/aws-cost-optimization-saas-case-study)