Managed service providers spend years earning trust with a client base and then hand the software revenue to someone else. The partner program lets you deploy on your own hardware, resell the platform under your own commercial terms, and keep earning on the builders you introduce for as long as they stay with you.
The MSP business has a ceiling built into it: you sell hours and hardware, and the recurring software revenue in your clients' stack flows past you to vendors your client has never met. Meanwhile you are the one who gets called when it breaks.
You become the route to market. Builders come onto the platform through you, and attribution follows them for as long as they remain under your account. Where a client requires the runtime to sit on hardware they or you control, that is a supported deployment rather than an exception.
A supported path for clients whose requirements do not allow a shared hosted runtime.
You continue to earn on a builder for as long as they remain under your account, rather than on a first-year bounty.
Appliance updates are signed and pulled, with health-gated swaps, so a fleet stays current without anyone hand-patching machines.
Managed connectivity across deployed appliances, so operating many client sites does not mean operating many bespoke networks.
Your clients already trust you with their infrastructure. This adds the application layer to what you can offer.
The platform is the product. Your contribution is the relationship, the deployment, and the support you already provide.
You set terms with your clients. The platform's cut is defined and predictable.
Deployment, update mechanics, and the program's commercial structure are all published rather than negotiated blind.
That is what the partner appliance program is for. Deployment and update mechanics are documented.
A builder you bring across remains attributed to you for as long as they stay under your account.
The division is defined in the partner program documentation, which is public and readable before you commit.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docs