White-label short link software — what to pick
A short-link service under your own domain looks simple but the picking criteria are non-obvious. Here's the checklist that actually matters before you commit.
Pick the wrong white-label short-link platform and you find out at month three, when you've onboarded a dozen customers, signed a year-long agency contract, and discovered the platform doesn't support custom domains for tenants — or charges separately for analytics — or treats all your customers as one account on the back-end.
The decision looks simple from the outside. Short links have been around for fifteen years. The category is mature. Yet half the platforms calling themselves "white-label" miss something a real white-label business needs.
This is the checklist we hand to people asking which platform to pick. It's not about Linked.Codes specifically — it's the criteria you should run any candidate through before committing. Some of these we got wrong in our first build and had to rebuild later, so the list is partly self-flagellation.
The hard criteria — non-negotiable
If a platform fails any of these, it's not actually white-label.
Custom domain per tenant, with automatic TLS
Each of your tenants needs to be able to point their own domain at the platform. client1.com and client2.io should both work, with a working https:// certificate, without you having to manually issue or renew anything.
The implementation detail to ask about: "How does the TLS certificate get issued for a tenant's custom domain?" The right answer is "the platform issues it automatically when the DNS record verifies, via Let's Encrypt or similar." Wrong answers: "you upload your cert", "we issue once per year", "you need to email us." Anything that puts manual ops in front of a tenant onboarding will scale into a part-time job.
Tenant data isolation
Tenant A cannot see tenant B's links, scans, users, or settings. This is enforced at the database level, not just the UI level. Ask: "If tenant A's user logs in via tenant B's domain (mistaken or malicious), what happens?" The right answer is "they can't — the session is scoped to the tenant whose domain they came in via."
Stripe Connect or equivalent BYO billing
Tenants charge their own customers in their own Stripe account. Money flows to them; you charge them a separate platform fee. Without this, you become the merchant of record for everyone's transactions — which is a tax, compliance, and chargeback nightmare.
If the platform only supports "platform-side billing" (everyone pays the platform vendor, vendor remits to you), you're not running a white-label business; you're a reseller in front of someone else's payment processor.
Per-tenant branding
Logo upload, accent colour, brand name string, ideally a custom font. The branding has to apply across every customer-facing surface — dashboard, checkout, emails, share previews — not just the marketing site.
If branding only applies to the dashboard and the share preview / login email still says the platform vendor's name, tenants notice and price down.
The soft criteria — they tell you who's serious
Pass marks here separate "okay" platforms from "good" ones.
Self-serve domain verification
Customer wants to add their own domain. They should be able to add it from the dashboard, see DNS records to set up, hit a "verify" button, and have TLS provisioned within a few minutes. No support tickets, no Slack hand-offs, no waiting overnight.
If the platform requires emailing support to add a custom domain, multiply that friction across every tenant you'll have. It doesn't scale.
Separate sub-user accounts per tenant
Your tenants have their own teams. The platform should let tenant A invite five users to their account, all isolated from tenant B's users. Each user has a role (owner, editor, viewer or similar). This is table-stakes but a surprising number of platforms charge per-account-on-the-platform-side rather than per-tenant.
Analytics that don't disappear behind a paywall
Click counts, country breakdowns, referrer hosts, time-of-day distribution. If the platform charges separately for analytics or hides them behind a higher tier, your tenants notice — short links without scan data is half the value gone.
Reasonable rate limits
Free or low tiers shouldn't cap at "100 redirects per minute" or "1,000 scans per month." Real campaigns spike. A QR code on a billboard hit by one ad placement might do 10,000 scans in an hour. If the platform's rate limit kills the campaign, your tenant blames you.
A way to bulk-export data
Tenants come and go. When a tenant leaves your platform, they should be able to export their links and historical scan data as CSV or JSON. If not, they're hostage to your platform — and savvy tenants ask about exit before they sign up.
Webhook events for the things you'd automate
Link created, scan happened, user signed up. Webhooks let you wire the short-link platform into your own systems (CRM, billing, etc). Without them, you're bolting on integrations the hard way.
The pricing-model question
Three categories of white-label short-link pricing exist:
Per-link or per-scan caps. "Up to 1,000 links" or "100k scans/month". Predictable for the platform, frustrating for tenants who occasionally have a big campaign. Run the math against your tenants' real volumes before committing.
Per-seat or per-tenant flat fee. "$50/tenant/month, unlimited usage." Works well when you have many small tenants. Less attractive when tenants vary enormously in size.
One-time license + hosting. Larger upfront ($299-1,499) plus a small monthly fee for the platform's running costs. Good for budget predictability; less aligned with platform vendor's incentives if usage explodes.
Each model has trade-offs. Pick the one that matches how you want to charge your own customers — if you charge them per-tenant flat, run on a per-tenant flat backend so the margins stay clean.
The hidden gotchas
A few things that aren't on most checklists but are worth asking about:
What happens to tenant data when their hosting subscription lapses? Some platforms delete after 30 days. Some keep it indefinitely as soft-deleted. Some lock it (read-only) until they pay. Each is reasonable; you should know which.
Can the platform vendor see tenant data? Almost always yes — they run the database. But the question is whether they have policy controls. Reputable vendors don't query tenant data without a support reason. Ask about audit logs and access controls if you're handling regulated data.
What's the migration path away? If you decide year three to switch platforms or build your own, what does the migration look like? Bulk export of links + scan history is the minimum. The ability to retain link slugs (so old codes keep working when re-pointed at your own infrastructure) is the gold standard.
What's the SLA? Most small platforms don't offer formal SLAs. Reasonable. The question is whether they have a public status page, treat downtime as a crisis, and communicate during incidents. The way they handle their own outages tells you how they'll handle yours.
Does the vendor respect "powered by" preference? Some platforms force a "Powered by Vendor" footer on tenant pages. Others let you remove it (often at a higher tier). For real white-label, removing or replacing the footer is essential.
A scoring sheet
The scoring is rough but the directional signal is right: anything under 14 has gaps you'll feel in production.
If branding only applies to the dashboard and the share preview still says the platform vendor's name, tenants notice and price down.
The cost of the wrong platform
Migrating off a white-label short-link platform after you've onboarded customers is painful. Every printed QR code that points at the platform's domain has to be re-pointed (impossible if you don't control the domain). Every saved link your tenants have shared via email or chat has to migrate. Every analytics history has to be exported and somehow reconciled with the new platform's schema.
This is why the hard criteria matter — the cost of switching once you've launched is roughly equal to the cost of building from scratch, plus the relationship damage with customers who lived through the migration.
Spend a week scoring three or four candidates against the criteria above before signing up. The week is cheap; the lock-in isn't.
What we built
Linked.Codes is one of the platforms you can score against this list. It clears the four hard criteria; it's strong on most of the soft ones. No platform clears every criterion at every tier — pick the trade-offs you can live with based on which customers you're targeting.
There are other good platforms. The criteria above are the criteria, regardless of which one you pick.
What's the difference between "white-label" and "branded reseller"?
White-label: your domain, your branding, your billing, customer thinks the product is yours. Branded reseller: vendor's domain with your logo, vendor's billing, customer can tell it's a third party. White-label commands a higher price; reseller is faster to set up.
How important is custom domain support?
Critical. Without it, every QR code you ship is locked into the vendor's domain — you can't migrate without breaking every printed code. Custom domain is the escape hatch.
Should I worry about the platform vendor being a competitor?
If the vendor sells direct to your target customers, yes — you're competing with your own supplier. Look for platforms positioned as infrastructure rather than direct competitors. Most are; some aren't.
What's a fair price for a white-label short-link platform?
Per-tenant fees of $5-50/month are typical. One-time licenses run $299-1,499. Avoid platforms that charge per-link or per-scan at low caps — campaigns spike and the bills get scary.
Can I host this myself?
You can self-host an open-source short-link library. The work is in everything around it: multi-tenant routing, custom-domain TLS, billing, branding, analytics. That's six months of work. Most people are better off white-labeling.
Do I need a developer to white-label a platform?
For setup, no — the platforms above are no-code from the admin side. For specific integrations (your CRM, your billing, your CMS), having a developer on-call helps but isn't usually month-one critical.
What if I outgrow the platform?
Two paths: migrate to a heavier-weight platform with higher limits, or build your own. Both are easier if you've owned the customer's domain from day one — you can swap the backend without changing any URL the customer has shared. This is why custom domain support is so non-negotiable.
Try it on your own domain
Branded short links and dynamic QR codes, on your subdomain or your own domain. One-time purchase, no per-click fees.
