Multi-Tenant Routing Architecture

Multi-tenant custom domain biolink: brand authority

Allow every creator, brand, and corporate client to display their bio link under their own domain name (e.g., links.clientbrand.com) via multi-tenant CNAME routing.

DNS Routing Engine

How CNAME custom domain mapping works in Bibiolink

In a typical hosted SaaS, enabling custom domains requires manual administrative intervention or expensive enterprise plans.

Bibiolink contains a native multi-tenant routing engine:

  • The user inputs their desired domain or subdomain into their settings.
  • The user creates a DNS CNAME record pointing to your server's hostname.
  • Bibiolink resolves incoming host headers to verify and match the registered tenant account.
  • Once configured, incoming HTTP/HTTPS requests with that `Host` header immediately serve the user's bio profile under their brand.
DNS Record ConfigurationStandard CNAME
# End-user DNS provider configuration Type: CNAMEHost / Name: links (or @)Target / Value: yourdomain.comTTL: Automatic / 300 seconds # Bibiolink automatically verifies propagation
Infrastructure

Subdomains, root domains, and reverse proxy routing

Bibiolink supports three levels of domain routing:

  • Path Routing: Default fallback (`yourdomain.com/username`).
  • Wildcard Subdomains: Instant deployment (`username.yourdomain.com`).
  • Custom Third-Party Domains: External CNAME (`links.clientbrand.com`).
Bibiolink multi-tenant custom domain CNAME routing and multi-gateway billing integration
Routing DimensionSpecification
CNAME VerificationAutomated In-Script DNS Lookup
SSL ProtocolAutomatic In-Script SSL Provisioning
Domain IsolationStrict Multi-Tenant Database Mapping
Root Domain SupportSupported via ALIAS / ANAME or Cloudflare CNAME flattening

Related Server Guides

Custom Domain FAQ

Common questions about multi-tenant custom domains

How do subscribers point their custom domain to my platform?

Subscribers add a standard CNAME record in their DNS management dashboard (e.g. at GoDaddy, Namecheap, or Cloudflare) pointing `links.theirbrand.com` to your platform's primary domain. Bibiolink automatically detects the incoming CNAME host and routes visitors to that subscriber's bio link.

How does SSL certificate configuration work for custom domains?

Bibiolink handles SSL automatically. When a subscriber configures a custom domain, the script performs automated DNS verification and provisions SSL certificates automatically, ensuring seamless HTTPS connectivity.

Can subscribers also use system subdomains?

Yes. In addition to custom external domains, every subscriber can be assigned an instantaneous system subdomain (e.g. `creator.yourdomain.com`) as well as standard path routing (`yourdomain.com/creator`).