White-label is a word nearly every link shortener puts on a pricing page and almost none define. The promise is that you resell the product as yours: your domain on the links, your logo in the dashboard, your name on the invoice. The reality is usually that one or two of those are true.
This is the general guide. It defines the layers, shows how four competitors list the feature on their public pages, and says plainly what Elido covers and what it doesn't. If you're an agency with client workspaces, billing and reporting to sort out, read the agency guide to white-label URL shorteners after this one. I kept that material out of here on purpose.
The Four Axes of White-Label
Four surfaces matter, roughly in the order a customer notices them.
Domain. The short URL itself, such as go.your-agency.com/abc123 instead of bit.ly/abc123. Every customer asks about this first.
Dashboard and email. Does the interface the customer logs into carry your logo and colours, and does it live on your hostname? Do password resets and invites arrive with your name on them?
Billing and identity. Who does the customer pay, and whose login do they use? If they pay the vendor directly, you have a referral deal, not white-label.
API and integrations. Whether a developer reads your API docs or the vendor's, and whether webhooks and SDKs carry your name.
I've sat through a few procurement calls where "white-label" turned out to mean the first axis only. Treat the word as a question, not an answer.
Domain: The Easy Layer
Custom short domains are table stakes. The vendor publishes a CNAME target, you add it with a verification record, and the vendor issues a certificate and serves traffic under your hostname. The custom domains walkthrough covers the mechanism and the TLS post covers issuance.
The catches are operational:
- Apex domains. DNS forbids a CNAME at the zone apex, so
your-agency.comitself usually needs an ALIAS, ANAME or CNAME-flattening record. The vendor can't fix that for you. - Certificate transparency. Public logs list every certificate issued for your hostname. That's normal, but worth knowing if a customer is sensitive about it.
- Domain quotas. Plans cap how many domains you can attach. If each customer needs a subdomain, check the count before you sign.
On Elido you add a hostname, publish a _elido-verify TXT record with the token the dashboard shows, and point a CNAME at the edge. The domain API also accepts wildcard hostnames, which helps when every customer gets a subdomain. I found no plan check on wildcards in api-core, so confirm quota on pricing. The feature page is custom domains.
Dashboard and Email: Where Gaps Usually Live
Serving a dashboard under your hostname means the vendor routes your hostname to a tenant, issues a certificate, and themes the UI. Email is harder than it looks. Many vendors change the From display name and leave the sending domain as theirs, because SPF and DKIM for a customer's domain is real operational work.
Here's what Elido does, checked in code on 2026-10-24:
- A workspace on the Business plan can set
brand_name,logo_url,primary_color,email_from_nameandportal_hostnamethroughPUT /v1/workspaces/{id}/branding. Other plans get a 402. Reads still work after a downgrade, so the config survives. - A custom
portal_hostnameis resolved by the dashboard middleware to a workspace through/v1/portal/lookup. - Emails pick up the workspace's brand name, colour, logo and sender display name. The sending address stays Elido's. A per-workspace sending domain is not built.
The white-label guide walks through the fields, and the product overview is on the white-label feature page.
Billing and Identity
Three billing models exist across the market.
Direct billing. Your customer pays the vendor and you collect a commission. That's a partner program.
Reseller billing. You buy from the vendor, sell at your own price, and invoice the customer yourself. You reconcile usage by hand unless the vendor gives you an export.
Parent and sub-accounts. You hold a parent account, each customer is a child, and billing happens at the parent. This is what most agencies want, and plenty of vendors reserve it for enterprise contracts.
I'll be direct about Elido here. It has a reseller API that links client workspaces to a parent, but it doesn't issue consolidated invoices or per-client usage statements. Billing is per workspace. The agency guide covers what that means in practice.
For identity, Elido supports per-workspace SSO through WorkOS and has SCIM provisioning endpoints in api-core; see SCIM and SSO. The procurement angle is in the SCIM and SSO post.
API and Integration Branding
Developers ask different questions than marketers do. Does api.vendor.com appear in their code? Who signs webhooks? What's the SDK package called? On this axis white-label is partial almost everywhere. The SDK name is the vendor's, and webhook signatures use the vendor's keys. Elido doesn't offer a branded API hostname or per-tenant webhook signing keys. If your customers' developers will read docs, plan to write your own wrapper docs.
How Vendors List It
Pricing pages are the only comparable public source. Here's what each one says, read on 2026-10-24:
| Vendor | Custom domains | White-label named on pricing page | SSO or teams |
|---|---|---|---|
| Bitly | One complimentary domain from Growth ($29/month) | Not mentioned | SSO logins on Enterprise only |
| Rebrandly | 1 on Free, 2 Essentials, 3 Professional, 10 Growth | Not mentioned | Teammates from Professional |
| Short.io | 5 Free, 7 Hobby, 10 Pro, 50 Team, unlimited Enterprise | Not mentioned | User groups on Enterprise |
| Dub | 100 Business ($90/month), 250 Advanced, unlimited Enterprise | Advanced "suited to white-labeling needs", no feature name | SAML/SSO row on the comparison table |
| Elido | Any paid plan | Workspace branding on Business | SSO per workspace, SCIM endpoints |
Sources: Bitly, Rebrandly, Short.io and Dub, all accessed 2026-10-24. Short.io's page doesn't say whether its monthly prices assume annual billing, and Rebrandly's lists several prices per plan without labelling them, so I've left those out. "Not mentioned" means absent from the pricing page. It may exist in docs or in an enterprise contract, so ask. I haven't tested any competitor's white-label setup.
Operational Reality
If you resell someone else's infrastructure, a few costs follow regardless of vendor.
Your SLA can't beat theirs. Their incident is your incident, and their status page won't carry your name. When they ship or deprecate a feature, you track it as if it were your roadmap. Your customer's procurement team will want compliance evidence, so you need the vendor's documents in your sub-processor chain, as the SOC 2 and HIPAA post explains. And confirm how you get your data out if the relationship ends.
What to Ask Before Signing
These are the questions I ask, in order:
- Can I add a custom domain on the plan I'm quoting, and how many?
- Can the dashboard live on my hostname, and does the email sending domain, not just the From name, use mine?
- Is billing direct, reseller or parent and sub-account?
- Is SSO available on my plan, and SCIM?
- Can the API sit on my domain, and are webhook keys per tenant?
- What's the export format and the exit path?
- What's the SLA, the credit policy and the incident channel?
If the answers are partial, the plan is partial. That can be fine. Most resellers run on partial white-label. The marketing should just say so.
Related on the Blog
Frequently asked questions
What does white-label mean for a URL shortener?
It means the vendor's brand disappears from the surfaces your customers touch. That covers the short domain, the dashboard, the emails, the billing relationship and, at the deep end, the API. Few products cover all of them, so the useful question is which of those surfaces carry your brand and which still carry the vendor's.
Is a custom domain the same as white-label?
No. A custom short domain removes the vendor's name from the link, which is the smallest and most common piece. Dashboard branding, email sender, billing and API naming are separate layers. A plan that only offers a custom domain is a branded-link plan, and calling it white-label overstates what you get.
Which URL shorteners offer white-label plans?
On their public pricing pages (read 2026-10-24), Bitly, Rebrandly and Short.io don't name white-label as a feature. Dub describes its Advanced plan as suited to white-labeling needs without listing a feature by that name. Elido documents workspace branding on its Business plan. Enterprise deals can differ, so ask the vendor.
Can I send white-label emails from my own domain?
It depends on the vendor, so ask. On Elido, workspace branding changes the brand name, logo, colour and the sender display name in emails, but the sending address is still Elido's. A custom sending domain with your own SPF and DKIM isn't available yet, and it's on our backlog.
How is white-label different for agencies?
Agencies add three needs on top: separate workspaces per client, a way to bill clients, and per-client reporting. Those are operational questions rather than branding ones, and we cover them in the agency guide to white-label URL shorteners, including what Elido's reseller API does and doesn't do.
Do I need to host my own redirect infrastructure for white-label?
No. The usual setup is a CNAME from your short domain to the vendor's edge plus a DNS verification record. The vendor issues the TLS certificate and serves the redirects, so you only manage DNS. You do depend on the vendor's uptime, and your SLA to customers can't be stricter than theirs.
Try Elido
Paste a URL, get a working short link
No signup. Link lives for 30 days. Sign up to keep it forever.
Free account required. The free plan includes 25 links in total. Already have an account? Log in