Full whitelabel: run LLM Pulse under your own brand

Full Whitelabel lets you rebrand LLM Pulse completely with your own identity. Your clients see your brand, your domain, and supported client-facing emails. Available on Enterprise plans.

With full whitelabel, you can:

• Serve AI visibility analytics under your own domain, logo, and colors
• Send client-facing emails from your brand through your SMTP server or an explicitly configured product-neutral sender
• Give clients a portal that never shows the LLM Pulse name
• Resell AI search reporting as your agency's own product

What it does

• Custom branding: your logo, brand name, and primary color throughout the platform
• Custom domain: serve the platform from app.yourbrand.com instead of llmpulse.ai
• Custom SMTP: send supported client-facing emails from your own email address
• Custom favicon: your icon in the browser tab
• Login page branding: your logo and brand on the login screen
• Email templates: supported client-facing emails use your brand name, custom domain links, and your sender address when SMTP is configured
• Crawler identity: opt-in project crawls use the stable, product-neutral AnalyticsCrawler/1.0 User-Agent shown in Project Settings

How to use it

1. Open Extras > Whitelabel configuration in the sidebar
2. On the Shared branding tab, set your brand name, primary color and logo
3. On the Whitelabel portal tab, upload your favicon
4. Configure your custom domain (requires DNS setup)
5. Configure custom SMTP to enable emails from your own sender domain, unless platform operators have enabled the product-neutral shared sender
6. Use Test Connection to verify SMTP settings
7. Preview email templates to see how branded emails look

The branded login and logged-in app appear on your custom domain. The configuration page stays on llmpulse.ai and keeps the LLM Pulse branding. After saving, use Open branded portal to check the client-facing version.

Portal analytics

AI Traffic and Agent Analytics appear in the client sidebar, and the portal connects and manages its own sources. In AI Traffic that covers Plausible, Piano Analytics, PostHog and Adobe. In Agent Analytics it covers Cloudflare and Bunny CDN, an Amazon S3 or CloudFront log bucket, and CSV or log uploads, plus log drains once the portal runs on your own domain. Google Analytics and Google Search Console are connected from Project Settings, through a Google app that does not carry our brand, and disconnecting either one stays in the main application. Everything stays inside the team member permissions you granted. To change what a saved source reads, such as another property, zone or S3 location, the portal connects it again with its own Google account, token, key or S3 key pair.

API access

• API keys under your brand: your portal manages its own API keys on your domain. Each key carries your own prefix, and the API reference beside it shows your brand and your domain as the base URL.
• Four sections of the API reference are hidden in your portal because their content names LLM Pulse and cannot be rebranded: Webhooks, Integrations, OAuth, and the API changelog. Read those on the main llmpulse.ai app.
• MCP setup is available in a Full Whitelabel portal on its custom domain when portal OAuth is enabled. In other portals, set up MCP in the main application.

Tips & notes

• Available on Enterprise plans only (account owners only, not members)
• Custom domain requires DNS CNAME record pointing to LLM Pulse
• SMTP setup requires SPF, DKIM, and DMARC records for email deliverability
• Supported client-facing emails use your branded templates, including invitations, authentication emails, scheduled custom reports, exports, reputation reports, weekly summaries, and analytics connection alerts
• Email delivery remains paused until the custom domain is configured and either custom SMTP or an explicitly configured product-neutral sender is available. This prevents platform-host links or headers from reaching clients.
• Custom SMTP is required if you want those emails to use your branded sender domain
• Other default product emails that are not whitelabel-safe are not sent to client team members. The account owner may still receive normal vendor-relationship messages according to their email preferences.
• Team Members and account roles are managed only on the main llmpulse.ai app. Those routes are blocked on customer domains.
• Customer portals suppress platform system banners and product marketing or identity scripts.
• The Integrations page is hidden in whitelabel mode