Scope, fee and working days are published on every engagement
Infrastructure assembled by hand cannot be reviewed, rebuilt or handed over. These engagements move environments into code, put every change behind a pull request and leave runbooks your own team can follow.
Practice readout
CLD Working principle
If an environment cannot be recreated from the repository, it is a risk. Every engagement here reduces the number of things only one person knows how to do.
02 Engagements
Your AWS environment defined in versioned Terraform with separate accounts and scoped IAM, so every infrastructure change is reviewed.
Terraform modules for IAM, VPC networking, subnets, security groups and core services
Fixed fee · GST incl.
₹44,999
Duration
25 working days
A line-by-line review of your AWS bill that returns ranked savings with rupee values and risks, so cost cuts never endanger production.
Line-by-line breakdown of three months of AWS spend
Fixed fee · GST incl.
₹12,999
Duration
6 working days
A GitHub Actions pipeline that tests every pull request and deploys with approval and rollback, so releases stop relying on one person.
Pull request checks for linting, unit tests and a successful build
Fixed fee · GST incl.
₹18,999
Duration
8 working days
Blue-green or rolling releases with health checks and automatic rollback, so you ship in working hours without taking the product offline.
Blue-green or rolling deployment on ECS, Kubernetes or EC2
Fixed fee · GST incl.
₹29,999
Duration
14 working days
Network policy, RBAC, resource limits, secrets handling and image scanning applied to a live cluster, closing its default security gaps.
Network policies that deny by default and allow only named traffic per namespace
Fixed fee · GST incl.
₹34,999
Duration
15 working days
IDX Other practices
Next step