What does white labeling cover in BYOB? #
White labeling in BYOB means clients see your brand instead of ours. The badge goes and your domain serves the site. On Enterprise the embedded experience and login can wear your identity too. Two tiers carry this: paid plans for surface branding and Enterprise for deep branding. The table below keeps budgets honest.
How do the tiers compare? #
Paid plans remove the BYOB badge and unlock custom domains, which covers freelancers and studios shipping client sites under their own addresses. SSL stays automatic and deploys stay one click, so branded delivery adds no ops burden.
Enterprise adds the deep layer. White label embed puts building inside your product or portal. Custom branding carries your logo and palette across the experience. Private cloud, SSO with SAML, audit logs, unlimited seats, and 99.9 percent SLA cover the controls buyers and legal teams ask about. A success manager stays on after launch.
| Capability | Pay as you go | Paid plans | Enterprise |
|---|---|---|---|
| Visible branding | BYOB badge shown | Badge removed | Custom branding across embed and surfaces |
| Domains | Free byob.page subdomain | Custom domains with auto SSL | Custom domains with your domain strategy |
| Hosting and cloud | Shared Cloudflare deploys | Shared Cloudflare deploys | Private cloud options |
| Identity | Built in auth per project | Built in auth per project | SSO with SAML and central lifecycle |
| Governance | Deploy snapshots with rollback | Deploy snapshots with rollback | Audit logs with defined ownership |
| Seats and sharing | Solo plus preview URLs | Collaborators on Pro and Max | Unlimited seats |
| Support | Self serve resources | Plan support | Success manager with 99.9 percent SLA |
Try it: Domain Name Ideas
Who does each tier fit? #
Three buyer types return most.
Agencies reselling client builds #
A studio shipping client sites under its own brand bills the work as its own product. Paid plans cover domain plus badge removal per site, while Enterprise embed lets clients edit inside the studio portal. Start paid and move when clients ask to click around themselves.
SaaS products embedding generation #
A software product adds site generation inside its dashboard so customers never leave. Enterprise embed plus custom branding keeps trust in one place, while SSO connects customer logins. Start with a pilot on one customer segment.
Internal platforms with strict controls #
A company gives teams a compliant way to publish pages under brand rules. Private cloud plus residency choices satisfy legal, while audit logs record who shipped what. Start with one team pilot, then expand by unit.
How do you start? #
For paid tier branding, the path is short. Subscribe, remove the badge, connect the domain, and ship.
Enterprise follows a longer path with your team in the room.
- Discovery call on requirements and constraints.
- Architecture blueprint with integration and security model.
- Platform build with demos you can observe.
- Pilot with one team on real work.
- Launch covers deploy and monitoring with docs handoff, then a success manager stays on.
What are the honest limits? #
Enterprise is a custom engagement, so expect a scoping conversation before numbers. Timelines stretch with integration count, and compliance reviews add weeks that no vendor controls. Under the hood the core stays BYOB powered even when your brand covers the surface, which matters for security reviews. Name identity policy and audit ownership before rollout, since retrofits cost more later.
What are the trade-offs? #
Two depths: paid plans for badge removal plus custom domains, Enterprise for embed, custom branding, SSO, and audit.
| Where the paid tier wins | Where it loses |
|---|---|
| Client sites under your domain with one click deploys and auto SSL | Embedded building inside your portal needs Enterprise scoping |
| No ops burden for surface branding | Timelines stretch with integration count and compliance review weeks |
| Bills as your product from day one | Core stays BYOB powered under your brand, which matters to some buyers |
Pick Enterprise when clients edit inside your product or auditors ask for identity plus logs. Pick paid plans when badge free domains solve this month.
What we learned building this? #
White labeling in BYOB has two layers: paid plans hide the badge and add custom domains, while Enterprise adds embeds, custom branding, private cloud, single sign-on, and audit logs. The path from discovery to pilot reflects that embeds plus identity need a scoped engagement, since each brand surface and login flow gets reviewed before launch.
Who this is for (and who should skip it)? #
This fits freelancers and small studios shipping client sites under their own domain and badge free look. Paid plans cover that surface branding without extra ops and keep deploys one click.
Skip it for deep embed or strict enterprise controls unless you plan an Enterprise engagement. If you need white label embed SSO with SAML audit logs and private cloud you need the custom path not a quick toggle.
One limit to know. Standard white label covers logos and domains, not SSO or audit logs. A common mistake is promising clients deeper access controls before confirming they need an Enterprise setup.
- Best for freelancers shipping badge free client sites under their own domain.
- Best for agencies reselling builds with steady one click deploys.
- Best for enterprises planning embeds with SSO and private cloud needs.
What should you do next? #
If badge free client domains solve this month, take a paid plan and connect the first domain today. If embedded building under your brand is the goal, contact the Enterprise team with your identity setup and rollout scope ready. Either way, pilot with one team before you promise the company.