White-label to the core, not just a logo swap
Give every partner, branch, or franchise its own branded home — theme, custom domain, emails, and documents — on one multi-tenant platform where branding never widens access.
Theme · Custom domains · Email · Documents · Embed · API
One platform behind the scenes, their front door out front
White-label isn't a SaaS-only feature. A software reseller, a coffee-shop franchisee, a university campus, or an insurance broker each gets a home that looks like theirs — while you run one multi-tenant system underneath.
Their brand, applied everywhere — no code
Set a partner or branch's palette, logo, favicon, and typeface once. Every surface they touch re-skins instantly — configured from settings, versioned, and previewed live before it ships.
- ✓Per-tenant colors, logo, favicon, typography
- ✓Configured in settings — no builds, no forks
- ✓Live preview before you publish the theme
Every partner on their own domain
Point a partner's own subdomain at PartnerOS. The host is verified before it resolves, TLS is issued and auto-renewed, and CORS grants match the same verified host — so a custom domain is a front door, never a back door.
- ✓Bring-your-own domain, verified before it resolves
- ✓Automatic TLS with auto-renew
- ✓CORS scoped to the verified host — isolation holds
Branded on every surface, not just the login
The brand follows the partner through every touchpoint — the portal, the emails, the documents, and the domain those all live on.
Partner portal
The whole portal UI carries the partner's colors, logo, and typeface — web and mobile.
Transactional email
Invites, notifications, and payout receipts send from the partner's look and, optionally, their domain.
Documents & agreements
Generated agreements and materials render under the partner's brand and letterhead.
Login & favicon
Sign-in screens, favicons, and browser tab titles are branded — no PartnerOS chrome leaks through.
Sender domain (DKIM)
Bring your own SMTP and DKIM keys — encrypted at rest — so email authenticates as the partner.
Embedded widgets
Drop deal registration or the payout ledger straight into the partner's own product.
Every location gets its own space, isolated from the rest
Franchisees, campuses, and sub-partners each run on their own branded domain, sealed off from siblings. Roll-up reporting stays with the operator at the top.
Coffee franchise
acme.coffee partners.acme.coffee
Every franchisee gets their own branded hub for orders, royalties, and playbooks — isolated from sibling units, rolled up to the brand.
University with campuses
university.edu campus.university.edu
Each campus runs enrollments and referral partners on its own branded space; the system office sees the whole network.
Agency network
agency.com portal.agency.com
Delivery and referral partners log into an agency-branded portal — the end client never sees a third-party tool.
Or put PartnerOS inside their product
Some partners want the workflow, not another login. Embed deal registration, materials, or the payout ledger straight into their own app with a themed widget — or drive everything through scoped machine keys against the API.
Open the API docs<script src="https://cdn.partneros.com/embed.js" data-portal="acme-coffee" data-view="deal-registration" data-theme="tenant" ></script>
Branding that can't widen access
Every white-label surface is bound to a verified tenant. The safe path is the only path — you can't brand your way into someone else's data.
Security & RBACVerified-host resolution
A custom domain only resolves once its host is verified, and CORS grants match the same host — so branding can never widen access.
Encrypted BYO credentials
SMTP passwords and DKIM keys are AES-256-GCM encrypted at rest, masked on return, and never logged.
Isolated by construction
Each partner, branch, or franchise is a tenant; every query is scoped to its org in the data layer, not the UI.
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.