White-label
Sell hosting as your own product. Your brand carries across the panel, the emails and the invoices your clients receive; your clients sit in their own isolated tenants underneath you; and you set the prices. Underneath it is the same control plane, driver fleet and infrastructure that runs our own network of 100,000+ PBN sites.
Most platforms treat white-labelling as a stylesheet bolted onto a customer panel. Here it is a property of the tenant itself: every organisation carries a brand reference alongside its type, its parent organisation and its default currency. The brand travels with the account, so anything rendered for that account — or for any account beneath it — is rendered in your identity rather than ours.
That works because the whole product is built on the Zinn Design System with semantic design tokens rather than hardcoded colours. The same token layer that gives every surface a light and a dark theme is the layer a brand overrides. There is no separate white-label build to fall behind the main product: your clients get the current panel, in your colours, on the day we ship it.
And because product line is a first-class dimension on plans, blueprints and sites, white-label works across every line on the engine — footprint-free, mainstream managed WordPress, WooCommerce and multisite — from one account rather than four integrations.
Organisations are hierarchical from row one: your reseller org sits above client orgs, which sit above their sites. That tree is not an org chart — it is the boundary the database enforces.
Each client is its own organisation with its own users, sites, billing and data. Postgres row-level security enforces the boundary at the database, not in application code, so a cross-tenant query is not something a bug can produce.
Access is a membership: a user, an organisation and a role. Client sub-accounts and your own internal team seats use exactly the same mechanism, so there is no second, weaker access model to reason about.
Owner, billing, developer and read-only. Roles resolve to granular module-and-action permissions, so what each person can reach is explicit rather than inherited from whoever invited them.
Sites run isolated from one another, so a compromise on one client's site is contained rather than free to reach a neighbour's.
Actor, action, target, metadata, IP and timestamp on every privileged action, scoped to the organisation it happened in. When a client asks who changed what, there is an answer.
Per-organisation API keys and OAuth clients with granular scopes tied to the same permission catalogue. The public API, CLI, Terraform provider and MCP server all authenticate the same way.
Reseller billing is hierarchical in the same shape as the tenancy tree: we invoice you, and you invoice your clients — in your own currency, at your own markup. You set your own plan prices; commissions and margins are tracked for you rather than reconciled by hand in a spreadsheet.
Two details matter more than they sound. First, price is captured at purchase: a subscription pins the exact plan version and records the amount and currency the customer actually paid — which may reflect FX, a discount or your markup — so a later catalogue edit or currency movement never rewrites what a live subscriber was sold. Second, on domains the reseller overlay is explicit: cart pricing composes platform sell price, then your markup, then any promotion, and the difference between wholesale cost, sell price and your cut is written to a margin ledger row per order line.
Invoicing follows the tree too. You see your invoices from us; your clients see invoices from you. Recurring charges are driven by our engine rather than by a payment gateway's subscription object, which is what keeps hierarchical reseller billing and multi-currency capture possible in the first place — there is no gateway construct that models a reseller.
A white-label panel is worth little if the confirmation email arrives from somebody else. The brand carries through the whole customer-facing chain.
Every user-facing string, notification and email is localizable into 58 languages, and content is auto-translated as part of the content lifecycle rather than as a manual afterthought. Right-to-left languages including Arabic are handled properly — the interface uses logical CSS properties throughout, so a mirrored layout is the same layout, not a separate stylesheet that drifts.
Pricing is multi-currency on the same terms. USD is the base; other currencies are derived through an FX adapter, charm-rounded and stored, and the panel renders the stored price rather than converting on every request. A subscription locks its currency and price at signup. Money is never a float anywhere in the system: it is integer minor units plus an ISO currency code, end to end.
The practical consequence for a white-label partner is that selling into a second country is a pricing decision, not an engineering project.
There is no separate reseller stack. White-label runs on the control plane that owns customers, billing, provisioning, tickets and events, and drives the same pluggable drivers for CDN, DNS, registrar, payments, mail and everything else. Whatever ships to the platform ships to your clients.
Every external dependency sits behind an adapter interface with more than one implementation, so no payment gateway, registrar, DNS provider or CDN is welded into the business logic. That rule protects us, and by extension it protects the book of recurring revenue you build on top of us: a gateway can be swapped, or a second added per region, without migrating your customers.
Migrations onto the platform are free and run as a durable, resumable workflow rather than a manual copy — so moving an existing client base is a scheduled operation, not a weekend.
White-label sits on our reseller and agency lines, which are new — tiers are not published yet. If you are already running client sites at scale and want early pricing, [talk to us](/contact) and we will scope it with you, including migrating your existing sites across at no cost.
In the meantime you can start free with a card-free 7-day trial on our footprint-free line (up to 5 sites, no card details) and see the panel, tenancy and billing model for yourself.
The brand is a property of the organisation, so it carries across the client-facing panel, the transactional email templates, marketing and lifecycle campaigns, and the invoices your clients receive. White-label partners can also send from their own verified domains rather than ours. Because the design system uses semantic tokens rather than hardcoded styling, branded surfaces stay on the same release train as the standard product.
Each client is a distinct organisation in a hierarchical reseller-to-client-to-site tree, and Postgres row-level security enforces that boundary at the database rather than in application code. On top of that, sites run with per-site compute isolation, so a compromise on one site is contained rather than able to reach a neighbour.
Yes. Billing is hierarchical: we bill you, you bill your clients, in your own currency and at your own markup. Price is captured at the moment of purchase against a pinned plan version, so later catalogue or FX changes never rewrite what a live subscriber was sold. On domain orders the platform sell price, your markup and any promotion compose in that order, and your cut is recorded on a margin ledger row per order line.
White-label works across every line on the engine — footprint-free hosting, mainstream managed WordPress, WooCommerce and multisite — because product line is a first-class dimension on plans, blueprints and sites rather than two separate applications.
They do not, mechanically. Both are memberships — a user, an organisation and a role — so client sub-accounts and your own internal seats use the same access model. The customer roles are owner, billing, developer and read-only, and each resolves to a granular set of module-and-action permissions.
Yes. The interface, notifications and content are localizable into 58 languages with proper right-to-left support, and pricing is multi-currency: USD is the base, other currencies are derived, charm-rounded and stored, and a subscription locks its currency and price at signup.
Every external service — payments, registrar, DNS, CDN, mail — sits behind an adapter interface with more than one implementation, and recurring billing is driven by our engine rather than by a gateway's own subscription objects. That is what makes a recurring book portable. Migrations onto the platform are free and run as a durable workflow.
Reseller and agency are new product lines and their tiers are not published yet. Contact us for early pricing. You can evaluate the platform now on a card-free 7-day trial on the footprint-free line, which covers up to 5 sites and needs no card details.
Isolated client tenants, your own pricing and margins, and your identity on every surface a client sees. Start free with a card-free 7-day trial, or talk to us about early white-label pricing and moving your existing clients across at no cost.
Start free