Skip to main content

Partners

Partnerships you can check for yourself

A partner badge is worth what you can verify. Where we hold an entry in a programme's public register, this page links straight to it so you can read what they say about us rather than what we say about ourselves, and where we do not hold one yet, it says that instead of implying otherwise.

Describe the workSee what we do
AWSAWS Partner Network
AWS

AWS

AWS Partner Network

We are registered in the AWS Partner Network. AWS reserves recognition as an AWS Partner for members who meet the requirements of one of its Paths, and we have not, so registered is the accurate word. It gives us partner training, technical resources and a route to AWS when a customer environment needs scoping.

What we do with it

  • AWS accounts, identity and networking run as day-to-day operations rather than a side job
  • Architecture reviewed against what the company will need next, not only what it runs today
  • Security and access built the way an auditor will eventually read them
  • Cost audits that find the spend nobody has looked at, with governance so it stays found

No public register at this level

Why we chose AWS
DigitalOcean logo

DigitalOcean

DigitalOcean Partner Pod

We are a member of the DigitalOcean Partner Pod, with access to the partner portal and the opportunity registration used to scope customer workloads.

What we do with it

  • Managed Kubernetes on DOKS, from a first cluster to production hygiene
  • Moving workloads between DigitalOcean and the larger clouds, in both directions
  • Cost and architecture reviews for teams deciding which platform fits their stage
  • Droplets, managed databases and Spaces run as day-to-day operations rather than a side job
Find us in the DigitalOcean Partner DirectoryWhy we chose DigitalOcean
GitLab logo

GitLab

GitLab Channel Partner Program · Track: Open

We are listed in GitLab's Authorized Partner Locator, which is the register GitLab points customers at when they want someone to implement, migrate or run the platform for them.

What we do with it

  • Migrations onto GitLab, including the CI rewrite that no importer does for you
  • Self-managed GitLab on Kubernetes: upgrades, runners, backups and restore drills
  • GitLab CI pipelines your team will actually maintain after we leave
  • Licensing and tier questions answered before you buy rather than after
Find us in the GitLab Partner LocatorWhy we chose GitLab

All product names, logos and brands are the property of their respective owners, used here only to identify each partner programme. Nothing here implies that any of them endorses our services.

What a partnership changes, and what it does not

Being in a partner programme gives us a route to the vendor when something needs escalating, early sight of changes, and training that keeps the answers current. It does not make us neutral about their products, and it does not mean a partner platform is the right answer for you. We work well beyond the platforms we are partnered with, precisely so the recommendation can follow the workload rather than the badge.

In practice it means a route to the vendor when a ticket stalls, and answers about tiers, limits and upgrade paths that are current rather than remembered from last year.

What the partnerships cover

The work behind the badges

A programme membership is only useful through the work it sits behind. These are the engagements where being in the vendor's programme changes the answer you get.

AWS Cloud ManagementAWS only, in depth, run day to day rather than when it breaksOpenArchitecture and PlanningDecisions made once, drawn so the next team can read themOpenSecurity and ComplianceAccess, separation and evidence, before an auditor asksOpenCloud Cost OptimizationWhat the platform is charging you for, and whether you use itOpen