The right infrastructure doesn’t support your team — it multiplies them.

We’re Gantry — a platform engineering practice that fixes what your team has been working around. The IaC you never wrote, the CI/CD pipeline held together with scripts, the observability you keep meaning to set up. We turn them into production-grade systems — same-day deploys, automated rollbacks, and traces that pinpoint failures in seconds.

Infrastructure is a multiplier, not a line item.

Start with an audit Learn more ↓

Every engineering team says they’ll fix the infrastructure later. Later never comes. You ship features on top of deploys that take 45 minutes, alerts that nobody reads, and a staging environment that doesn’t match production. Event-driven architecture, task queues, horizontal scaling, compression, edge networks, static analysis, real CI/CD — these aren’t things you earn at scale. They’re what makes scale possible.

We build the infrastructure that gives your engineers their time back — so every hire you make ships product, not YAML.

What we do

Three multipliers, one practice

Each one compounds. Together, they transform how your team ships.

Case Studies

Real problems we've solved

Every engagement starts with a specific pain point. Here's what that looks like in practice.

Cloud Migration Read full case study

Self-managed database to managed cloud

Problem

A self-hosted PostgreSQL cluster eating a full-time DBA’s calendar — patching, failover babysitting, 2 AM backup alerts. Pure infrastructure tax, zero product value.

What we did

Migrated to Cloud SQL with continuous replication via DMS. Terraform-managed instance, automated backups, and sub-60-second failover. Total application downtime: 90 seconds.

Result

Eliminated DBA on-call entirely and cut monthly database costs by 40%.

Cloud Migration Read full case study

Monolith to extracted services

Problem

A single Node.js monolith where one CPU-heavy module caused latency spikes across the entire product. Deploys were weekly, high-risk, and required a war room.

What we did

Applied the strangler fig pattern to extract the bottleneck into its own Cloud Run service — independent scaling, independent deploys, clean API boundary. No big-bang rewrite.

Result

Deploy frequency went from weekly to multiple times per day. The extracted service handles 3x peak load with zero manual intervention.

Cloud Migration Read full case study

Critical service rewritten in Go

Problem

A latency-sensitive eligibility service trapped inside an over-provisioned container fleet. P99 at 850ms, $320/month in compute, and scaling the fleet meant paying for capacity nothing else needed.

What we did

Rewrote the service in Go and deployed it as a Cloud Function. Compiled binary, sub-80ms cold starts, pay-per-invocation. Identical API contract — the caller just swapped the endpoint.

Result

P99 latency dropped from 850ms to 45ms. Monthly compute cost fell from $320 to $12 — a 96% reduction.

IaC Read full case study

Scheduled scaling for non-production environments

Problem

Three non-production environments running 24/7 at full capacity — $4,300/month in compute for workloads that saw zero traffic outside business hours.

What we did

Terraform-managed Cloud Scheduler policies that spin down Cloud SQL instances nights and weekends. Slack override command for off-hours work when needed.

Result

Non-production cloud spend dropped 65% — from $4,300 to $1,500/month — with no developer impact.

IaC Read full case study

Cloud IAP instead of VPN

Problem

Internal tools gated behind a VPN that took hours to set up, broke on every new laptop, and locked out the entire team when the config drifted. $18/user/month in licensing on top.

What we did

Replaced the VPN with Cloud Identity-Aware Proxy. Access controlled by Google Workspace identity and device posture — no tunnel, no client software, no certificates. Fully Terraform-managed.

Result

Onboarding dropped from 2+ hours to zero. Eliminated $9K/year in VPN licensing with a stronger security posture.

IaC Read full case study

Infrastructure as Code from scratch

Problem

Two years of cloud resources created by hand through the console. No record of what existed, who had access, or what anything cost. Onboarding a new engineer took two days of clicking through UIs.

What we did

Imported 180+ resources into Terraform without downtime. Layered state architecture, Infracost on every PR, and IAM managed as code with review-gated changes.

Result

Onboarding went from two days to a single PR. The team identified and decommissioned forgotten resources within the first week.

IaC Read full case study

IAM-based service-to-service auth on GCP

Problem

Services authenticating with shared secrets, hand-rolled JWT logic, and copy-pasted HMAC keys scattered across 17 deployment configs. No rotation, no audit trail, no way to answer “who can call what.”

What we did

