Azure subscription sprawl is governance debt
How Azure tenants sprawl one decision at a time, a management-group layout a small team can run, and the order to clean up RBAC without breaking anyone.
azure · governance
statvik · from status, the state of systems
The Cloud & DevOps consultancy for desired state, reached
Senior engineers in Kerala, working worldwide. We take one scoped infrastructure problem at a time (AWS, Azure, delivery, cost), reconcile it with your team, and leave you running it without us.
- AWS
- Microsoft Azure
- Kubernetes
- Terraform
- Docker
- Grafana
- Prometheus
- GitHub Actions
Statvik in numbers
6
Clients served
7
Projects delivered
~20%
Average cloud bill cut
Tools we work in daily
Logos identify tools we use. No partnership or endorsement implied.
When teams call us
Sound familiar?
Six ways engineering teams usually find us. Every one of them has a mapped engagement behind it.
- 01The AWS bill doubled in a year and no one can point to what changed.
- 02Deploys need a senior engineer, a Slack thread, and a quiet Friday.
- 03Terraform exists, but half the infrastructure was clicked together in the console.
- 04On-call pages constantly, and almost none of it means anything.
- 05One person understands production, and they just gave notice.
- 06Kubernetes is in. Operating it was never planned for.
Services
Five practices, one method
Scoped engagements led by senior engineers, finished when your team runs the result without us.
AWS
Architecture, automation, optimization, migration, and reviews for AWS environments.
Explore
Microsoft Azure
Design, improvement, automation, and optimization for Azure environments.
ExploreDevOps
Improve how your team builds, deploys, and operates software.
ExploreCloud Cost Optimization
Find where cloud spend is wasted and what's practical to fix.
ExploreCloud & Infrastructure
Infrastructure your team can build on and operate.
ExploreNot sure which fits? Tell us what's broken and we'll point you at the right shape of engagement, or say plainly that you don't need one.
Start a conversationThe idea behind the name
From drift to desired state
Infrastructure drifts: hand-edits accumulate, costs creep, one engineer becomes load-bearing. We reconcile systems back to a state your team can hold. The name is a promise about exactly that.
drift: deploys: manual, feared, Friday-blocked
reconciled: deploys: one action, tested rollback
drift: cost: one number nobody owns
reconciled: cost: attributed, scheduled, visible
drift: on-call: pages all night, means nothing
reconciled: on-call: a page means something
drift: infra: in one engineer's head
reconciled: infra: in code, documented, handed over
drift → desired state · scoped, then handed over
How we work
The course of every engagement
Assess
Read-only access first. We map what exists (the pipeline, the accounts, the incidents) and write down where it drifts from what you need.
Reconcile
The worst pain goes first: fragile deploys, alerts nobody trusts, spend nobody owns. Changes land as pull requests your engineers review.
Hand over
Documentation, runbooks, and a session where your team drives. The engagement ends on a date we set at the start.
Then we leave. Most consultancies are built to stay; ours is built to hand over.
Pricing
You pay for the work. Only the work.
Fixed-price reviews, weekly-rate build work, a defined end either way. Senior engineers on a Kerala cost base, with no bench, no account managers, and no overhead riding on your invoice. Ask, and you get a number in the first conversation.
Scenario · illustrative composite
Deployments that depend on one person
Releases happen every other week, at night, run by the one engineer who knows the order of operations. The checklist lives in a doc that's almost current. Rollback is untested. Every release carries two weeks of changes, so every release is a big deal.
Where we'd start
- How a change travels from merge to production
- What's automated, what's scripted, what's tribal knowledge
- Test suite reliability and runtime
What typically gets better
- Any engineer on the team can run a release, on a Tuesday afternoon
- Rollback becomes a tested path instead of a theory
- Releases shrink, and each one carries less fear
Field notes
Written when we have something to say
Why your AWS bill keeps growing even when traffic doesn't
The specific mechanisms that make an AWS bill climb while traffic stays flat, and why per-team cost visibility changes behavior more than any dashboard.
aws · cost-optimization
Do you need Kubernetes?
What a Kubernetes cluster really costs to operate, what small teams should run instead, and a four-question heuristic for when it earns its keep.
kubernetes · platform-engineering
Tell us what's drifting.
Two or three sentences about your setup is plenty. You'll get a plain read on whether we can help, and what it would take.
Kerala, India · 10°N 76°E · working worldwide