Your brand.
Their experience.
Your clients never need to know what powers the platform. PulseCargo™ white-labels the entire experience — custom domain, branded emails, your color system, client-isolated analytics — so every touchpoint reinforces your brand, not ours.
Every client-facing surface carries your brand.
Setup takes minutes. Every visual and communication surface your clients touch is yours.
Your clients never see PulseCargo.
Unless you choose to include an attribution line, the platform is entirely yours. No PulseCargo logo, no PulseCargo email headers, no PulseCargo subdomain leaking into browser bars or email clients.
The same applies to mobile views, email notifications, document download headers, and public tracking links.
15 languages. Per-user preference. Zero configuration.
Your clients set their own language. You don't need to configure anything per client — each user selects their preference on first login, and the portal switches immediately.
Right-to-left layout support included for Arabic. All 15 locales cover the full portal — shipment views, documents, analytics, and notifications.
Per-tenant isolation that isn't just a filter.
Dedicated database per tenant
Each tenant runs on a separate SQL Server database instance — not a shared database with tenant_id column filtering. One tenant's data is structurally unreachable from another tenant's session, even under misconfiguration or a compromised query parameter.
- No shared connection pool across tenants
- EF Core query filters as defense-in-depth
- Azure SQL Row-Level Security as second layer
- Per-tenant Azure Blob storage containers
- 61 controllers reviewed for cross-tenant exposure
Shared database, row-level filter
Most multi-tenant platforms use a single shared database with a tenant_id column on every table. Access control is enforced in the application layer — a bug, a misconfigured query, or a missing WHERE clause can expose another tenant's data.
- Shared schema means shared risk surface
- Application-layer-only enforcement
- Single misconfiguration exposes all tenants
- Connection pool shared across tenants
18 client-facing reports. Fully isolated by account.
Your clients access their own analytics — shipment performance, cost trends, carrier scorecards, emissions data — without ever seeing your other clients' numbers. Power BI Row-Level Security enforces client isolation at the report engine level, not just the application layer.
- 18 reports available to client portal users (Enterprise tier)
- Row-Level Security enforced at the Power BI dataset
- Client users cannot escalate to company-level reports
- Per-client feature flags control report access
- Branded report headers with your company name
Different feature sets for different client tiers.
Not every client needs the full suite. PulseCargo supports per-client feature flag configuration — you control which modules, reports, and capabilities each client account can access from within your operator dashboard.
- Module-level access control per client account
- Report-level access within the analytics suite
- ESG reporting access configurable per account
- Public tracking link generation can be enabled/disabled
- Operator dashboard for managing client configurations
White-label questions answered.
What does the white-label configuration include?
Custom subdomain, your logo and color system, custom email sender domain and templates, and your company name throughout all client-facing interfaces. Clients never see PulseCargo branding unless you choose to include it.
How does per-tenant database isolation protect client data?
Each tenant runs on a dedicated SQL Server database — not a shared database with row-level filtering. One tenant's data is structurally unreachable from another tenant's session. EF Core query filters and Azure SQL Row-Level Security add defense-in-depth on top.
Which languages does the client portal support?
15 languages: English, German, French, Spanish, Portuguese, Italian, Arabic, Chinese (Simplified), Japanese, Korean, Vietnamese, Thai, Turkish, Corsican, and Hindi. Language selection is per-user — your clients set their own preference without any configuration on your side.
Do clients see each other's analytics data?
No. Power BI Row-Level Security is enforced at the report level. A client user can only access reports scoped to their account. There is no shared report view where clients could see each other's freight or financial data.
Can I give different clients different feature access?
Yes. Per-client feature flags let you control which modules, reports, and capabilities each client account can access — set from your operator dashboard without any code changes.
See what your branded portal looks like.
We'll configure a white-label demo environment with your logo and colors so you can see the full client experience before committing.
Request a branded demo