ED CONSULTING GROUP

Capability statement

What we do,
in full.

A complete view of where we work, what we deliver, and how engagements are structured. Written for the person who has to justify the decision internally.

At a glance

Core focus
Cloud architecture, platform engineering, reliability, and security for organisations running on AWS, Google Cloud and Azure.
Engagement model
Remote, contract or corp-to-corp. Fixed-scope projects, retained advisory, or embedded delivery alongside your team.
Seniority
Every engagement led by an engineer with 20+ years of production experience. No pyramid staffing.
Delivery format
Infrastructure as code in your repositories, documentation, and a handover session. You own all of it.
Typical start
A scoped first piece of work, usually two to six weeks, that stands on its own and proves the fit.

Core competencies

What we are engaged to do.

Cloud architecture and landing zones

Organisation and account structure, network topology, identity and access design, and the guardrails everything else inherits. Delivered as Terraform, with the decisions written down.

  • Multi-account and multi-project foundations
  • Network and connectivity design
  • Identity federation and IAM models
  • Migration planning and execution
  • Cost structure and tagging discipline

Platform and DevOps engineering

The paved road your engineers actually want to use: reproducible environments, pipelines that tell the truth, and self-service that does not require a ticket.

  • Terraform modules and reusable patterns
  • CI/CD pipeline design and hardening
  • Kubernetes platform build and operations
  • Developer self-service tooling
  • Release and environment strategy

Reliability and SRE

Turning uptime from a hope into a measured property. Service levels defined against what users actually feel, with the observability to prove it.

  • SLI and SLO definition
  • Observability, tracing and alerting
  • Incident response and postmortem practice
  • Sustainable on-call design
  • Capacity and failure testing

Security and compliance

Least privilege that survives contact with delivery pressure, and control evidence that is produced by the system rather than assembled the week before an audit.

  • IAM and least-privilege design
  • Policy as code and guardrails
  • Secrets management and key handling
  • Audit readiness and control mapping
  • Security review of existing estates

Technical environment

Cloud
Amazon Web Services, Google Cloud Platform, Microsoft Azure
Infrastructure as code
Terraform, OpenTofu, CloudFormation, Pulumi
Containers and orchestration
Kubernetes, EKS, GKE, AKS, ECS, Cloud Run
CI/CD
GitHub Actions, GitLab CI, Argo CD, Jenkins, Cloud Build
Observability
Prometheus, Grafana, OpenTelemetry, Datadog, Cloud-native stacks
Data and storage
PostgreSQL, managed SQL services, object storage, backup and recovery design

Why teams pick us

You get the senior engineer

Not a sales team followed by whoever is on the bench. The person in the first call is the person in the pull request.

Priced without the overhead

A lean remote team has no offices, no bench and no layers to fund, and that shows up in what we charge.

Built to be handed over

Every engagement ends with your team able to run and extend the work. That is the deliverable, not a retainer.

Honest about fit

If your problem is smaller than you feared, or outside what we do well, we tell you in the first conversation.

Ready to scope something?

Bring the messy version. Scoping it properly is part of the work.

Talk to the assistant Send a message