Partners

Bring the engineering organisation with you.

Agencies run Capybari for their clients. Tool builders connect it to the git host, the server and the alerting their users already have. Consultants and creators refer the teams they cannot take on. Three ways in, one form.

No fee, no minimum commitmentYou keep the client relationshipReviewed within five working days

Three kinds of partner

Find the one that describes you

You can be more than one. Plenty of agencies implement for some clients and refer the rest.

Implementation partners

You are an agency, studio or consultancy, and you run Capybari for your clients. You set up their projects, assemble the right specialist team per project, write the role contracts to match their conventions, connect their deployment targets, and stay on to operate it. You own the engagement and set your own rates. We give you per-client project isolation, per-client deployment targets and an audit trail you can show them.

Technology partners

You build something Capybari should meet in the middle — a git host, a hosting or infrastructure platform, a monitoring or alerting product, a chat tool where approvals should land. We work on branches in the customer's own repositories and deploy to SSH hosts they control, so the useful integrations are the ones already sitting either side of that. Bring the use case and we will bring an engineer.

Referral partners

You advise, teach or write for people who keep describing our exact problem — more roadmap than hours, no room to hire a reviewer, a security engineer and a DevOps engineer. You introduce them; we do the rest. Commission is paid on what they actually spend, and the terms are published in full on the affiliate page rather than negotiated in private.

Getting started

Four steps, no procurement theatre

Most partners are running their first client project inside a fortnight.

Apply

Fill in the form below. Tell us who you work with and what you would build. Two paragraphs is plenty.

Talk it through

A 30-minute call about the work in front of you, not a qualification script. We say no clearly when it is not a fit.

Run a real project

Bring one live piece of client work. We help you set up the project, the team and the first deployment target, and we watch the first deploy with you.

Go on the record

Signed agreement, partner listing, referral tracking if you want it, and a named contact who answers you directly.

What partners get

The practical list

Proposed terms, marked PLACEHOLDER until the partner agreement is signed off.

  • A named contact who knows your accounts, rather than a shared inbox
  • Onboarding for your team — a working session on projects, role contracts, autonomy levels and deployment targets
  • Per-client project isolation and per-client deployment targets on the Business plan
  • An audit trail you can hand to a client — every plan, diff, deploy log and investigation, exportable
  • Referral commission on the accounts you introduce, on the published terms
  • A listing in the partner directory with your specialisms and the industries you serve
  • Early access to features on the roadmap, and a route to say they are wrong before they ship
  • Co-marketing when there is something true to say — a case study your client has approved, not a logo swap
  • Sandbox projects for demonstrations, so you are never showing a client your other client's board
  • Direct escalation into engineering for anything blocking a client deploy

Apply

Tell us what you would build

One form for all three partner types. A person reads it, and we aim to reply within five working days.

Please tell us who you are.

Please use an address we can reply to.

Please give us a company name.

Please include a link we can look at.

Pick the closest fit. We will work the rest out on the call.

Please choose one.

Specifics beat enthusiasm. One real project is worth three paragraphs of strategy.

Please tell us a little about the work.

We use what you send here to answer you and nothing else. See the privacy notice.

Before you write

Applications that get a fast yes tend to have these things in them.

  • A live project you could start with, not a hypothetical one
  • The stack and git host your clients actually use
  • Whether your clients deploy to their own servers today
  • How many projects you would expect to run in parallel
  • Anything you think we are missing — we would rather hear it now

Partnerships
partners@capybari.com
PLACEHOLDER — confirm before launch

Everything else
Contact us
General enquiries, support and sales

Questions

What partners ask first

Does becoming a partner cost anything?

No. There is no application fee, no annual partner fee and no minimum commitment. You will need a Capybari account to run projects — whichever plan suits the work, and the Business plan is the one built for multi-client use.

Who owns the client relationship?

You do. Implementation partners contract with their own clients, set their own rates and keep their own commercial terms. We do not approach your clients directly without asking you first, and we do not take over an account you introduced.

Can I be more than one type of partner?

Yes, and most agencies are. You implement for the clients who want it run for them, and you refer the ones who would rather run it themselves. Tick More than one of these on the form and we will set both up.

What does an implementation partner actually do?

Set up the client's project and connect their repositories. Assemble the specialist team the work needs. Edit the role contracts so the agents follow that codebase's conventions. Configure the deployment target — deploy command, health check, rollback command. Then operate it: approve plans, hold the review gates, and raise the autonomy level as the client's confidence grows.

What integrations are you actually looking for?

Anything sitting immediately either side of the pipeline. Git hosts, because we work on branches in the customer's own repositories. Hosting and infrastructure, because deployment targets are SSH hosts the customer controls. Monitoring and alerting, because that is what tells you a health check should have failed. Chat tools, because approvals and mid-run questions want somewhere to land. See the integrations page for what exists today and the roadmap for what is queued.

Can I white-label Capybari?

Not today. You can run it for a client under your own service brand and hand them the audit trail, but the product itself is not re-brandable and we are not going to pretend otherwise. If that is a blocker, say so on the form — it is useful evidence.

How do referral commissions work?

They are published in full, including the rate, the cookie window, the payout schedule and the minimum, on the affiliate page. Referral partners are paid on the same terms as everyone else. There is no private rate card.

My clients will not let an agent near production. Now what?

Then do not point it at production. Start at Manual autonomy, where nothing runs until someone presses the button, and connect no deployment target at all. Plenty of teams run Capybari for planning, building and review only. Deployment is a thing you switch on later, if ever.

Something not covered? Ask partnerships directly.

Run one client project through it

The fastest way to know whether this is worth a partnership is to put one real piece of client work through the board and watch what the plan looks like.

No fee · No minimum commitment · Reviewed within five working days