For delivery partners

The cloud platform layer, delivered alongside your engagement.

For agencies, fractional CTOs and consultancies who have the client relationship and need senior platform engineering underneath it. We take a defined workstream, work in the client’s repositories through your process, and hand over so the work outlives all of us.

Discuss an engagement The problems we take on

Your client's stack, not ours

01Defined inIaC

Terraform
CloudFormation
AWS CDK
Pulumi
Other IaC

02Shipped byCI/CD

GitHub Actions
GitLab
Azure DevOps
Argo CD
Other pipelines

03Runs onCloud

AWS
Kubernetes
Docker
Other platforms

04Watched byObservability

Datadog
Prometheus
Grafana
Other tooling

+ more we work with

AzureGoogle CloudOpenTofuTerragruntHelmJenkinsVaultPackerAnsibleCloudflarePostgreSQLRedisSentryNGINXand what your team already runs

How it works

Three arrangements, described as work rather than as tiers.

There is no partner programme to join and no badge to display. Each engagement is scoped in writing on its own terms.

Alongside a product build

You are building the product. The platform underneath it is not your team’s job.

An agency delivering an application often inherits the cloud account it runs in, and the unloved parts — accounts, identity, networking, pipelines, backups — land on whoever is nearest. We take that layer as a defined workstream, in the client’s repositories, so your engineers stay on what you were hired for.

Typically: environments, deployment path, access boundaries, observability, handover

Behind a fractional CTO

You have diagnosed it. You need senior hands, not another opinion.

A fractional or interim CTO may already know what the estate needs and have no capacity to build it. We deliver against your plan rather than re-running the diagnosis, and we are content for the recommendation to stay yours — including when it is to do less than we would be paid for.

Typically: a named workstream from your own backlog, with your acceptance criteria

Beside another consultancy

The engagement needs a specialism that is not what you sell.

Data, security, product and application consultancies all hit the same boundary: the cloud platform the work has to land on. We take that piece, scoped in writing, and we do not sell around it into the rest of your account. If the client later asks us about work that is plainly yours, we say so.

Typically: landing zone, IaC adoption, delivery pipeline, recovery

Who carries what

The division of responsibility does not change because you are in the room.

Your client still approves every plan that gets applied — which is the reason an introduction is low risk for the relationship you own.

Your client keeps

Every decision that binds their business

The repositories, and what gets merged
Approval of the exact plan that is applied
Production authority — never delegated to us

You keep

The relationship, and the direction

The client relationship and the reporting line
The acceptance criteria the work is held to
The recommendation — including “do less”

InfraEdge takes

One defined workstream

Scoped in writing before anything starts
Delivered as pull requests through their process
Handed over to whoever stays — usually you

If the client asks us about work that is plainly yours, we say so. There is no referral agreement to protect and no incentive to widen the account.

Before you introduce us

The questions you would be mad not to ask.

Answered here rather than on a call, because the reason to answer them is that you are putting your own client relationship at risk.

How we access a client estate

Team meeting in a bright office around a conference table, representing the start of a joint engagement.

Will you go around us?

No — and that is structural, not a promise. The scope is agreed in writing with you before anything starts and says what is ours. If your client asks us about work that is clearly yours, we send them to you. We have no referral agreement to protect and no incentive to widen the account.

Whose name is on the work?

Whichever you need. We are content to be named as the engineering partner, and equally content to be invisible and deliver through your process under your client relationship. What we will not do is let a client believe your team built something we built, if they ask us directly.

Who carries the client relationship?

You do, unless you ask otherwise. We would rather talk to one named technical owner on your side than to your client in parallel, because two reporting lines into one engagement is how scope drifts.

What happens at the end?

The same handover anyone else gets: code in the client’s repository, tests, runbooks written for whoever holds the pager, and a decision record of what we did not do. If you are staying on after we leave, the handover is to you.

Can you white-label, or do you have a partner programme?

There is no partner programme, no tier, no referral fee and no exclusivity, and we are not going to invent one to answer this question. What exists is a written scope per engagement. On naming: we will work under your brand, but we will not tell a client something untrue about who did the work.

How quickly can you start?

It depends on what is already committed, and the honest answer is sometimes a date several weeks out. Capacity is the constraint rather than appetite, and we would rather give you a date you can plan around than one that slips after you have told your client.

Discuss an engagement

Twenty minutes, no charge. Tell us what your client needs and where the boundary sits, and we will tell you whether it is work we can take and roughly when. Nothing is priced on the call; if there is work worth doing, a written scope reaches you within 24 hours.

Request a 20-minute triage call How an engagement runs