White-Label IoT Monitoring Under Your Own Brand
A white-label IoT platform lets you deliver monitoring to your customers under your own name. In ioX-Pulse you set the app name, logos, favicon, home-screen icon and brand colors, point your own domain at the workspace, and your customers sign in to your product.
The alternative is building a portal yourself, which means a front end, an account system, dashboards, alerting and a team to keep all of it running while your actual product waits. White-labeling gives you the same customer experience without the engineering program behind it, and you keep the parts that are genuinely yours: the hardware, the deployment, the relationship.
- Your logo and colors throughout, tone-mapped automatically so dark mode does not need a second set
- Your own subdomain with its own TLS certificate, so the address bar and the padlock both say your company
- Invitations, password resets and alerts sent from your address, through your mail provider
- A mark of your choosing on dashboards your customers share publicly, reaching people who never sign in
- Network server connection details can be hidden entirely, so the plumbing under your service stays yours
- Every customer account inherits the same branding, so nothing drifts as you add customers
Every mark your customer sees
What You Can Put Your Name On
Branding is a settings page, not a professional services engagement. Here is exactly what you can put your own name and marks on.
| Asset | What it is |
|---|---|
| App name | Replaces the product name throughout the interface. |
| Menu logo | Your mark in the sidebar, on every page your customer visits. |
| Login logo | Sits above the sign-in form. Leave it empty and the menu logo is used here too. |
| Favicon | The icon in the browser tab. |
| App icon | Shown when somebody saves your portal to their phone home screen. Without one, phones show a plain letter tile. |
| Login background | An optional full-bleed image behind the sign-in page. |
| Login headline and subtext | Your own words on the sign-in screen when no background image is set. |
| Brand colors | Primary, accent, and optionally the left menu background. The interface adapts them for dark mode automatically, so you do not supply a second palette. |
Uploads and removals take effect immediately rather than waiting for a save, so you can see a logo in place before you commit to the rest of the page.
Trusted by teams monitoring critical infrastructure
Your address bar, your certificate
Serve It From Your Own Domain
Branding stops working the moment somebody looks at the address bar. Point a subdomain of your own at the workspace and that stops being a problem: your customers reach your portal at your hostname, with a certificate issued for your company.
Name it
Enter a subdomain you control, such as iot.yourco.com. The card then shows you the two DNS records to add.
Point it
Add the records at your DNS provider. Either one proves ownership, and adding both makes activation finish fastest.
Activate
A TLS certificate is issued for your hostname. You do not have to wait on the page — your admins are emailed when it goes live.
5–30 MINUTESTotal time is about half an hour, and most of that is waiting for the certificate rather than doing anything. Changing or removing the hostname later is a button, not a support ticket.
The messages you never think about
Send From Your Own Address
Most of what your customers receive from the platform is email they did not ask for and cannot ignore. If those arrive from a name they do not recognize, your branding has a hole in it exactly where trust matters most.
Connect your own mail provider and every one of those messages goes out from your address, with your sender name, through your infrastructure.
Test it before a customer sees it
Verify the connection and send yourself a live test before any of it reaches a customer — and the test tells you which sender and which reply address were used.
Set the support address even if you keep the platform sender
Separately, a support address of your choosing becomes the Need help? line in the footer of every message, and the address replies go to — so a customer replying to an alert reaches your team rather than a no-reply mailbox.
Down to every account
Your Brand Everywhere Your Customers Look
Branding is set once at the workspace level and reaches everything below it. That is deliberate: a consistent identity across every customer account is what makes them feel like parts of one product rather than a collection of logins.
No per-account override to drift out of step — and nothing to redo when you add a customer.
Every customer account
Inherits your branding automatically. There is no per-account override to drift out of step, and nothing to redo when you add a customer.
Publicly shared dashboards
Dashboards your customers share by public link carry a mark of your choosing in the corner, and it can point at your own site. That reaches people who never sign in at all.
The machinery underneath
Network server connection details can be switched off across the workspace, so a customer looking at a gateway sees your service rather than the machinery underneath it.
WHITE-LABELS THE SERVICE, NOT JUST THE UI
