Your domain, your logo, your Stripe. Run buyer and partner portals on a custom domain under your brand, take payment through your own Stripe Connect account, and keep every tenant isolated at the row level across sixty-four separate tables.
Per tenant
Custom domains
Your brand
Logo
Your Stripe
Payments
64
Isolated tables
The Basics
White-label means your buyers and partners see your domain, your logo, and your company on the invoice.
When you run a lead operation, the buyers and partners you work with should be dealing with your business, not a platform vendor sitting between you. White-label puts your domain and logo on the portals they log into and processes their payments through your own Stripe account, so the relationship stays yours.
Underneath, the routing engine, contracts, caps, reporting, and every other module run exactly the same. White-label is about who the customer sees and who gets paid, layered on top of a platform that keeps every tenant’s data walled off from every other tenant’s.
Your Domain, Your Logo, Your Stripe
The parts a buyer or partner actually notices are the parts you control.
Point a custom domain at your tenant and your buyers and partners reach the portals at your address. They log in, submit, and check their numbers on your domain, not a shared platform URL.
Upload your logo and it carries through the portals your buyers and partners use. The people you work with see your brand where they spend their time, not a generic platform shell.
Buyer checkout pages are scoped to your tenant and branded to you, and payment is processed by your company through your own Stripe Connect account. The line item reads “Payment is processed by your company.”
Built Different
Running more than one brand only works if the tenants behind them cannot see each other's data.
Every per-tenant table (sixty-four of them) carries a tenant identifier, and queries are scoped so one tenant’s rows never surface in another tenant’s view. Multiple brands run on the same platform without leaking into one another.
Admin, buyer, and partner portals all run under your brand. The people on each side of your business log into your domain and see your logo, whichever role they hold.
Checkout pages are scoped to the tenant and branded to that tenant, and payment routes through that tenant’s own Stripe Connect account. Each brand collects on its own account, not a shared one.
Each tenant can turn features on or off independently, so brands can differ in what they offer without running separate installs. One platform, many configurations.
Who Runs It This Way
A few shapes of business where your brand in front matters as much as the engine behind.
Agencies running lead distribution for clients want each client to see the agency’s brand, not a third-party tool. Custom domains, your logo, and your Stripe keep the agency in the middle of the relationship instead of exposing the platform underneath.
Operators running more than one brand want each brand to look and bill like its own company. Row-level isolation across sixty-four tables plus per-tenant feature toggles let multiple brands share the same platform while staying fully separated in data and configuration.
In every case the same routing engine, contracts, caps, and reporting run underneath. White-label changes the domain your buyers reach, the logo they see, and the account that collects their payment, without changing how leads actually route.
Frequently Asked
What operators ask before putting their brand on the platform.
Your domain, your logo, and your Stripe. Buyers and partners reach the portals on a custom domain, see your uploaded logo, and pay through your own Stripe Connect account with checkout branded to your company. The routing engine and every other module run the same underneath.
Yes. You point a custom domain at your tenant and the buyer and partner portals are served at your address. The people you work with log in and operate on your domain rather than a shared platform URL.
Yours. Buyer checkout pages are scoped to your tenant and branded to you, and payment is processed by your company through your own Stripe Connect account. The checkout states that payment is processed by your company.
Through row-level tenant isolation across sixty-four per-tenant tables. Each tenant’s rows carry a tenant identifier and queries are scoped so one tenant never sees another’s data. Multiple brands run on the same platform without crossing over.
The admin, buyer, and partner portals all run under your brand on your domain with your logo. Whichever role someone holds, they are inside your branded environment.
Yes. Per-tenant feature toggles let each tenant enable or disable features independently, so brands can differ in what they offer while sharing one platform and one codebase.
Put Your Name On It
Run branded buyer and partner portals on a custom domain, collect through your own Stripe Connect account, and keep every tenant isolated at the row level. One platform, your brand in front.
Every module included at no extra license fee.