Networking & edge

Networks, DNS and edge delivery that are fast, private where they should be, and understood.

Talk to an engineer
Problems we solve
“Our network layout can’t grow any further.”
“DNS changes are scary.”
“Staff still reach internal tools over an old VPN.”

What we do

Advise

Networking & edge consultancy

An assessment of your Networking & edge setup, with findings ranked by risk and effort.

Build

Networking & edge delivery

We design and build it with your team, in your accounts, documented as we go.

Run

Networking & edge support

Monitoring, patching and upgrades, with incident response agreed per contract.

Teach

Networking & edge training

Workshops and pairing on Networking & edge, built around your own systems.

Tools we work with

Cloud networking

  • AWS VPC
  • Transit Gateway
  • Azure Virtual Network
  • Virtual WAN
  • Google Cloud VPC
  • Cloud NAT

DNS & edge

  • Cloudflare
  • Route 53
  • Azure DNS
  • Cloud DNS
  • CloudFront
  • Azure Front Door
  • Fastly

Load balancing & proxies

  • AWS ALB / NLB
  • Application Gateway
  • Cloud Load Balancing
  • NGINX
  • HAProxy
  • Envoy

Zero-trust & VPN

  • Cloudflare Zero Trust
  • Tailscale
  • WireGuard
  • AWS Client VPN
  • Azure VPN Gateway

Protection

  • Cloudflare WAF
  • AWS WAF
  • AWS Shield
  • Cloud Armor

How an engagement runs

  1. 1 A call. 30 minutes with an engineer to understand the problem.
  2. 2 A look. Read-only access or a walkthrough, so we scope from facts.
  3. 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
  4. 4 The work. In your accounts and repositories, alongside your team.
  5. 5 A handover. Documentation and a session with your team, so you’re not dependent on us.

Proof

A recent Networking & edge engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.

See our work
Case study · anonymised
European SaaS scale-up
Challenge
Our network layout can’t grow any further. That was how the client put it on the first call.
Approach
We redesigned the network layout so it could grow, put DNS under version control, and replaced the old VPN with zero-trust access.
Stack
VPC · Route 53 · Cloudflare · zero-trust access
Result
DNS changes are reviewed like code, and staff reach internal tools without a VPN.

Questions

Do you work in our accounts or yours?

Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.

Can you work alongside our own team?

Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.

How is this priced?

Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.

Tell us what’s broken, slow or expensive.