For consultancies, software factories and independent professionals
Your client stays yours. We provide the cloud and DevOps capacity you need.
If you have projects and need capacity or a specialism in cloud and DevOps, we provide it. Your client stays yours.
01 / Models
Three ways to work together
01
Subcontracted project
You keep the contract and the client relationship. We deliver a scope and price agreed before work starts.
Who it is for
When you have a defined project and need technical delivery capacity.
02
Specialist reinforcement
A named senior engineer, subject to availability, joins your project for an agreed period to cover a specific area: Kubernetes, observability, FinOps or automation. Scope, hours and schedule are agreed in writing before we start; no on-call outside agreed hours.
Who it is for
When the project is yours and you need a specialism your team lacks.
03
Referral under agreed terms
You introduce the opportunity. Before we start we agree in writing how the client relationship is handled and on what terms we take on delivery.
Who it is for
When the request does not fit your focus but you want your client to remain well served.
SpecialismsDevOps and support in agreed hoursObservability and alertsCloud reviewCloud and Kubernetes migration
02 / Process
How we get started
You share the context
You present the project, the client (under NDA where relevant) and your needs.
We assess fit, availability and scope
We assess whether we can help, when, and with what scope.
Proposal
You receive a written proposal with scope, collaboration model and terms.
Coordinated delivery
We work in the agreed repositories and infrastructure, with agreed updates and clear communication.
Documentation and handover
We document everything and hand over the knowledge so your team can carry on.
03 / Questions
Common questions from consultancies
Confidentiality
We sign an NDA before you share sensitive project details.
End client
We agree with you how and when we communicate with your client.
Repositories and infrastructure
We work only in the agreed repositories, accounts and environments, with individual identities and minimum permissions you can revoke at any time.
Transparency
We keep you informed of scope and work status through agreed updates.
Scope
What the work includes and what stays out is defined in the proposal before we start.
Autonomy
We work with technical autonomy within the agreed scope, without needing task-by-task direction.
Handover
We leave documentation and step-by-step guides for what we do, so your team can carry on.
- The specifics are agreed in writing for each collaboration.
04 · Let’s talk
Let’s explore a partnership
Tell us about your consultancy, the technical opportunity you are considering or the kind of collaboration you are looking for. We read your message and reply.