Platform operators

Deploy the analytics engine
under your own brand

The full governed quant workflow platform — deterministic analytics, approval gates, audit trail, committee-ready reports — deployed on your domain, in your Azure tenant, with your name on it. Your clients never see Nexqion.

What you get

Your platform. Your clients. Your brand.

Your brand name and logo — no Nexqion visible
Your own domain (analytics.yourbrand.com)
Your Azure tenant — client data never leaves your environment
Your colour scheme via environment config
All governed analytics, approval gates, and audit trail intact
Nexqion branding on any client-facing screen
Data routed through Nexqion infrastructure
Re-engineering of core analytics engine required

All governance properties are preserved under your brand: deterministic reproducibility, full audit chain, approval gates, and compliance-ready PDF output. You are not buying a reskin — you are deploying an enterprise governance engine.

Regulatory basis: SR 11-7 · EU AI Act · ESMA 2024 · GDPR / Schrems II. Data sovereignty is structural — your client data stays inside your Azure tenant by design.

Who deploys white-label

Fund administrators

Offer a governed analytics layer to all your fund clients under your own brand. One deployment, hundreds of end clients — each with isolated data.

Wealth platforms

Embed institutionalgrade risk and reporting workflows into your existing platform. Compliance-grade output without rebuilding your analytics stack.

Investment advisory platforms

Give your network of investment advisers a fully branded analytics copilot. Looks like an internal tool. Governed, auditable, and reproducible like an enterprise system.

Deployment steps

architecture

Four-step deployment

From Nexqion delivery to your branded platform, running in your infrastructure.

01

Your brand layer

Domain, logo, company name, agent name — all from environment config. Zero code changes.

02

Your Azure tenant

API, worker, storage, and database run inside your subscription. Nexqion has no access to your data.

03

Your identity provider

Users log in via your Microsoft Entra or existing SSO. Full role-based access control.

Technical setup
01

Brand config

Set NEXT_PUBLIC_BRAND_* environment variables: company name, agent display name, tagline. Applies globally across all UI screens in one place.

02

Domain + DNS

Point your subdomain (e.g. analytics.yourbrand.com) to the deployed frontend. TLS certificate provisioned automatically via Azure.

03

Azure tenant

Deploy API and worker containers into your Azure subscription. Storage, queue, and database stay inside your tenant boundary — no cross-tenant data movement.

04

Identity

Connect your Microsoft Entra External ID or existing IdP. Users authenticate against your identity provider, not Nexqion's.

Data sovereignty

Client data stays inside your Azure tenant

No cross-tenant routing. No Nexqion access. No exceptions.

Azure Blob Storage

All uploaded datasets, artifacts, and PDFs stored in your subscription.

PostgreSQL

Run state, approvals, audit trail — all in a database you own and control.

Container Apps

API and worker run in your Azure Container Apps environment. You manage the runtime.