> **Building with AI coding agents?** If you're using an AI coding agent, install the official Scalekit plugin. It gives your agent full awareness of the Scalekit API — reducing hallucinations and enabling faster, more accurate code generation. > > - **Claude Code**: `/plugin marketplace add scalekit-inc/claude-code-authstack` then `/plugin install @scalekit-auth-stack` > - **GitHub Copilot CLI**: `copilot plugin marketplace add scalekit-inc/github-copilot-authstack` then `copilot plugin install @scalekit-auth-stack` > - **Codex**: run the bash installer, restart, then open Plugin Directory and enable `` > - **Skills CLI** (Windsurf, Cline, 40+ agents): `npx skills add scalekit-inc/skills --list` then `--skill ` > > `` / ``: `agent-auth`, `full-stack-auth`, `mcp-auth`, `modular-sso`, `modular-scim` — [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/) --- # Branded custom domains Custom domain branding lets you provide a fully branded authentication experience for your customers. By default, Scalekit assigns a unique environment URL (like `https://yourapp.scalekit.com`), but you can replace it with your own domain (like `https://auth.yourapp.com`) using DNS CNAME configuration. This branded domain becomes the base URL for your admin portal, SSO connections, directory sync setup, and REST API endpoints—giving your customers a seamless, on-brand experience throughout their authentication journey. This guide shows you how to configure a CNAME record in your DNS registrar and verify SSL certificate provisioning for your custom domain. | Before | After | |--------|-------| | `https://yourapp.scalekit.com` | `https://auth.yourapp.com` | **Production environment only:** CNAME configuration is available only in production environments. Ensure you're working in your production environment before proceeding. Custom domains use DNS CNAME records to route traffic from your branded domain to Scalekit's infrastructure: 1. Your custom domain (e.g., `auth.yourapp.com`) points to Scalekit's infrastructure via a CNAME record 2. Scalekit automatically provisions and manages SSL certificates for your domain 3. All Scalekit services (Admin Portal, SSO endpoints, directory sync, REST API) become accessible through your branded domain This architecture ensures your domain remains on your brand while leveraging Scalekit's secure, scalable infrastructure. CNAME records safely route traffic without exposing your configuration, and SSL certificates automatically provisioned by Scalekit ensure all traffic to your custom domain is encrypted (HTTPS). **Existing integrations remain unaffected:** Integrations configured before the CNAME change will continue to work with your previous Scalekit domain. They don't automatically update to use your custom domain. ### DNS record reference When configuring your CNAME record, you'll need to provide the following fields: | DNS Record Field | Example Value | Description | |------------------|---------------|-------------| | Record Type | `CNAME` | Canonical Name record that creates an alias from your domain to Scalekit's infrastructure | | Name/Host/Label | `auth.yourapp.com` | Your custom subdomain (copied from Scalekit dashboard) | | Value/Target/Destination | `scalekit-prod-xyz.com` | Scalekit's endpoint URL (copied from Scalekit dashboard) | | TTL | `3600` | Time to Live in seconds (optional, typically set by your registrar's default) | **Field names vary by registrar:** Different DNS registrars use different names for these fields. The `Name` field might be called "Host" or "Label", and the `Value` field might be called "Target" or "Destination". The values you enter remain the same. ## Set up your custom domain Let's set up your custom domain by adding a CNAME record to your DNS registrar and verifying the configuration. 1. CNAME configuration is available only for production environments. Log into the Scalekit dashboard and ensure you're working in your production environment. 2. In the Scalekit dashboard, go to **Dashboard > Customization > Custom Domain**. This page displays the CNAME record details you'll need to configure in your DNS registrar. ![](@/assets/docs/guides/custom-domains/1.png) 3. Go to your domain registrar's DNS management console and create a new DNS record. Select `CNAME` as the record type. 4. In **Dashboard > Customization > Custom Domain**, copy the `Name` field (your desired subdomain). Paste this value into your DNS registrar's `Name`, `Label`, or `Host` field. 5. Still in **Dashboard > Customization > Custom Domain**, copy the `Value` field. Paste this value into your DNS registrar's `Destination`, `Target`, or `Value` field. 6. Save the CNAME record in your DNS registrar. The changes may take some time to propagate across DNS servers. 7. Return to **Dashboard > Customization > Custom Domain** in the Scalekit dashboard and click the **Verify** button. This validates that your CNAME record is properly configured and accessible. **Existing connections?:** If you have existing SSO or SCIM connections, they will continue to use your previous Scalekit environment domain. New connections will use your custom domain going forward. ### SSL certificate provisioning After successful CNAME verification, Scalekit automatically provisions an SSL certificate for your custom domain: - **Initial provisioning** - SSL certificate provisioning can take up to 24 hours after CNAME verification - **Check status** - Click the **Check** button in **Dashboard > Customization > Custom Domain** to verify SSL certificate status - **Still pending after 24 hours** - If SSL provisioning takes longer than 24 hours, contact our support team at support@scalekit.com for assistance **SSL certificate provisioning:** After the CNAME record propagates, Scalekit automatically provisions an SSL certificate for your custom domain. This process can take up to 24 hours. Click the **Check** button in the dashboard to verify SSL certificate status. ## External resources For detailed instructions on adding a CNAME record with popular DNS registrars: - GoDaddy: Add a CNAME record - Namecheap: How to create a CNAME record --- ## More Scalekit documentation | Resource | What it contains | When to use it | |----------|-----------------|----------------| | [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content | | [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas | | [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |