Run your entire partner network in one place
PartnerOS is the operating system for any partner network — resellers, franchises, campuses, brokers, agencies. Recruit, onboard, automate, pay, and grow every partner. One configurable core. API-first. Multi-tenant by construction.
SaaS · Franchise · Education · Agencies · Financial · Distribution
Replaces the patchwork most programs run on
Built for every kind of partner network
A partner is any external org you manage — a reseller, a franchisee, a campus, a broker. The core is configurable, so PartnerOS fits how your network actually runs.
SaaS & tech resellers
ISVs, MSPs, and channel resellers moving software and cloud.
A VAR registers a deal, then earns recurring MRR share.
Franchise & multi-location
Franchisors and multi-unit brands running royalties and rollouts.
A coffee franchise pays 6% royalty per café, every month.
Education & campuses
Institutions with branches, plus tutoring and admissions networks.
A university credits a campus $150 per enrollment.
Agencies & consultancies
Referral and delivery partners working shared pipelines.
An agency registers a lead and splits the delivery fee.
Financial & insurance
Brokers, IBs, and introducers with tiered commission books.
A broker earns an override on a sub-broker's policy.
Distribution & wholesale
Distributors and sub-dealers with multi-tier margin.
A distributor passes cost-plus pricing down to sub-dealers.
One core, any vocabulary
PartnerOS ships a small set of generic objects. Rename them, restage them, and map them to how your industry actually talks — no forked codebase, no bespoke build.
Everything a partner program needs, in one system
Ten modules on one event bus and one API — from the first application a partner submits to the payout that lands in their account.
Recruitment & onboarding
Application intake, approval, and a portal provisioned the moment a partner is approved.
Learn moreDeal registration & PRM
Register deals, protect them, and move them across configurable pipelines on a shared board.
Learn morePlaybooks automation
An event-driven, node-graph engine that turns any signal into the right action, automatically.
Learn moreCommissions & payouts
Rules-based commissions, an auditable ledger, and managed payouts partners can withdraw.
Learn moreContent & legal OS
Foldered material libraries plus document templates, e-signature, and renewal automation.
Learn morePartner & customer CX
A service desk with SLA escalation, CSAT/NPS surveys, and automatic health scoring.
Learn moreCustom metrics & dashboards
Ingest any event, define your own metrics, and build a dashboard for every partner level.
Learn moreWhite-label portals
Give every partner a branded portal on your domain — or on their own verified domain.
Learn moreAPI & integrations
A generated OpenAPI, scoped machine keys, signed webhooks, and an event-ingest rail.
Learn moreSecurity & multi-tenancy
Role-based access, strict tenant isolation, and encrypted BYO credentials — by construction.
Learn moreSee all features
Deep-dive every module, how it works, and how it connects.
BrowseFrom application to payout, on autopilot
Recruit & approve
Application intake, a review queue, and a portal provisioned the moment a partner is approved.
Register & sell
Partners register deals into your pipelines; your team runs them on a shared board.
Automate & enable
Playbooks react to every event — send docs, assign tasks, accrue commissions, notify.
Pay & grow
Commissions accrue to an audit ledger, payouts execute, and CX + dashboards retain.
Turn every signal into the right action
PartnerOS runs on an event bus, and Playbooks is how you program it. Trigger on any event, branch on conditions, wait on timers, and fan out to actions — no code.
- ✓Event-driven, node-graph workflows
- ✓Email, tasks, docs, commissions, webhooks
- ✓Actions emit events, so journeys compose
Pay partners accurately, on time
Define commission rules, accrue to an append-only ledger the instant a deal closes, run recurring schedules, and execute managed payouts through a provider — every cent traceable.
- ✓Immutable, auditable commission ledger
- ✓Recurring schedules + withdrawal approvals
- ✓Managed provider payouts with retries
One pipeline for every partner deal
Partners register deals from their portal; your team runs them on a shared, configurable board. A partner only ever sees their own deals — enforced in the data layer, not the UI.
- ✓Configurable pipelines and stages
- ✓Kanban board with won/lost semantics
- ✓Strict per-partner deal isolation
A dashboard for every partner level
Connect a partner's systems and turn the event stream into insight. Define custom metrics — count, sum, unique — and compose dashboards rendered at whatever partner level you choose.
- ✓Operator-defined metrics over any event
- ✓Metric, time-series and event-list widgets
- ✓Rendered per partner, with a hard leak guard
Catch churn before a partner leaves
A full service desk with SLA escalation, plus CSAT and NPS surveys and health scoring that rolls status, open tickets, and last CSAT into a tier you can act on.
- ✓Tickets, threads, assignment, SLA sweeps
- ✓CSAT / NPS with a public respond flow
- ✓Health tiers that feed retention playbooks
API-first — and the docs can't drift
Every endpoint is generated from its runtime schema, so the OpenAPI spec always matches the server. Mint scoped machine keys, push events over the ingest rail, and receive signed webhooks.
- ✓Generated OpenAPI + interactive docs
- ✓Scoped machine keys and event ingest
- ✓HMAC-signed outbound webhooks
curl -X POST https://api.partneros.com/api/events/ingest \
-H "authorization: Bearer pos_live_…" \
-H "content-type: application/json" \
-d '{
"customerEmail": "buyer@acme.example",
"type": "feature_used",
"payload": { "feature": "export" }
}'
# → 200 event recorded → metrics + dashboards updateGive every partner their own branded home
Each partner org carries its own theme, logo, and custom domain — resolved only for verified hosts, so branding never widens access. Same platform, their front door.
White-label portalsMulti-tenant by construction
Isolation isn't a setting you remember to switch on — it's the architecture. The safe path is the only path.
Security & RBACServer-side scoping
Every partner query is scoped to the caller's org in the data layer — never trusted from the client.
Role-based access
Each route is guarded by a permission; the UI gates nav and actions on the same set.
Encrypted BYO credentials
Partner secrets are AES-256-GCM encrypted at rest, masked on return, and never logged.
Verified-domain isolation
Custom domains and CORS both require a verified host, so branding never widens access.
“A partner program is a system. It deserves an operating system — not ten disconnected tools and a spreadsheet.”
Why we built PartnerOS
Frequently asked questions
What exactly is PartnerOS?+
An all-in-one platform for running a partner program end to end: recruitment and onboarding, deal registration and pipelines (PRM), an event-driven automation engine, commissions and managed payouts, a content and legal OS, a partner CX suite, custom metrics and dashboards, white-label portals, and a full API — all on one multi-tenant system.
How is a partner kept from seeing another partner's data?+
Isolation is enforced in the data layer, not the UI. Every partner-scoped query runs through a shared scoping helper tied to the caller's organization, and cross-tenant access throws by construction. Operators get explicit, audited cross-partner visibility; partners are pinned to their own slice.
Can partners get their own branded portal?+
Yes. Each partner org carries its own theme, logo, and favicon, and a portal can live on a custom domain resolved by verified host. Only verified domains resolve, and CORS grants match the same host, so branding never widens access.
How do integrations and the API work?+
PartnerOS is API-first and the API documents itself — every endpoint is generated from its runtime schema, so the OpenAPI spec can't drift. Mint scoped machine keys, push customer events over the ingest rail, and subscribe to HMAC-signed outbound webhooks. You can even point an AI agent at the spec and have it call endpoints directly.
What happens automatically when a deal is won?+
Winning a deal emits an event. From there the automation engine takes over: the commission rule accrues a ledger entry, a welcome or fulfillment playbook can start, dashboards update, and any subscribed webhook fires — with no manual step.
How are commissions and payouts handled?+
Commissions accrue to an append-only ledger (all money in integer minor units), recurring schedules advance on a background worker, partners request withdrawals, operators approve, and a payout worker executes the provider transfer with backoff. Every movement is auditable, and money values never appear in legal documents.
Ready to run your partner program in one place?
Book a walkthrough and see recruitment, PRM, automation, payouts, CX, and dashboards working together — on one platform.