soft guideINFRASTRUCTURE & ADVISORY

Independent engineering. Clear direction.

Infrastructure
you can trust.

Hands-on DevOps and cloud engineering, with security built into the conversation. Practical help for your AWS infrastructure, Kubernetes, and delivery workflows.

Discuss your infrastructureSee the platform ↗
A focused technical scopeAWSKubernetesTerraformGitOpsSecurityAI agents

01 / How I can help

Clarity first.
Better systems next.

From an independent review to hands-on implementation, get advice that connects infrastructure decisions to how your team actually works.

01AWS architecture & operationsMake the architecture fit the workload. Understand cost, resilience, and the trade-offs behind each decision.02Kubernetes, made operableReview cluster configuration, workload boundaries, and day-to-day operations. Build a clearer path to hardening.03Security posture & guidanceTurn IAM, configuration, and network findings into specific actions your team can implement.04Delivery & infrastructure as codeCreate repeatable infrastructure and reviewable delivery workflows, with a sensible path back when changes fail.

02 / The platform

Infrastructure,
as a product.

No infrastructure and no lifecycle yet? Get a production-grade, secure AWS and Kubernetes platform built from a tested baseline, in your accounts, as your own code. Add agents that watch it and propose the fixes.

01

Launch

You have a product. You need somewhere production-grade to run it.

02

Secure

Everything in Launch, plus the controls auditors and attackers both test first.

03

Autonomous

Everything in Secure, plus agents that watch the platform and propose the fixes.

03 / Selected work

Built before
it was sold.

Case studies from the platform behind Soft Guide: cells, a single controlled exit to the internet, declared network access, guardrails, and an AI SRE agent that never acts alone.

01

A new region is a new cell, not a bigger cluster

A platform that grows by adding identical, isolated cells: one VPC and one cluster each, built from one module and handed to GitOps through a single ConfigMap.

  • AWS
  • Terraform
  • Terramate
  • Kubernetes
  • GitOps
  • Flux
02

One way out to the internet

Every outbound connection from a cluster leaves through a single gateway that allowlists hostnames, behind three independent fences: routing, CNI policy and an L7 proxy.

  • AWS
  • Kubernetes
  • Cilium
  • Envoy
  • Security
07

An on-call engineer that never acts alone

An AI SRE agent inside the cluster: it investigates every alert with read-only tools, reports cause and evidence in chat, and changes nothing without a human approval checked in code.

  • AI agents
  • Observability
  • Kubernetes
  • Security
All case studies

04 / Security is part of the work

Understand the risk.
Know the next step.

Good infrastructure advice goes beyond a list of findings. It explains what matters, why it matters, and how to move forward.

Explore security advisory
Look at the configuration.
Review access, exposure, and operating practices in the context of your system.
Make the trade-offs clear.
Balance risk, reliability, implementation effort, and ongoing cost.
Leave a usable roadmap.
Translate findings into specific, prioritized changes and clear ownership.

05 / A practical engagement

From a question
to a way forward.

01

Understand the system

We agree on the question, scope, access boundaries, and what a useful outcome looks like. Existing diagrams, configuration, and team context come first.

02

Review & prioritize

Review the relevant architecture and configuration. Document findings with context, impact, effort, and the decisions they support.

03

Improve & hand over

Work through agreed changes or equip your team to implement them. Leave a prioritized roadmap, clear documentation, and a practical handover.

Start a conversation

Bring your infrastructure
into focus.

Tell me what you are building, operating, or trying to improve.

Let’s talk