Skip to content
JACAV

White-label & multi-tenant

Managed service providers and platform teams need one console that shows every customer at once, and a per-customer view that reveals nothing about the others. Both come standard, fully white-labeled.

Same maths

Fleet view and drill-down reconcile

The platform overview and each tenant dashboard compute health from the same formula, so a number never changes meaning depending on which screen you are looking at.

Fleet view and drill-down reconcile

Complete data isolation

A customer admin sees only their own accounts. The tenant filter is enforced on the data, not hidden in the interface.

Your brand

White-label to the accent colour

Brand name, logo, tagline, and palette are per-tenant. Resell it as your own product; the charts recolour with the theme.

The same estate, two views

Your console, and your customer’s

Above the line you see every tenant at once. Below it, a customer sees only themselves — under their own brand, with the charts recoloured to their palette. Both are computing health from the same formula.

Provider fleet console showing combined spend and per-tenant health across every customer under management
Provider view — every tenant in one console, ranked by what needs attention first. Demo estate.
A fully rebranded tenant dashboard for Halverson Freight, showing only that customer's clusters, spend, and findings
Tenant view — the same product under the customer’s own brand and palette, scoped to their estate alone. Demo estate.
What you control

Rebranded to the accent colour

White-labeling that stops at the logo leaves your customer looking at someone else’s product. These four are configured per tenant.

  1. 01

    Brand, logo, and tagline

    Per tenant, not per deployment. One installation serves every customer under its own identity.

  2. 02

    Accent colour through to the charts

    The palette is tokenised, so a tenant theme recolours the visualisations rather than leaving a branded header above someone else’s product.

  3. 03

    Isolation enforced on the data

    A customer admin sees only their own accounts. The tenant filter lives in the query layer, not in the interface — hiding a row in the UI is not isolation.

  4. 04

    Fleet and tenant views reconcile

    The platform overview and each tenant dashboard compute health from the same formula, so a number never changes meaning depending on which screen it is read from.

Questions

What partners ask

Can my customers tell it is Cloud Dongle?

Not from the product surface. Brand name, mark, tagline, and palette are per-tenant configuration, and the charts follow the theme.

Can one customer see another customer’s estate?

No. Scoping is applied to the data access itself rather than to the rendering, so there is no view that returns another tenant’s rows for the interface to then hide.

Is self-hosting available?

Yes, on the partner arrangement — for providers whose own customers require the data to stay inside their infrastructure.

Start here

Point it at one cluster and see what it finds

The sandbox runs on demo data, so you can look before you connect anything. When you are ready, access is read-only and nothing changes without your approval.

Open the live sandbox
Talk to a founder

Built by Anto and Edwin · Jacav