Skip to main content
Ontelis home
See a demo
Ontelis home

One map of every connected system and process

The Context Graph is a knowledge graph of all the business systems a customer connects, and everything inside them, used as a map for agents to navigate.

Context GraphGraph as of Oct 20, 10:14:07 ET
Southeast region10 territories · 2 districtsTavrentaSyndicated weekly prescriptionsDr. Lena MarchettiIQVIA OneKey · Sun Oct 18“L. Marchetti” · Veeva CRMHeld · DCR-55102
Movement · aggregate only21.3% 18.2%, −3.1 pts291 fewer new-to-brand prescriptions over 8 weeks
Context package16Sources9
  1. Asked in a thread

    “Why did Tavrenta lose 3 share points in the Southeast, and how much of it is access versus field?”

    Marcus Ellery, VP of Sales, East

    Commercial analytics agent · 10:14:06 ET

  2. Scope
    10 territories2 districts214 priority doctors61 accounts

    Veeva CRM alignment · Mon Oct 19

  3. Definitionsruled, not measured

    R-108 v2 new-to-brand share · R-110 v2 decline

    Ruled by Naveen Prakash, Jan 12, 2026; v1 kept with its dates.

  4. Movementaggregate only

    21.3% 18.2%, −3.1 pts · market 9,860 9,940

    131 of 196 qualifying priority doctors wrote fewer

    Syndicated weekly prescriptions · week ending Fri Oct 9

  5. Permissions

    Mask policy US-COM v14 · business review: performance diagnosis

    Withheld186 doctor-level rows · LT-RX-03

    0 patient-level values; 7 small counts hidden as <11

  6. Held and cut
    Waiting on data steward

    DCR-55102: “L. Marchetti” is not matched to Dr. Lena Marchetti until Grace Tanaka confirms. Effect: under 0.1 pts on the split.

    Cut: 2 older team notes, available under the same permissions.

  7. Signed 10:14:16 ET

    CP-88213 · 7c1e 94a0 … 5d2b a94f

    16 items · 3,104 of 8,000 tokens · data plane HLV-US-1

Trusted by 2 out of the 5 largest life sciences companies

A knowledge graph of every connected system

  • Schemas, code, permissions and lineage are parsed by rule-based parsers.

Queried, not copied

  • Slow-changing things such as HCPs, territories, contracts and content are stored as nodes.

Two dates on every fact

  • Every fact keeps two dates: when it became true, and when Ontelis found out.

One package per step

  • A context package is the small, permission-filtered, signed bundle an agent receives before a step: facts, rules, suggestions, notes and check results. Every item carries its source, as-of time, edge label and treatment.

What a change will break

  • When a source ships a release, Ontelis diffs its new metadata against the graph and lists the agents, rules, checks and connectors that break.

“The diagram used to be the thing we argued about. Now it shows us where every value came from, and it flags what our own templates got wrong.”

Senior Solution Architect, Campaign OperationsOne of the top 10 global pharma companies

Who decides

Agents do

  • Read a signed context package before each step.
  • Get the impact list before proposing a change.
  • Read context and ask to act through the Agent Gateway.

People decide

  • Named owners rule on ambiguous edges and conflicting definitions; data stewards confirm middling matches. Each ruling records who made it and when.
  • Process owners confirm each process model before agents run on it.
  • System owners sign off the first graph.
  • An approver other than the builder approves each deploy.

What the Context Graph does not do

  • Act as an MDM.Veeva Network or OneKey stays the master.
  • Act as a warehouse.
  • Act as a BI tool.
  • Act as a vector index.Embeddings may help find entry nodes, but they never create edges.
  • Correct a source.

Where it fits

The Context Graph builds step 2 of every run, with IntuitionDB and Mask.

  1. 01TriggerAgents
  2. 02 · This pageContext packageContext Graph, with IntuitionDB and Mask
  3. 03Agent draftAgents
  4. 04Govern checksGovern
  5. 05Decision cardWorkspace
  6. 06Write through ConnectConnect
  7. 07LedgerGovern
  8. 08Outcome to IntuitionDBIntuitionDB

Watch Ontelis at work

Short walkthroughs of agents doing commercial work, from the first draft to the person who signs off.

Trace a share loss to access or field

Analytics & Insights · Commercial analytics agent · 4:06

0:00 / 4:06

Customer stories

One of the top five US biopharma companies

Brand teams get HCP answers in under 30 seconds

Read the story
One of the top 10 global pharma companies

Email campaigns cut from 131 effort-days to 46

Read the story

Questions about the Context Graph

The Ontelis Context Graph is a map of your business systems and what's inside them, built for agents. It records what exists and how it connects: the fields on an SAP purchase order, a Snowflake dbt model, a Vault approval workflow, and how your doctors, territories and contracts relate across them. Agents use the map to find the context a task needs, then read the actual values from the source system at that moment. Each agent gets only what it's permitted to see.

Security and data

Data in Context Graph
Row values such as claim lines stay in their source systems and are read live through named query templates.
Vendor documents
Ontelis provides: a SOC 2 Type II report, an ISO 27001 certificate, a HIPAA business associate agreement wherever Ontelis processes PHI, a data processing agreement with transfer clauses, and a sub-processor list.
Models
Ontelis builds no foundation model. No model is trained on customer data, except an opt-in adapter that never leaves the customer’s data plane.
Your controls
Ontelis’s posture as a vendor is kept separate from Govern, which holds your own controls.

One map of every connected system and process

See a demo