Replaced all custom auth with GCP Workload Identity. Each service gets a dedicated service account; the platform issues and rotates short-lived OIDC tokens automatically. 23 hardcoded secrets removed, ~800 lines of auth middleware deleted.

Result

SOC 2 audit passed with zero auth-related findings. An entire class of credential-expiry incidents eliminated.

Observability Read full case study

OpenTelemetry for end-to-end observability

Problem

No tracing, inconsistent log formats, metrics split across four tools. Debugging a latency spike meant grepping logs on individual containers and hoping you picked the right service first.

What we did

Instrumented 8 services with OpenTelemetry — distributed traces, structured logs with trace correlation, and per-route latency metrics — all flowing to Grafana Cloud through a single collector.

Result

MTTR dropped from ~4 hours to 20 minutes. Proactive alerts caught 3 regressions before users noticed.

CI/CD Read full case study

Task queues and event-driven processing

Problem

Report generation, bulk imports, and webhook delivery all running synchronously inside API request handlers. 12-second P95, gateway timeouts, duplicate work on every retry.

What we did

Offloaded heavy work to Cloud Tasks and Pub/Sub. API endpoints return a 202 immediately; workers scale independently with retry logic and dead-letter handling. Idempotency keys prevent duplicate side effects.

Result

API P95 dropped from 12 seconds to 180ms. Webhook delivery went from 94% to 99.8%. System handles 10x throughput without scaling the API tier.

Technologies

Tools we work with

Opinionated picks, not a logo wall. Every tool earns its place by multiplying your team's output.

Infrastructure as Code

Every resource reviewable, every change auditable, every environment reproducible — IaC is the foundation that makes every other multiplier possible.

Terraform, OpenTofu, Terragrunt + 3 more

CI/CD & Delivery

A fast, reliable pipeline multiplies every engineer on your team — no deploy rituals, no war rooms, just push and move on.

GitHub Actions, GitLab CI/CD, Cloud Build + 3 more

Observability & Monitoring

You can’t improve what you can’t see — observability turns 4-hour debugging sessions into 20-minute fixes, and that time compounds across every engineer on your team.

OpenTelemetry, Cloud Trace, Cloud Logging + 5 more

Security & Zero Trust

Security that adds friction is security that gets bypassed — we wire it into the platform so it’s invisible, automatic, and on by default.

IAM-as-Code, Workload Identity, Cloud IAP + 2 more

Architecture & Edge

The right architecture decisions early are multipliers that compound forever — most teams never make them because they haven’t felt the pain yet.

Kubernetes, Event-driven architecture, Horizontal scaling + 4 more

See the full toolkit →

Process

How we work

Fixed-scope sprint, fractional role, or embedded in your team — we adapt to what you need.

01

Audit

Week 1

We map everything — cloud spend, infrastructure, CI/CD, IAM, DNS, observability gaps. You get findings ranked by impact and a remediation plan with no ambiguity.

02

Build

Weeks 2–4

We execute. Terraform, pipelines, migrations, security fixes — built, tested, and documented. Working infrastructure, not a recommendations PDF.

03

Handoff

Everything lives in code, documented with ADRs. Your team operates it from day one. We build systems that outlast the engagement.

Need us longer? We stay on as fractional engineers for as long as it makes sense.

Pricing

Straightforward pricing

Straightforward pricing. Every engagement pays for itself.

Infrastructure Audit

Full review of cloud spend, security posture, IaC coverage, and observability gaps. Prioritized roadmap with estimated savings. Starting at $5,000.

Implementation Sprint

We execute the roadmap — migrations, IaC, CI/CD, observability. Fixed scope, fixed price. Typically $8,000–$15,000 for a 2–4 week sprint.

Embedded Retainer

Ongoing platform engineering capacity. Architecture reviews, infra PR reviews, incident response, Slack access. $4,000–$8,000/month.

Audit fees are credited toward any follow-on work.

Scope your engagement

Who we are

Engineers, not consultants

Gantry is a platform engineering practice led by Dian — mathematician turned systems engineer turned startup founder.

We believe infrastructure should be a multiplier for every engineer on your team. The right CI/CD pipeline, the right architecture, the right observability — these aren’t overhead. They’re what let a 10-person team ship like a 50-person team. Most companies treat this as something to fix later. We think it’s the first thing you should get right.

We take the problems other people avoid — and we build systems that keep compounding long after we leave.

Based in Europe. Clients everywhere.

FAQ

Frequently asked questions