Skip to content
Duvaryne — Duvaryne LLP

Services

What We Do

Last updated

Compute spend cut on a production EKS estate
50–60%Compute spend cut on a production EKS estateRead the case study
Less release overhead
80%Less release overheadRead the case study
Recovery time objective, multi-region failover
< 15 minRecovery time objective, multi-region failoverRead the case study
Fewer after-hours pages
90%Fewer after-hours pagesRead the case study

Four engagements, not a menu #

These are the pieces of work we take, because they are the ones we can point at evidence for. There is no fifth column here for "digital transformation" or "AI strategy" — if we have not delivered it in production, it is not on this page.

AWS Cloud #

Landing zones, migration, networking and security design, and managed support once it is live. Built as Terraform in your repository, under your account — the handover is a git clone.

Typical trigger: you are moving to AWS, restructuring accounts ahead of an audit, or you have inherited an estate nobody documented.

DevOps and Platform Engineering #

CI/CD pipelines, Kubernetes where it is warranted, GitOps, supply-chain signing, and observability that reduces pages instead of generating them.

Typical trigger: nobody on your team wants to deploy on a Friday.

Cost Optimisation #

We read your Cost and Usage Report, find the waste, and put in the controls that stop it coming back two quarters later. No percentage-of-savings pricing.

Typical trigger: your AWS bill has grown faster than your traffic and nobody can say why.

IT Consulting #

Architecture review, modernisation roadmap, security and compliance gap analysis, and managed support. Fixed-scope assessments priced before work starts.

Typical trigger: you need a decision made by someone senior who has no incentive in the outcome.

What we do not do #

We do not build websites, mobile apps or custom application software for clients. We do not resell licences. We do not do end-user IT, helpdesk or procurement. We do not take percentage-of-savings deals on cost work, because that model rewards numbers that look good for one quarter rather than ones that survive a year.

We also build our own SaaS products, but we do not build products for clients — that distinction is deliberate and we hold it.

What every engagement has in common #

Scope is written and priced fixed before work begins. Delivery is embedded — we build with your engineers and document as we go. Everything we produce is Infrastructure as Code, in your repository, under your account. There is no lock-in to us, by design.

And if the honest answer on the first call is that you do not need us yet, that is what you will hear. It costs us a small engagement and saves you a larger mistake.

Frequently asked questions

Straight answers to what technical buyers actually ask before a first call.

Which service do we actually need?

If your bill is the problem, start with cost optimisation. If shipping is the problem, start with DevOps. If you are moving to AWS or restructuring accounts, start with AWS Cloud. If you are not sure, book the free review and we will tell you which one applies — including when the answer is none of them.

Do you work on retainer or per project?

Both. Project work is scoped in writing and priced fixed before anything starts. Retainers are used where there is no in-house platform engineer to hand over to, and are priced on a fixed number of hours per month. Most clients start with a project and move to a retainer only if they want us to keep holding it.