Platform architecture

Vavan is the AI operating system for physical B2B. It is a multi-organization platform: Vavan LLC operates the platform, and each customer runs inside an isolated organization. Rather than replacing the tools a business already depends on, Vavan connects them, normalizes them into one shared model, and runs applications and AI agents on top of that model.

The architecture has three layers — Connect, Normalize, and Act. Each section below describes one layer in detail. If you only read one downstream page, read the ontology overview: it is the model that sits at the center of everything here.

The problem: fragmented tools

A typical physical-B2B operator runs the business across a dozen disconnected systems — a CRM for the sales pipeline, an ERP for inventory and fulfillment, accounting software for invoices, email for communication, and a separate routing or dispatch tool for deliveries. Each system holds a partial, differently-shaped view of the same customers, products, and orders.

Because no two systems agree on what an "account" or an "order" is, work cannot flow between them automatically. Teams reconcile the gaps by hand: re-keying data, exporting spreadsheets, and chasing context across tabs. AI cannot help much either, because there is no single, reliable model of the business for it to read or write. Vavan's job is to remove that fragmentation — first by ingesting these systems, then by collapsing them into one representation.

Connect: ingest the systems you already run

The Connect layer pulls in the systems a business already operates. Vavan integrates with CRMs such as Salesforce and HubSpot, with ERPs, with accounting systems such as QuickBooks, with email, and with prospecting sources. See Integrations for the current set of connectors and how to configure them.

Credentials for these integrations are stored per-organization and encrypted — never in shared application configuration. Each organization's API keys, tokens, and secrets are scoped to that organization alone, so one customer's connection to its CRM or ERP is never reachable from another organization or from the platform's general runtime configuration. See Security & isolation for how this isolation is enforced.

Normalize: one shared semantic model

The Normalize layer maps everything that Connect ingests into a single shared semantic model — the ontology. The ontology is a typed representation of the real things a business operates on: accounts, contacts, products, orders, sites, drivers, routes, signals, and tasks, along with the links between them.

Each kind of object is an object type with defined properties, and objects are connected through typed link types — for example, a contact belongs to an account, an order consumes products, a route visits sites. When data arrives from a CRM, an ERP, and an accounting system, it does not land as three disconnected records; it resolves into the same typed objects and relationships. That is what makes the model AI-readable: an agent can reason over a coherent picture of the business instead of stitching together raw rows from incompatible sources.

Act: apps and agents read and write the same objects

The Act layer is where work happens. Applications and AI agents read and write the very same Vavan Core objects that Normalize produced — there is no separate operational database that drifts away from the model. See Applications for the apps that ride on Core.

Within Act, events become work through a consistent chain:

• Signals. Rule-based logic and AI detect conditions that need attention — churn risk, a reorder coming due, a hot lead, a stalled deal, an overdue follow-up — and surface them as signals.
• Tasks / next best actions. A signal produces a recommended action, assigned to a person, so the right work lands with the right owner instead of sitting unnoticed in a report.
• Actions. When work is carried out, it runs as an action: a write that mutates Vavan Core with built-in rules and side effects, keeping the model consistent and auditable.

Vavan Core at the center

The reason the three layers compose into an operating system rather than a pile of integrations is that they all converge on Vavan Core. Connect feeds it, Normalize defines its shape, and Act reads and writes it. Every application speaks the same model, so there is no point-to-point integration between apps — adding a new app means teaching it Core, not wiring it to every other app.

A concrete example: a churn-risk signal raised in the CRM references the same account object that Dispatch operates on. That signal can become a task in Dispatch and a stop on a driver's route, because all three are working against one shared account — not three separate copies that have to be reconciled.

Signals, tasks, and actions: a closed operational loop

Together, the Act primitives form a closed loop. The platform observes Vavan Core and raises signals; signals generate tasks with a clear owner; tasks are resolved by actions; and actions mutate Core — which in turn changes the conditions the platform observes next. Detection, prioritization, execution, and the resulting state change are all expressed against the same model, so the operational loop stays consistent end to end without manual reconciliation between systems.

Multi-organization architecture and data isolation

Vavan is multi-organization by design. Every customer's data is scoped to its own organization, and access is enforced with row-level security so that one organization can never read or write another organization's objects. Integration credentials live per-organization and encrypted, as described in Connect above. For the full picture of isolation, encryption, and access control, see Security & isolation.

Where to go next

• Vavan Core overview — the shared model the whole platform is built around, including object types, properties, link types, and action types.
• Core concepts — the vocabulary (organizations, entities, signals, tasks, actions, credits) used throughout the docs.
• Applications — the apps that read and write Vavan Core, including the CRM and Dispatch.
• Integrations — connect Salesforce, HubSpot, your ERP, accounting, and email, with per-organization credentials.