Full white-label override. Custom domain. Branded client portal. White-labeled PDFs and email templates. Multi-tenant architecture with per-client isolation, account-manager assignments, and scoped permissions.
White-label at AIVZ is full-stack. The agency's brand identity replaces AIVZ's across every customer-facing surface — the URL the client visits, the dashboard they log into, the deliverables they receive, and the notifications they get. Seven specific override surfaces.
The client visits a domain you own — aeo.your-agency.com. Full DNS configuration support; SSL provisioning automatic via Let's Encrypt or your existing wildcard certificate. The AIVZ.app domain doesn't appear in the standard workflow.
Logo, favicon, login page treatment, dashboard header, sidebar branding. Light + dark theme variants, primary brand color, secondary brand color, custom font, tagline. Every UI surface picks up the override automatically.
The client logs into a portal that shows your brand exclusively — your logo, your color treatment, your support contact, your help links. The methodology terminology stays canonical; everything else is yours.
Scan reports, regression alerts, weekly summaries, executive briefings render with your brand: custom letterhead, color scheme, executive-summary template, contact info in the footer, logo as the document watermark.
Notification emails sent from your domain ([email protected]) with your branding throughout. Custom-domain email sending uses SPF/DKIM/DMARC alignment.
API endpoints proxied through your subdomain — api.your-agency.com/v1/scans/.... The AIVZ-branded API URL doesn't appear in webhook payloads, error messages, or response bodies.
For agencies running their own client dashboard (built in-house or with another platform), AIVZ ships a JS embed component that renders scan results, score history, and recommendation queues inside your dashboard. The embed inherits your dashboard's CSS context — no AIVZ branding on the embed surface unless you configure it.
A client onboarded through your white-labeled instance never sees AIVZ branding in the standard workflow. They see your brand at the URL level, the UI level, the deliverables level, the notification level, and the API level. AIVZ is the engine; your agency is the brand the client experiences.
White-label override has a deliberate boundary: the methodology stays canonical. Tier names, layer names, confidence labels, and the AI Visibility Stack tier color tokens don't get overridden. This isn't a technical limitation — it's a methodology-IP decision rooted in the discipline that gives the score credibility in the first place.
These tier names are part of the published methodology. The colors are too. They stay in place under white-label.
Every factor measurement carries one of these labels. They are part of the published methodology and don't get rewritten under white-label.
The factor names, the category structure, and the Stack layer mapping for each factor are canonical. White-label resellers don't rewrite factor names or rebrand the taxonomy — they deliver the canonical taxonomy under their own brand wrapper.
Under your white-label: A score of 78 displays as "AI Extractable" — the same tier name a client would see directly from AIVZ. The Stack breakdown shows "Access / Understanding / Extractability." A factor labeled "Strongly Inferred" displays that confidence label — not a custom rewrite. Your brand wraps the experience. The methodology stays the standard.
The methodology-IP discipline isn't a limitation imposed on white-label resellers — it's the feature that makes the white-label valuable. Three reasons the canonical methodology earns trust.
A client reading "AI Authority — 92" from your white-labeled report knows it means the same thing as "AI Authority — 92" from any other AIVZ provider. If clients hire a new agency in two years and that agency uses AIVZ, the historical scores port forward — same definition, same threshold, same method.
If every reseller renamed "AI Authority" to "Visibility Champion," the score would lose this portability. Methodology canonicality is what makes the score industry-standard rather than a private metric.
Procurement teams comparing AEO vendors can compare AIVZ scores from different resellers directly — the methodology is the same, so the comparison is apples-to-apples. If white-label allowed methodology overrides, comparison would require methodology audits at every provider.
The discipline protects clients who switch agencies, evaluate multiple providers, or run AEO across a portfolio of brands with different agency relationships.
AIVZ refines the 93-factor taxonomy, the confidence labels, the per-platform scoring, and the Authority Rank engine continuously. Refinements ship to all instances simultaneously — including white-label resellers. Your clients benefit without you managing version upgrades.
If methodology were reseller-overridable, every white-label instance would fragment into a methodology fork. Updates wouldn't propagate. Quality would diverge.
You position your agency as the AEO partner — the operator who runs the work, manages the relationships, and delivers the reports. You don't position as the methodology author — that's AIVZ's role, and your clients benefit from the canonical-methodology trust posture. The agencies that thrive on AIVZ white-label are the ones that lean into the canonical methodology.
Every client gets a logically isolated workspace; agency admins manage many workspaces from a single agency-level interface; clients see only their own data. The isolation is enforced at the data layer, not just the UI layer.
Cross-workspace data access is impossible by architecture, not just by permission.
| Role | Capabilities |
|---|---|
| Workspace Owner | Full workspace access including billing visibility (typically the client's primary contact). |
| Workspace Admin | Full operational access; cannot modify billing or workspace settings reserved for the Owner (typically the agency account manager). |
| Workspace Member | Read scans and recommendations; cannot trigger fix execution or modify workspace settings (client's broader team). |
| Workspace Viewer | View dashboards and reports; no operational actions (read-only stakeholders). |
The white-label setup process runs through five stages, typically completing within one working week from application approval.
You submit the agency application. We respond within 1 business day with approval, clarification questions, or referral to Pro-tier if Agency-tier isn't the right fit.
1 business dayCover your client portfolio, current stack, white-label requirements, and the scope of the first onboarded client. Confirm approval; hand off to onboarding; schedule white-label setup session.
30 minutesConfigure your custom domain (DNS records you provide), upload brand assets (logo variants, color tokens, font URL), set up SPF/DKIM/DMARC for email sending, configure PDF templates, set role-based access defaults. By end of session, your white-label instance is live at your domain.
~2 hoursBulk-import the first client's domains, assign account managers, set credit budgets, configure scheduled reports, run the first scan. End-to-end live within a working day.
~1 working dayYour team takes over day-to-day operations. AIVZ provides Slack-based support during onboarding (first 30 days) plus standard ticket-based support thereafter.
Day-30 transitionWhite-label at scale invites security review. Enterprise prospects and security-conscious agencies typically need to confirm specific architectural and compliance properties before approving the partnership.
Tenant ID enforced as query-time discriminator on all data access; cross-tenant queries blocked architecturally.
All stored data encrypted at rest. TLS 1.2+ for client traffic, white-label traffic, API traffic, inter-service traffic.
At Enterprise tier — integrate with Okta, Azure AD, Google Workspace, or other identity providers.
Across all workspace and agency-level operations — exportable for compliance reporting.
Daily backups with documented recovery time and recovery point objectives; details available under NDA.
Permission scoping at agency-, workspace-, and role-level.
Enterprise tier supports specified-region data residency for GDPR and regional compliance.
SOC 2 Type II audit visible at /trust. GDPR-compliant data handling. Sub-processor inventory disclosed.
| Capability | Free | Pro | Agency | Enterprise |
|---|---|---|---|---|
| Custom domain hosting | — | — | ● | ● |
| Brand asset replacement | — | — | ● | ● |
| Branded client portal | — | — | ● | ● |
| White-labeled PDF reports | — | — | ● | ● |
| White-labeled email templates | — | — | ● | ● |
| API subdomain proxy | — | — | ● | ● |
| JS embed component | — | — | ● | ● |
| Multi-tenant workspaces | — | — | 50 client domains | Unlimited |
| Account-manager assignments | — | — | ● | ● |
| Credit budget allocation | — | — | ● | ● |
| Role-based access control | — | — | ● | ● |
| Bulk client onboarding | — | — | ● | ● |
| Aggregate agency dashboards | — | — | ● | ● |
| SSO / SAML | — | — | — | ● |
| Specified-region data residency | — | — | — | ● |
| Dedicated CSM | — | — | — | ● |
| Custom SLA | — | — | — | ● |
We respond within 1 business day; setup takes one working session; first client onboarded within a working week.
