White-Label Domains: Giving Workspaces Their Own Identity

When a crew member opens a gig offer from their production company, the experience should feel like it belongs to that company. The logo should be theirs. The colors should be theirs. And the URL in the address bar should be theirs too, not a generic SaaS domain that undermines the professionalism they have spent years building.

Why Custom Domains Matter

Brand consistency is not vanity. For production companies, it is a business tool. When you send a client a link to review their event roster, the URL tells a story. crew.yourcompany.com says "we have our act together." A third-party subdomain says "we use someone else's tool." The difference is subtle but real, especially when competing for enterprise clients who evaluate every touchpoint.

For crew-facing use, the calculus is similar. A crew member who bookmarks their gig portal wants to see a familiar URL. When they share the link with a colleague, it should look like a recommendation for your company, not an advertisement for your software vendor.

White-label domains also matter for email deliverability. Links embedded in gig notifications and pay stubs that point to your own domain build trust with spam filters and recipients alike. A consistent sender domain paired with a consistent link domain reduces the chance of landing in promotions or junk folders.

How Multi-Tenant Domain Routing Works

In a multi-tenant architecture, every workspace already has a unique identifier. JamCrew assigns each workspace a subdomain by default: yourcompany.jamcrew.io. The app resolves the tenant from the hostname on every request, loads the workspace configuration, and renders the appropriate branding.

Custom domains extend this same mechanism. Instead of only matching against *.jamcrew.io subdomains, the routing layer also checks incoming hostnames against a table of registered custom domains. When a request arrives at crew.yourcompany.com, the system looks up which workspace owns that domain and proceeds exactly as it would for a subdomain.

The DNS setup is straightforward from the customer's perspective. They add a CNAME record pointing their chosen subdomain to our platform. The CNAME target is a single hostname that routes all custom domain traffic through our infrastructure. No IP addresses to hardcode. No DNS changes if we migrate servers.

SSL at Scale

Every custom domain needs its own SSL certificate. Visitors should see the padlock icon regardless of whether they are on a subdomain or a custom domain. Manual certificate management does not scale, so the process has to be automated.

Certificate provisioning happens on first request. When a new custom domain hits the platform, the system verifies DNS resolution, issues a certificate through an automated certificate authority, and installs it. Renewal happens automatically before expiration. The workspace admin never touches a certificate file or troubleshoots an SSL error.

The technical challenge is handling the provisioning window. Between the moment a customer points their DNS and the moment the certificate is live, there is a brief gap where HTTPS is not available. The platform handles this gracefully by serving a redirect or a status page until provisioning completes, which typically takes under two minutes.

Theming Across Domains

A custom domain without custom branding is incomplete. The theming layer in JamCrew applies workspace-specific colors, logos, and fonts regardless of the domain. Whether a crew member accesses the platform through yourcompany.jamcrew.io or crew.yourcompany.com, the visual experience is identical.

The platform chrome, the navigation shell, tab bar, and system UI, maintains structural consistency. This is intentional. Workspace admins control their brand expression within the content area: card headers, accent colors, logo placement. The underlying interaction patterns stay familiar across every workspace, which means crew members who work with multiple production companies do not have to relearn the interface.

The Boundary Between Platform and Brand

The design challenge with white-labeling is knowing where the platform ends and the brand begins. Let too much change and the product becomes unrecognizable. Lock too much down and the customization feels hollow.

JamCrew draws the line at structure. The spacing grid, component architecture, motion curves, body typography, and icon system are fixed. They are the reason the app feels solid and consistent. Everything on top of that structure, the colors, the logo, the display font, the accent, is the workspace's canvas.

This approach means a crew member who works for three different production companies sees three different brands but one familiar tool. They know where to find their gigs, how to check in, and where to review their pay. The brand wrapping changes. The product underneath does not.