Skip to content
Kedgeworks

One team, in the code.

Thirty years of engineering, almost all of it inside other organisations' critical systems. Visa, Sky, the BBC, GoDaddy, Hargreaves Lansdown, Diageo, the NFL. A principal leads every engagement and stays in the codebase until handover.

What the team does

Architecture
Target architectures for systems that already carry load, and for ones being built from a brief. Microservices, event-driven work, API and aggregation layers, and the migrations that move a live platform onto them.
Delivery
The whole surface, from the front end through the services to the pipeline that ships them. React, Next.js, Node, TypeScript, .NET Core, GraphQL, Postgres.
Infrastructure
Docker, Kubernetes, Terraform, Jenkins and GitHub Actions, across Azure, GCP and AWS. We own the deploy as well as the code, because a team that cannot ship safely does not get faster by writing more of it.
Leading teams
We have run other organisations' engineering teams, built one from nothing, and taken a platform off an outsourced supplier and back in-house. Mentoring and standards are part of the engagement rather than an extra.
The founders

Grant Unwin

Founder · Rochdale

David Yates

Founder · Crewe

Grant and David founded Kedgeworks and lead the work. They have delivered on the same codebase for years, most recently at Naturecan, on the NFL and NHL platforms, and through the Missguided headless transformation.

How engagements are staffed

A principal is accountable for everything that ships, and nobody is ever billed at a level above the work they are doing.

Beyond the founders we work with a small group of developers we know and have worked with before. We bring them in when an engagement needs more hands, and a principal leads and reviews their work for its duration.

We do not publish a headcount, because it is not fixed. The bench is assembled for the engagement rather than carried as overhead, which is why we are not selling you a team we need to keep busy.

What the team works in

Ordered by how much of the work used it.

Build
  • React24
  • Node.js22
  • TypeScript18
  • Next.js7
  • Express6
  • .NET Core4
  • C#4
  • GraphQL3
  • JavaScript3
  • Astro1
  • Fastify1
  • React Native1
  • Vue.js1
Ship
  • Docker10
  • Jenkins6
  • GitLab5
  • Kubernetes5
  • AWS4
  • GitHub Actions4
  • Terraform4
  • Azure3
  • GCP2
  • Vercel1
Store
  • PostgreSQL5
  • Redis5
  • Azure SQL1
  • BigQuery1
  • Cosmos DB1
  • MySQL1
  • RabbitMQ1
Prove
  • Jest16
  • Playwright5
  • Cypress3
  • Selenium2
  • Grafana1
  • K61
  • Lighthouse CI1
  • Prometheus1
  • Sentry1

The numbers count published case studies, so they understate the total. Anything we have used once on one engagement is not on this list.

“A valuable asset to our team in the time he worked with us, he proved himself to be dependable, a hard-worker, and brought an impressive level of expertise to the team. I was always impressed by Grant’s ability to quickly understand complex requirements, and deliver elegant solutions quickly and at a very high quality.”
Adam Dodds, Head of Engineering, Missguided

Talk to the person who would run it.