Home/AWS Partnership/Alliances
Technology alliancesWe work with your stack, not against it.
An MSP that requires you to adopt its tooling is selling lock-in with a service wrapper. We operate whatever you already run, and recommend changes only where the arithmetic supports it.
Three commitments on tooling
No mandatory stack
We do not require you to adopt a monitoring platform, a ticketing system or a security product to be our customer. We have operated all of the major options and will work in yours.
No vendor commissions
We do not take referral fees or resale margin on third-party tooling. If we recommend a product, our only interest is that it makes your estate cheaper or safer to run.
Licences stay yours
Any tooling we deploy is licensed to you, in your tenancy, under your contract. Nothing we install stops working because you stopped being our customer.
What we run in production across our customer base
Listed because customers ask what we have real operating experience with — not as endorsements, and not as partnerships unless stated.
Observability
Our default recommendation is OpenTelemetry instrumentation regardless of backend, so a future change of vendor is a configuration change rather than a re-instrumentation project.
Infrastructure as code & delivery
Terraform is our default for infrastructure. Where a customer has standardised on CDK we work in CDK rather than force a migration that returns nothing.
Security & compliance
Compliance automation platforms are genuinely useful for evidence collection. They are not a substitute for the controls themselves, and we will say so if one is being used that way.
Data & analytics
Where customers run Snowflake or Databricks we manage the AWS foundations underneath — networking, identity, storage, cost and security — and integrate rather than compete.
Service management
We integrate into your service desk where you have one, so incidents and changes appear in your system of record rather than only in ours.
Networking & edge
Including the appliance-based estates that come with a data centre exit and cannot simply be replaced with a native service on day one.
All product and company names are the trademarks of their respective owners. Listing does not imply a formal partnership, endorsement or resale arrangement unless stated explicitly.
You will usually have more than one supplier
Most estates we join already have an application development partner, a managed network provider, an endpoint and identity team, and sometimes an incumbent integrator mid-programme. That is normal and we plan for it.
What matters is that boundaries are written down: who owns the change, who is on the bridge during an incident, and who makes the call when a decision cannot wait. Ambiguity there is the single most common cause of a bad night.
How we workIndependent testing
We deliberately do not penetration test our own configurations. An independent tester is worth far more to you than a convenient one, and any provider offering to test the thing they built is offering you comfort rather than assurance.
We scope the engagement, introduce firms we have worked with, take no referral fee, and remediate what they find.
Tell us what you already run
We will tell you honestly what we would keep, what we would change, and what we would leave well alone.