VNCaxf

VNCaxf is the Application Exchange Framework: the backend layer that lets the suite’s applications exchange data and services with each other and with the enterprise systems around them, at the scale of a large organization.

Products should not each invent their own integration. VNCaxf provides the shared middleware — metadata, content references, cross-application synchronisation and the gateway path — so a new integration is a configured connection rather than a new codebase inside every product.

What it delivers

One middleware instead of many point integrations. Each product speaks to the framework; the framework speaks to the other products and to enterprise systems.
Metadata integration. The framework carries the shared description of an object — its type, classification and references — so products agree on what they are exchanging.
Content and cross-application data synchronisation. Content referenced by several applications stays consistent, instead of being copied and drifting.
A gateway path for AI and external services. Requests to AI models and other backend services are routed through one controlled layer.
Scale. The framework runs as its own service layer, so integration capacity grows with the organization instead of with each application.

Main capabilities

Capability	What it gives you
Shared middleware services	Metadata, content management and cross-application data synchronisation as common services.
Application exchange	A defined contract for how products exchange data and events.
Gateway layer	One controlled path for authenticated requests to backend and AI services.
Identity-aware routing	Requests reach the framework with the caller’s identity and are handled under the suite’s access rules.
Extensibility	New enterprise systems are connected through the framework, not by changing every product.

Typical use

A new enterprise system — an ERP, an HR system or a billing service — is connected once, and the products that need its data use the framework.
A product introduces a new object type; its metadata is published through the framework so other products can reference it.
AI requests from several products are routed through the same gateway, so policy, budget and audit apply uniformly.
During an integration project, content referenced by two applications is kept in step rather than copied.

How it fits the suite

VNCuxf provides the user-facing framework; VNCaxf provides the backend exchange. Together they keep the suite coherent without a shared monolith.
VNClagoon AI uses the gateway path for its model requests.
VNCdirectory provides identity and access for every exchange.
VNCfiles holds the content the framework references.

Roles

Role	What they do
Integration engineer	Connect enterprise systems through the framework.
Administrator	Configure the gateway, identity and allowed connections.
Security	Review the routing, access and audit of exchanges.