Section 16.4 · Catalog v16.4.0 · Updated April 21, 2026
The Complete AIVAON Service Catalog
Twelve core products plus ten §16.4 expansion products — twenty-two in total — organized into four families, all consuming a single Platform Spine. Engineered as one platform. Sold as independent products. That distinction is the difference between a platform that customers experience as coherent and a portfolio of acquisitions stitched together with integration scaffolding.
- Products
- 22
- commercially independent
- Families
- 4
- commercial groupings
- Platform Spine substrates
- 10
- shared by every product
- SKU × product cells
- 110
- fully populated
Ask the doctrine — on your device, no server round-trip
Self-demonstrating the AIVAON Hybrid product: every answer is computed in your browser using the bundled §16.2 catalog and (when WebGPU is available) WebLLM synthesis on your local GPU. Same architecture Hybrid deploys to customer devices.
On-device Catalog Doctrine Assistant
Loading on-device assistant — runs entirely in your browser.
The Catalog Doctrine — seven binding principles
Every implementation decision across the catalog products is governed by these seven principles. They are the difference between commercial coherence and platform fragmentation.
1 — Architectural singularity
Every product consumes the same Control Plane, Identity Fabric, Event Bus, Observability Substrate, Audit Pipeline, Billing Engine, Compliance Infrastructure, API Gateway, Policy Decision Point, and Secret Management. Deviations require a formal exception with a remediation path back to the unified substrate.
2 — Commercial independence
Every product is independently purchasable with standalone pricing, contracts, activation, and deactivation. Customers can enter through any product and expand along any vector without architectural or commercial friction.
3 — Composition by configuration
Combining products into a unified workflow is a configuration operation, not an integration project. A Realtime session automatically carries Agents context when Agents is entitled, Telephony routing when Telephony is entitled, Intelligence analytics when Intelligence is entitled, and Trust evidence when Trust is entitled.
4 — Entitlement-driven surface exposure
Product boundaries are enforced at the entitlement evaluation layer, not at code branches scattered across services. A single entitlement-model change cleanly expands or contracts the product surface a tenant experiences.
5 — Expansion-optimized onboarding
Every product surfaces adjacent products at natural expansion moments through organic capability surfacing — never through interruptive upsell prompts. Quantitative value estimates are derived from the tenant's observed usage.
6 — Unified operational accountability
Every product shares the same SLA framework, incident response, support escalation, security posture, and compliance posture. Enterprise customers purchasing multiple products experience one operational relationship — not twelve.
7 — Catalog coherence preservation under evolution
New capabilities are positioned within the existing twelve-product catalog rather than spawning new products that fragment commercial clarity. New products are added only through a formal expansion process that justifies commercial independence.
The Platform Spine — ten substrates, every product
The Platform Spine is the cross-cutting substrate that every product consumes and that no product reimplements. Every product is measured against a Spine Adherence Score that quantifies its compliance with architectural singularity.
Live current adherence: /console/admin/platform-spine
Control Plane
Tenant configuration + entitlement decisions for every product, every operation.
Identity Fabric
Authenticated subjects across human users, service accounts, devices, and agents.
Event Bus
Carries every platform event across products with deterministic ordering and replay.
Observability Substrate
Metrics, logs, and traces with cross-product correlation IDs.
Audit Pipeline
Regulatory-grade evidence of every decision — append-only, signed, time-attested.
Billing Engine
Meters usage and produces invoices with per-product attribution and tier enforcement.
Compliance Infrastructure
Data residency, consent, regulatory constraint enforcement at the substrate layer.
API Gateway
Unified external interface with per-tenant rate limits, auth, and quota enforcement.
Policy Decision Point
Authorization evaluation for every operation against the tenant's active entitlement.
Secret Management
Key material and credential handling with HSM-backed roots and short-lived issuance.
22 products, four families
Every product is independently purchasable, independently activatable, and bound to the same Platform Spine. The family is the commercial conversation; the product is the purchase decision; the Spine is the delivery vehicle.
Family 1
Substrate
The communication infrastructure that the platform owns end-to-end — WebRTC media, PSTN telephony, unified messaging — plus the Section 16.4 expansion products that operationalize the substrate as enterprise capability: Voice Identity (voice-as-brand-asset with consent + rights + attestation) and Campaigns (outbound orchestration as a first-class commercial product).
realtime
AIVAON AIVAON Realtime
The substrate-owned WebRTC media platform — Opus, AV1, SVC, geo-distributed signaling, sub-300ms P95 — that wrapper platforms cannot match because they rent it.
First value in ≤15 min · self-serve
telephony
AIVAON AIVAON Telephony
Carrier-integrated PSTN with full A-level STIR/SHAKEN, E911 dispatchable location, and per-jurisdiction regulatory overlays across GH, US, and EU.
First value in ≤15 min · self-serve
messaging
AIVAON AIVAON Messaging
Unified SMS, WhatsApp, RCS, and regional messaging — one canonical message model, per-market compliance, channel-graceful degradation.
First value in ≤12 min · self-serve
voice_identity
AIVAON AIVAON Voice Identity
Voice-as-brand-asset — consent-first voice cloning, cryptographically attested rights management, cross-channel persona continuity, expressive emotion / style configuration, and survivable ownership transfer.
First value in ≤15 min · self-serve
campaigns
AIVAON AIVAON Campaigns
Outbound orchestration as a first-class commercial product — campaign definition, target list management with deduplication and suppression, hard-gate consent validation, regulator-aware pacing, agent / human handling, disposition tracking, and per-jurisdiction compliance reporting.
First value in ≤15 min · self-serve
Family 2
Intelligence
Every AI capability the platform delivers — Agents executing customer interactions, Intelligence turning the event stream into business insight, Hybrid running on-device — plus the Section 16.4 expansion products that extend intelligence in depth: Intelligence Graph (unified knowledge + retrieval), Coach (real-time agent augmentation), and Insights Pro (predictive + prescriptive analytics).
agents
AIVAON AIVAON Agents
Declarative agent definitions, hybrid model routing, MCP-native Tool Bus, conversation memory, prompt-injection defense — production-grade AI automation across every channel.
First value in ≤15 min · self-serve
intelligence
AIVAON AIVAON Intelligence
Conversation analytics, multi-touch outcome attribution, funnel and cohort analysis, drift detection, cost-per-outcome — the analytical depth that justifies platform commercial value.
First value in ≤12 min · self-serve
hybrid
AIVAON AIVAON Hybrid
Gate Reflex on-device latency, Workhorse on-device inference, Neural Voice on-device synthesis, signed manifests, device attestation — the on-device commercialization of hybrid intelligence.
First value in ≤15 min · self-serve
coach
AIVAON AIVAON Coach
Real-time agent augmentation — contextual guidance, live quality and compliance signals, escalation recommendations, and post-session coaching insights with peer benchmarking that converts the platform from agent-replacement to agent-enhancement.
First value in ≤15 min · self-serve
intelligence_graph
AIVAON AIVAON Intelligence Graph
Unified knowledge and retrieval substrate — source connectors, entity resolution, relationship mapping, hybrid retrieval (vector + keyword + graph), per-agent RAG configuration, and cross-agent knowledge sharing with isolation governance.
First value in ≤15 min · self-serve
insights_pro
AIVAON AIVAON Insights Pro
Predictive and prescriptive intelligence — intervention recommendations, outcome forecasting, churn prediction, multi-touch revenue attribution, and autonomous configuration optimization with rollback safety — the visionary differentiator that moves the market beyond descriptive analytics.
First value in ≤14 days · sales-assisted
Family 3
Trust
The governance, compliance, observability, and deployment-sovereignty surface regulated industry customers require — Trust, Observability, Sovereign — plus the Section 16.4 expansion products that operationalize trust as proof: Safeguard (continuous adversarial testing + AI safety) and Benchmark (verifiable performance evidence + interactive TCO).
trust
AIVAON AIVAON Trust
Live Compliance Control Plane, data-subject-rights workflow, attestation library, audit evidence packaging, consent management — compliance depth as a purchasable capability.
First value in ≤1 days · sales-assisted
observability
AIVAON AIVAON Observability
Tenant-facing dashboards, distributed trace exploration, anomaly-aware alerting, incident workflow, SIEM streaming — the operational visibility surface enterprise teams require.
First value in ≤10 min · self-serve
sovereign
AIVAON AIVAON Sovereign
Customer-managed signing root, sovereign deployment kit, air-gapped operation, federation across deployments — for customers whose requirements preclude any shared infrastructure.
First value in ≤30 days · sales-assisted
safeguard
AIVAON AIVAON Safeguard
Continuous AI safety and red-teaming — adversarial testing, prompt-injection detection, exfiltration monitoring, bias evaluation, compliance-specific safety validation — as integrated capability that extends the Trust substrate into active proof.
First value in ≤15 min · self-serve
benchmark
AIVAON AIVAON Benchmark
Public, reproducible, methodology-transparent benchmarking across latency / quality / connectivity / cost / compliance / sovereignty / scale, plus the interactive TCO calculator that converts benchmark publication into commercial engagement.
First value in ≤10 min · self-serve
Family 4
Experience
Developer experience, ecosystem extensibility, enterprise commercial wrapper — Studio, Marketplace, Enterprise — plus the Section 16.4 expansion products that broaden the experience surface: Workflow (visual business-process automation), Migrate (competitive-displacement product), and Certify (certified developer / partner / solution / consultant ecosystem).
studio
AIVAON AIVAON Studio
Visual agent authoring, workflow canvas, vertical template library, simulation environment, evaluation harness, typed SDKs in six languages — developer productivity that wrapper platforms cannot match.
First value in ≤10 min · self-serve
marketplace
AIVAON AIVAON Marketplace
Certified integrations across CRM/ITSM/eCommerce/collaboration, MCP-native first-class support, partner publishing workflow, attach analytics — the network-effect engine.
First value in ≤10 min · self-serve
enterprise
AIVAON AIVAON Enterprise
Named CSM, QBR cadence, financial SLA, custom model provisioning, advanced controls — the commercial wrapper that binds the other eleven products.
First value in ≤14 days · sales-assisted
migrate
AIVAON AIVAON Migrate
Competitive displacement as a structural product — automated configuration translation from Vapi / Retell / Bland / Twilio Flex / Google Contact Center AI / Genesys, parallel-operation traffic splitting, data migration tooling, and migration-success validation.
First value in ≤7 days · sales-assisted
workflow
AIVAON AIVAON Workflow
Visual business-process automation with full execution primitives — trigger / action / decision / parallel / join / timer / human-step / loop / subworkflow / error-handler nodes — spanning the entire AIVAON catalog plus Marketplace integrations and custom SDK nodes.
First value in ≤15 min · self-serve
certify
AIVAON AIVAON Certify
Certified developer / partner / solution / consultant ecosystem with examination infrastructure, recertification cadence, public directory, and credential maintenance — the network-effect-generating ecosystem that distinguishes category leaders from category participants.
First value in ≤14 days · sales-assisted
Five SKUs, sixty fully-populated entitlement cells
Every product is available in every SKU. The matrix scales capabilities and limits — never availability. Sovereign tenants get every product, every capability, and customer-controlled signing roots.
Tier 10
Starter
Solo operators and small teams entering production voice, messaging, and AI.
Self-serve · 1+ seat
Tier 30
Professional
Multi-agent campaigns, multi-channel orchestration, multi-seat operations.
Self-serve · 3+ seats
Tier 50
Business
Multi-market deployments with advanced analytics, attribution, and continuous certification.
Self-serve · 10+ seats
Tier 80
Enterprise
Custom infrastructure, named CSM, policy-as-code governance, BYOK, financial SLA.
Sales-assisted · 25+ seats
Tier 100
Sovereign
Customer-managed signing root, sovereign deployment, air-gapped operation, federation.
Sales-assisted · 50+ seats
Composition by configuration — the Cross-Product Workflow Engine
The aivaon.workflow.v1 wire protocol composes any subset of the catalog products into a single orchestrated execution. Identity, entitlement, audit, and tenant context propagate across product boundaries automatically. One trace, one audit trail, one billing record across every product hop.
- DAG-only structure. Cycles are rejected at parse time so workflows are deterministic and replayable.
- Mandatory context surfaces. Every edge MUST propagate identity-context, entitlement-context, audit-context, and tenant-context. Workflows cannot evade audit by dropping fields.
- Real executors only. The Production-Executor Coverage gate (currently 100%) blocks merges that leave any product action handled by a stub.
- Bounded substrate cost. Per-node timeout and retries are bounded at the parser layer so adversarial workflows cannot exhaust runner budget.
Catalog Evolution Program — five expansion criteria
New products are added only through a formal expansion process governed by a reviewer matrix (Product + Engineering + GTM + Finance + Compliance). Every proposal evaluates five Catalog Expansion Criteria before approval:
Commercial independence
Standalone purchase, activation, and value realization without a co-purchased product.
Addressable market
Demonstrated demand, segment size, and willingness-to-pay backed by named accounts or research.
Architectural fit
Clean Spine consumption with no architectural exception, no shared codebase forks, no parallel substrate.
Spine adherence path
Concrete plan to reach minimum Spine Adherence Score before GA, with named substrate-binding owners.
Retire risks evaluated
If approved, the catalog adds reversibility cost — every add is also a future possible retire.
How customers grow across the catalog
Expansion-optimized onboarding is one of the seven principles. Every product surfaces adjacent products at natural moments through organic capability surfacing — never through interruptive upsell prompts.
- 1
Pick the entry product
Choose any one of the catalog products as your initial entry point — there are no required bundles or prerequisites. Self-serve activation completes in ≤15 minutes for Studio, Realtime, Messaging, and Agents.
/services → - 2
Activate via the Section 16.2 Quickstart
The /console/onboarding/section16.2-quickstart wizard walks through entitlement configuration, first workflow, first execution, and readiness drilldown in five guided steps with localStorage persistence so you can return where you left off.
/console/onboarding/section16.2-quickstart → - 3
Compose with adjacent products by configuration
Use the Studio visual canvas at /console/studio to compose a cross-product workflow — drag nodes for any product action, wire propagated context, and execute. The aivaon.workflow.v1 wire protocol enforces DAG-only structure, mandatory context surfaces, and bounded retries.
/console/studio → - 4
Watch expansion triggers surface organically
As usage builds, the Expansion Trigger service surfaces adjacent products in the tenant dashboard with quantitative value estimates derived from observed usage. CSMs see the same triggers in /console/admin/expansion-triggers with bulk-acknowledge + bulk-convert tooling.
/console/admin/expansion-triggers → - 5
Track Composite Readiness Index
Every operational dimension that the §16.2 doctrine measures rolls into the Composite Commercial Readiness Index at /console/admin/section16.2-readiness — Spine Adherence, Production-Executor Coverage, Catalog Evolution velocity, Expansion Trigger Conversion. The dashboard auto-refreshes and links to the per-dimension drilldowns.
/console/admin/section16.2-readiness →
Frequently asked questions
- How many products are in the AIVAON Service Catalog?
- The §16.2 doctrine establishes exactly twelve named, purchasable, independently activatable AIVAON products: Realtime, Telephony, Messaging, Agents, Intelligence, Hybrid, Trust, Observability, Sovereign, Studio, Marketplace, and Enterprise. They are organized into four families: Substrate, Intelligence, Trust, and Experience. Section 16.4 extends the catalog to twenty-two products by scheduling ten expansion products in release waves 1–4, for a 110-cell SKU × product entitlement matrix.
- What is the AIVAON Platform Spine?
- The Platform Spine is the cross-cutting substrate that every product consumes and that no product reimplements. It comprises ten substrates: Control Plane, Identity Fabric, Event Bus, Observability Substrate, Audit Pipeline, Billing Engine, Compliance Infrastructure, API Gateway, Policy Decision Point, and Secret Management. Every product is measured by a Spine Adherence Score that quantifies its compliance with the architectural-singularity principle.
- Can I buy AIVAON products independently or do I need a bundle?
- Every product is independently purchasable with standalone pricing, contracts, activation, and deactivation. The §16.2 commercial-independence principle guarantees customers can enter through any one product and expand along any vector. Multi-product bundles exist commercially but they're an aggregation of the independent products, not a separate SKU.
- How do AIVAON products integrate with each other?
- Composition is a configuration operation, not an integration project. The Cross-Product Workflow Engine speaks the aivaon.workflow.v1 wire protocol and propagates identity-context, entitlement-context, audit-context, and tenant-context across product boundaries automatically. Workflows that span Telephony → Agents → Trust → Intelligence run as one orchestrated execution with one trace, one audit trail, one billing record.
- What are the five AIVAON SKUs?
- Starter, Professional, Business, Enterprise, and Sovereign. Every product is available in every SKU per the §16.2 doctrine; the SKU-product entitlement matrix scales capabilities and limits rather than gating availability. The matrix has 60 cells (12 products × 5 SKUs) and every cell is concrete — either available with explicit limits + capabilities, or unavailable with explicit reason.
- Where can I see live operational adherence to the §16.2 doctrine?
- The console at /console/admin/section16.2-readiness publishes the live Composite Commercial Readiness Index. It combines four signals: Platform Spine Adherence Score (architectural singularity), Production-Executor Coverage (real-vs-stub action handlers), Catalog Evolution velocity (governed changes per quarter), and Expansion Trigger Conversion (organic upsell realization). The aggregate gauge and per-dimension drilldowns are refreshed continuously.
- How does the catalog evolve over time?
- Through the Catalog Evolution Program. Adding a product requires an approved decision evaluating five Catalog Expansion Criteria: commercial independence, addressable market, architectural fit, Spine adherence path, and retire-risk evaluation. Decisions are recorded in an append-only ledger gated by a reviewer matrix (Product + Engineering + GTM + Finance + Compliance). The CI gate blocks PRs that introduce new product slugs without a backing approved decision.
- Is the catalog API-discoverable for AI agents?
- Yes. /.well-known/agent.json publishes 17 A2A skill cards covering every §16.2 PART XIII surface (Spine Adherence, Cross-Product Workflows, Expansion Triggers, Catalog Evolution, Readiness Index). 28 MCP tool descriptors are exposed through the AIVAON MCP server. /llms.txt enumerates the 12 products with deep-links. /section16.2/knowledge-graph.json publishes the entire catalog as a single Schema.org @graph fetch optimized for AI answer-engine ingestion.
For AI agents and search engines
The §16.2 catalog is fully discoverable through machine-readable surfaces: