Cash for you. Credits for your customer.
Cloud providers fund partner-delivered work through structured pathways. Those pathways are closed to individuals and open to partners. As a network subcontractor you deliver under our status and share in what that unlocks.
- Paid to you
- Cash, against milestones in the purchase order
- Paid to your customer
- Cloud credits in their account
- Cost to you
- None
- Commission on your own fee
- None
- Who submits
- CloudOps Network, as the named applicant
- Who handles reporting
- CloudOps Network
- Programme detail
- Shared with members during intake
On qualifying projects, CloudOps Network engineers receive a cash benefit paid against milestones defined in a purchase order, and their customer receives cloud credits applied to their provider account. CloudOps Network submits and reports as the named applicant. Engineers pay nothing to join or to participate, and no commission is taken from their own client fee.
What the benefit actually changes
You earn more on the same project
The benefit is in addition to what you charge, not carved out of it. For most engineers this is the reason to join.
Your proposal gets cheaper for the client
Credits reduce their cloud spend. That changes the shape of a deal you might otherwise lose on price.
You close work you would have lost
Projects stuck on budget approval move when part of the cost is offset. This is the effect engineers report most often.
You stop doing the paperwork
Registration, submission, evidence, reporting and provider communication sit with us. That is the part that makes this impractical alone.
You keep the relationship
The client stays yours. Nothing in the structure inserts us between you and your customer commercially.
You get a defensible answer for the client
A disclosure script that explains the arrangement plainly, because the worst version of this is a customer finding out later.
The honest constraints
We would rather set expectations correctly than have you find these out in month three.
Not every project qualifies. Timing is tied to provider cycles rather than to our preferences. And accuracy is absolute, because the whole structure depends on it.
Not every project qualifies
Eligibility turns on workload type, scale, region and timing. A fast no is more useful than a slow maybe.
Timing follows provider cycles
Approval and payment timing are not entirely ours to set. We tell you the expected timeline at intake and update you if it moves.
Work cannot start early
Anything delivered before a purchase order is issued cannot be covered. There is no exception and no backdating.
Claims must be accurate
Overstated scope, inflated figures or misrepresented customer situations end network membership. One inaccurate submission puts everybody's access at risk.
Benefit questions
How much is the benefit worth?
It varies by pathway, project scale and region, which is why we confirm the figure per opportunity rather than advertising a number. You are told what your share is and what your customer's credits are before you commit to anything.
Is this a referral fee?
No. It is payment for delivery work performed under a subcontract, tied to milestones. You are doing the engineering.
Do I get paid even if I am also charging the client?
Yes, where the pathway allows it. The two are separate commercial relationships, and the intake makes clear which applies to a given opportunity.
What are the credits my customer receives?
Cloud credits applied to their account with the provider, usable against their consumption. They come from the provider, not from your fee.
Which cloud providers are covered?
Coverage is deepest on AWS. Other providers are supported where a pathway exists for the work in question, confirmed during intake.
Can I see the exact programme names?
Not publicly. Once you are in the network and an opportunity is in intake, you are told exactly which pathway applies, what it requires and what it pays.
What members say
Engineers on why they stay, in their own words.
The vetting was real, and so was the first match. Three weeks after my invite I was on a migration that fit my exact stack, at my rate, with a purchase order before I wrote a line.
I brought my own customer through intake mostly to test the claim. The credits landed in their account, the cash benefit paid against milestones, and the client relationship stayed mine.
No platform fee and no commission sounded too good until I saw where the economics come from. The compliance bar is strict, and honestly that is why the benefits keep working.
Request an invite
Tell us what you build, where you work and what you are certified in. If there is a fit you will hear from a person, not an autoresponder.
Joining is free. It always will be. Engineers are never charged to be matched or to receive benefits.