Cloud infrastructure & DevOps
Infrastructure as code, deployment pipelines, observability, and cloud cost control — sized to the team that runs them, from senior engineers who have run production at scale.
Last updated:Cloud infrastructure and DevOps consultancy covers the platform an application runs on: infrastructure as code, deployment pipelines, observability, and cloud spend. Revenant Systems builds and reviews cloud infrastructure with Terraform and Terragrunt on AWS and Azure, and runs GitOps delivery on Kubernetes with Helm and ArgoCD — where that fits the team and the product.
What does infrastructure as code cover?
Infrastructure as code defines cloud resources — networks, compute, databases, permissions — in version-controlled configuration instead of hand-edited consoles, so environments are reproducible, reviewable, and recoverable. Revenant Systems writes infrastructure as code in Terraform, with Terragrunt to keep multi-environment and multi-account estates maintainable.
The founder has built and run Terraform-managed estates on both AWS and Azure in prior roles, using plain Terraform and Terragrunt as each estate warranted.
- Terraform and Terragrunt
- AWS and Azure
- Multi-environment and multi-account layouts
- Codifying existing hand-built estates
What is GitOps, and why use it for Kubernetes delivery?
GitOps is a deployment model in which the desired state of a Kubernetes cluster lives in Git and an operator such as ArgoCD keeps the cluster matched to it — every change reviewed, versioned, and reversible. Revenant Systems builds GitOps delivery on Kubernetes with Helm charts and ArgoCD.
In prior roles the founder deployed and ran ArgoCD-driven GitOps on EKS, managing production services and a full observability stack through Helm charts and Git.
- Kubernetes (EKS)
- Helm
- ArgoCD
- CI/CD pipelines
Can you reduce our cloud costs?
Usually, yes. Cloud estates that have grown organically tend to carry over-provisioned compute, idle environments, and architecture priced for a scale that never arrived. A cloud cost review applies Revenant's audit-first methodology to spend: measure what the estate actually does, then re-architect the expensive parts with evidence.
In a previous role the founder led a cloud-spend redesign that cut a platform's AWS infrastructure costs by around 60% while its traffic doubled.
- Audit-first spend review
- Right-sizing compute and storage
- Architecture-level savings, not instance tweaks
Observability: metrics, logs, and dashboards
Observability is being able to see what production is doing — metrics, logs, and dashboards that answer questions during an incident, not after it. Revenant Systems builds observability on VictoriaMetrics and Grafana for metrics and dashboards, with Grafana Loki for log aggregation, deployed and managed as code.
In prior roles the founder deployed and managed VictoriaMetrics, Grafana, and Loki — run via Helm and ArgoCD — as the observability stack for platforms processing billions of events a month.
- VictoriaMetrics
- Grafana dashboards and alerting
- Grafana Loki log aggregation
Does every project need Kubernetes and Terraform?
No. Infrastructure should be sized to the team that runs it: a three-engineer startup rarely needs the platform a fifty-engineer organisation does. Revenant Systems recommends Kubernetes, Terraform, or GitOps only where the audit shows they pay for themselves, and works cleanly with whatever infrastructure you already have.
What's included
- Terraform / Terragrunt infrastructure as code (AWS, Azure)
- Kubernetes deployment and GitOps (EKS, Helm, ArgoCD)
- CI/CD pipelines
- Observability: metrics, logs, dashboards
- Cloud cost review and right-sizing
Stack Terraform · Terragrunt · AWS · Azure · Kubernetes · Helm · ArgoCD · Grafana
Frequently asked questions
Which cloud platforms do you cover?
AWS and Azure, managed through Terraform — with Terragrunt where multi-environment or multi-account estates warrant it. The founder has built and run Terraform-managed estates on both platforms in prior roles; the tooling recommendation follows the estate, not a preference.
Our infrastructure was built by hand — can it be brought under code?
Yes — codifying existing hand-built estates is part of the service. The work brings the estate under version-controlled Terraform configuration, so environments become reproducible, reviewable, and recoverable rather than dependent on console memory.
How much could we save on our cloud bill?
The audit-first answer: measure before promising. Estates that grow organically tend to carry over-provisioned compute, idle environments, and architecture priced for a scale that never arrived. In a prior role the founder led a redesign that cut a platform's AWS costs by around 60% while traffic doubled; the fixed-scope cloud cost audit establishes what your estate can support.
Do you provide monitoring and alerting?
Yes — observability is part of the service: VictoriaMetrics and Grafana for metrics and dashboards, with Grafana Loki for log aggregation, deployed and managed as code alongside the rest of the estate — so production questions get answered during an incident, not after it.
Can you set up our Kubernetes delivery?
Yes — Revenant Systems builds GitOps delivery on Kubernetes with Helm charts and ArgoCD, keeping the cluster matched to Git so every change is reviewed, versioned, and reversible. Handover includes the documentation and access your team needs to run it independently.
We already have infrastructure — can you work with it?
Yes. Revenant Systems recommends Kubernetes, Terraform, or GitOps only where the audit shows they pay for themselves, and works cleanly with whatever you already run. Infrastructure is sized to the team that operates it, not to a reference architecture.
Every engagement follows the same process — see how we work.