DASHBOARDS & GRIDS
White-label analytics
Your logo, your colours, your theme, on dashboards your teams and customers open every day. The vendor stays invisible unless you want it seen.
- Your team logs into somebody else's product
- Vendor colours, vendor domain, vendor name
- Your logo, your colours, your theme
- Charts and widgets follow the branding
What white-label means
A white-label product is one you can present as your own. The logo in the corner is yours, the colours are your palette, the theme matches your other tools, and the vendor's name appears nowhere unless you choose to show it. The product underneath is the same for every customer; the surface belongs to each. For analytics, the surface is dashboards, data grids and charts, which are opened more often than any other screen a business runs, so the surface matters more here than for most software.
The lead visual makes the point in one glance. The same sales overview - 952 orders, 14 urgent, 36 rejected - reads as somebody else's product under a vendor logo and vendor greys, and as yours under your logo and your palette. The numbers did not change. Who the dashboard appears to belong to did.
When it matters
Least when the only users are the team that bought the product; they know what it is. Most when the users did not buy it. Internal teams across a large organization, who should see one coherent set of company tools rather than a collection of vendors. Partners - dealers, franchisees, suppliers - who are given a dashboard of their own performance and should see your brand on it. Customers, if dashboards are part of what you sell, for whom a third-party logo is a question about who they are really dealing with. In each case the branding is not decoration; it is who the dashboard appears to come from.
What carries the brand
The logo and the name, obviously. The colour palette, applied as a theme rather than painted on one screen. And, the part that is easy to miss, the charts and widgets: chart series colours, KPI tiles, grid headers. A product that puts your logo on the login screen and then draws every chart in the vendor's blue is branded on the door and not inside. Since the charts are the most-seen pixels on any dashboard, the test of a white label is whether the chart palette is yours.
| Check | What to look for | Why it matters |
|---|---|---|
| Logo and name | Yours, everywhere a logo appears | The product reads as yours to whoever opens it |
| Colours and theme | Your palette, applied as a theme | Consistency with your other tools |
| Charts and widgets | Follow the configured branding | The most-seen pixels are the chart colours |
| Where it runs | Your infrastructure | A branded front on a vendor-hosted back is half a white label |
| Exports | Branded where they carry a header | Exports travel further than screens |
| The vendor's name | Absent unless you want it shown | Partners and customers should not meet a third party |
Theming should be a configuration, not a project. A palette and a logo set once at deployment, applied to every dashboard, grid and chart from then on, including the ones configured next year. If a rebrand means re-skinning forty dashboards by hand, the product is not white-label; it is customizable, which is a different and more expensive promise.
Brand and boundary
White-label and "runs in your infrastructure" are often sold together and are worth checking together. A branded front end on a vendor-hosted back end is half a white label: it looks like yours and lives with someone else. When the whole product - the index, the dashboards, the assistant - runs on your servers or your private cloud under your domain, the brand and the boundary agree, and the question "whose system is this?" has one answer. Runs in your infrastructure covers the boundary half.
The endpoint is part of the brand
One more surface, newer than the others: the MCP endpoint that AI clients connect to. When a team adds a server in Claude or Cursor, the name and the address they see are part of the product's face. A white-label MCP server is one that answers at your domain under your name, so that the AI tools, like the dashboards, present your data as yours. The enterprise MCP server describes what else such a server needs.
None of this is vanity. A dashboard that looks like part of the company gets opened; one that looks like a vendor's tool gets delegated to whoever "owns the tool". Adoption follows familiarity, and branding is the cheapest familiarity there is.
What to ask a vendor
Does the branding apply as a theme or screen by screen? Do charts and widgets follow it? Where does the product run, and on whose domain? Does your name appear on exports? And can the vendor's name be removed entirely, not merely shrunk? A vendor who can answer yes to all five is offering a white label. A vendor who answers the first and goes quiet on the rest is offering a logo slot.