Platform Architecture

AVO is not a single application — it is a set of purpose-built engines connected by clear interfaces.

The core engines

Karsa is the measurement engine. It runs AS scans, pAS scans, ASg quick-peeks, VS measurement runs, manages Focuses and Prompt Books, fires and records Probes, and runs Probe Intelligence. Karsa owns the DKL (Domain Knowledge Layer) — the per-domain data cache. All measurement state lives in Karsa.

Ava is the intelligence engine. It reads Karsa’s output and produces Cards, Account Insights, Content Briefs, and Content Engine management. Ava owns the IKL (Intelligence Knowledge Layer) — the cross-network aggregate intelligence. Ava never writes to Karsa’s tables.

Netra is the Pixel tracking engine. It receives events from client-installed Pixel snippets, attributes AI-referred traffic, and surfaces the data to Ava for Pixel cards.

The partner deployment model

Avonetiq operates Karsa, Ava, and Netra centrally — one instance shared across all partners. Individual partners do not run their own measurement infrastructure.

Each partner gets their own Sutra (a data proxy layer that handles access control, billing, and multi-tenancy between Astra and the engines) and their own Astra (the client-facing portal, deployed with the partner’s branding). Clients never call Karsa or Ava directly — all requests flow through Sutra.

Current partners: cacaFly (Taiwan, Traditional Chinese market) and NAVICUS (Japan, Japanese market).

Internal tooling

Artha is the Avonetiq ops console — account management, partner configuration, system monitoring.

Shastra is the engineer console — Datapoint inspection, calibration tooling, and access to AS Simulate for testing formula changes before publishing via TimeMachine.

Samhita is the data acquisition system — it seeds IKL coverage by identifying industry domains and running synthetic probes in categories where client coverage is developing.