Pathiqa

The infrastructure layer between AI agents and enterprise data.

Pathiqa sits between an enterprise's knowledge (their data) and the AI systems that increasingly carry out its work. From this position it helps enterprises improve their agentic workflows with better access to enterprise knowledge and govern how agents interact with their data.

In early deployment with a select group of design partners.

What it is

The systems an enterprise runs were built for people and conventional applications, not for software that reasons and acts on its own. Data is siloed, semantically inconsistent across systems, and held together by informal knowledge. Today, agents reach this data through bespoke wiring built for each workflow, with no shared layer for access, accountability, or cost.

Pathiqa allows an enterprise to use whichever AI system(s) they want and governs data from any provider, system, type, or location (without having to change their whole stack).

The architecture

One architecture. Five layers of value. Three components.

The ontology

Resolves the enterprise’s data by meaning and persists independently of the systems it describes.

Connects · Insulates // layers 01 · 05

The ledger

Records every declared intent, access, action, and outcome as a signed, immutable entry.

Governs · Learns // layers 02 · 03

The key

The unit to which scope, access rights, and reputation attach — internally and across boundaries.

Exposes · Carries reputation // layers 04 · all

Five layers of value

Pathiqa's approach creates five layers of value for an enterprise.

// 01

Connect

// Ontology

Agents work with the context they need.

An agent that cannot resolve a customer across CRM, billing, support and product fails the moment it is deployed. Pathiqa’s ontology resolves meaning across the existing estate without consolidation. Requests from agents are given exactly the context they need, no more and no less, so agents produce better answers and outcomes. Our intelligent routing and permission-aware caching cut retrieval cost and load. The agent receives a coherent semantic surface that adapts as schemas evolve.

For CIO · Head of AI · Business sponsor · CFO Aligns to EU AI Act Art. 14 · NIST AI RMF Map

// 02

Govern

// Ledger

Every action is declared, recorded, and reversible.

Before an agent can access data, Pathiqa requires it to declare its intent, scope, and boundaries. This declaration becomes an enforceable contract. Every action is written to a structured, immutable ledger: intent, data accessed, model used, outcome produced. When something goes wrong, versioned rollback reverses a single agent’s impact without affecting other agents, users, or operations.

For CISO · General Counsel · CRO · Compliance Aligns to EU AI Act Art. 12 · ISO 42001 · DORA

// 03

Learn

// Ledger

The ledger compounds into a record of how the enterprise actually works.

Every agent decision is captured with intent, scope, model, latency, cost, and outcome. Over time this accumulates into operational awareness an enterprise has not had before: where work happens and what it costs, which agents and models deliver, what to automate further or retire. It is also the foundation for cost governance. Once the enterprise knows what a task should cost, budgets attach to keys, scopes, and outcomes.

For CDO · COO · CEO · CFO Aligns to EU AI Act bias monitoring · algorithmic accountability

// 04

Expose

// Key

Enterprise data, exposed to the outside on commercial terms.

Pathiqa’s ‘key’ architecture gives an enterprise a new, and safe, way to share their data with their customers or the public. The key is the unit to which reputation, scope, and access rights attach. Customer-, partner-, and public-facing keys each receive carefully scoped access, with every action recorded and every contract violation triggering automatic revocation. Banks let counterparty agents query positions; insurers let broker agents quote against policy data. Pathiqa moves from cost centre to revenue platform.

For CCO · Partnerships · BD · Product Aligns to GDPR Art. 6 & 7 · Open Banking

// 05

Insulate

// Ontology

The enterprise stays in control of its data and its history, independent of any vendor.

Pathiqa is deliberately on the enterprise’s side. Adopting it gives an enterprise the freedom to change its software and AI vendors whenever it wants, avoiding expensive lock-in and staying in full control of its data. The enterprise, rather than its software providers, owns its ontology and ledger. Schemas can change, vendors can be swapped, models can be replaced.

For Board · Audit Committee · CRO · CIO Aligns to DORA Art. 28–30 · EU AI Act audit continuity

Posture

Pathiqa is vendor-neutral on both sides. Above it, agents may be foundation models, bespoke reasoning systems, or human-in-the-loop copilots. Beneath it, systems of record may be core line-of-business systems, document stores, or warehouses. The runtime speaks to both, so neither has to speak to the other directly.

The runtime is a layer for metadata and decisions. Raw data remains inside the systems that hold it. This is a structural property, not a configuration.

Deployment

Hosted: A managed instance operated by DSI. The fastest route into a working pilot.
Dedicated: A single-tenant instance in a dedicated environment. For organisations with stricter isolation requirements.
On-premise: Installed inside the organisation’s own environment. For sovereign and high-sensitivity workloads.

Access

Pathiqa is in early deployment with a select group of design partners. New engagements begin with a short briefing.

Request access