Infrastructure & Networking

Infrastructure & networking

The engineering behind the hosting, available on its own

Private cloud platforms, networks, DNS and migrations. Project work for organisations whose requirements have outgrown a control panel, delivered by the people who run our own infrastructure.

What we take on

Four kinds of work


Private cloud and virtualisation

Proxmox clusters from a single node to something properly redundant: shared or replicated storage, high availability, backup and restore that has been tested rather than assumed, and capacity planning that leaves room to grow.

Networking

Routing and firewalling, site-to-site links, overlay networks for remote staff and sites, VLANs and segmentation, and remote access that doesn’t mean exposing RDP to the internet.

DNS and email deliverability

Authoritative DNS, split-horizon setups where internal and external answers differ, and untangling the SPF, DKIM and DMARC problems sitting behind mail that quietly stopped arriving.

Migrations and repatriation

Moving workloads off a hyperscaler whose bill has got out of hand, off ageing hardware, or off a host you’ve outgrown. Written cutover plan, tested rollback, scheduled downtime if any is needed at all.

How we work

Documented, handed over, not held hostage


Scope before quote

We look at what exists first. The proposal describes what will be built, what it will cost, and what is explicitly out of scope.

Built to be understood

Configuration is version-controlled where it can be, and you get the diagrams and documentation at handover, not on request.

Yours afterwards

You can keep us on to run it, hand it to your own team, or give it to someone else. Nothing is locked to us on purpose.

Who it suits

When this is the right call

  • Your cloud bill has grown past what the workload is worth and you want to know what running it yourself would actually cost.
  • You have one server doing everything and no tested way to recover it.
  • You’re opening a second site and the network needs to join up properly rather than over a consumer VPN.
  • Something works, but nobody left at the company knows how, and it isn’t written down anywhere.
  • You need an engineer for a defined piece of work, not a monthly retainer for support you won’t use.

Describe the problem

A paragraph about what you’re running and what isn’t working is enough to start. If it isn’t something we should take on, we’ll say so.

Scroll to Top