Enterprise AI Control Plane

The control plane for enterprise AI, on your own infrastructure

MERIDVAR is software you install and operate. It discovers the AI in use across your organisation, records how each system and vendor was assessed and approved, refuses the requests your policy rejects before a model is called, and keeps the evidence. Nothing is sent to us.

  • Self-hosted appliance
  • Single tenant
  • No telemetry
  • Runs without internet access
MERIDVAR consoleIllustrative

Gateway admissions

Requests routed through this appliance.

CallerRouteDecision
Support reply assistantOpenAI-compatible APIAdmitted
Contract summariserOpenAI-compatible APIAdmitted
Console playgroundCarries a national identifierRefused
01 identitypass
02 shadow-aipass
03 prompt-dlprefused: national identifier
04 to 17skipped
Provider calls
0
Stored sample
Masked

Why it matters

AI use has outrun AI governance

Employees use consumer AI. Developers wire in model APIs. Business units buy AI inside SaaS products. Agents act through MCP servers. Each decision was local, but the exposure is not.

AI in use
There is no single inventory of the systems, agents and vendors in use.
Risk
There is no shared view of the data involved, the autonomy granted or the decisions made about people.
Data flows
A prompt is an authorised request to an authorised service, with the data in the body.
Spend
Consumption is spread across teams, keys and providers.
Accountability
Nobody can show who approved what, on what basis and until when.
13%of organisations reported a breach of AI models or applications.
97%of those organisations lacked proper AI access controls.
USD 670,000was added to the average cost of a breach where shadow AI use was high.

Source: IBM, Cost of a Data Breach Report 2025.

AI adoption is decentralised

AI arrives through employees, SaaS features, developer keys and vendor contracts, all at the same time. No single team sees all of it.

AI systems are becoming autonomous

Agents call tools, and MCP servers expose enterprise systems to models. A tool that can delete, pay or send data outside the organisation is a new kind of privileged access.

Accountability now has a schedule

EU AI Act transparency obligations have applied since 2 August 2026. Boards, auditors and regulators are asking the same question: how is AI governed here?

What it does

Five questions, answered in one record

Governance programmes start from declared inventories that are disconnected from the traffic. Security products start from the traffic and are disconnected from the decision. MERIDVAR keeps both in one place, on your network.

Stage 01

What AI is in use?

An AI inventory of systems observed in traffic or declared by people. Shadow AI discovery against your list of sanctioned providers. An agent registry, an MCP server inventory and endpoint agents.

Used by: Security and IT

AI security

MERIDVAR consoleIllustrative

AI inventory

Systems that this appliance observed in traffic or that a person declared.

AI systemProvenanceStatus
Support reply assistantObserved in gateway trafficCandidate
Contract summariserDeclared by an operatorDeclared
Unsanctioned chat serviceFound in an uploaded proxy logCandidate
Legacy translation botDeclared by an operatorRetired

An observation never becomes a declaration on its own. A person confirms it.

The product views on this site are illustrative, with invented example data. They show behaviour documented for the current release and are not screenshots of a customer environment.

How it works

The control plane runs where you run it

One appliance sits between your callers and your model providers. It runs five connected stages and keeps one record for every team.

MERIDVAR reference architectureCallers on the customer network reach AI providers through the MERIDVAR appliance, which runs five connected stages: discover, assess, approve, control and prove. Security, privacy, risk, finance and audit teams read one shared record. Nothing leaves the customer network for MERIDVAR.Your networkOutside your networkPeopleA token for each personAI applicationsOpenAI-compatible APIAI agentsSigned identitiesMCP serversDeclared inventoryUnmanaged trafficPAC file and proxy captureMERIDVAR applianceOne organisation, one appliance, and no control plane in our cloud01DiscoverInventory and shadow AI02AssessQuestionnaires and risk rules03ApproveReviews and approvals04ControlAdmission gateway05ProveEvidence log and audit packageModel providersAnthropic, OpenAI, Azure OpenAI, xAISelf-hosted modelsYour own endpointSaaS AI servicesSeen through uploaded logsAdmitted requests onlyNo telemetry to MERIDVARRuns without internet accessOne shared recordSecurityPrivacyRisk and complianceFinanceAuditEvery team that answers for AI reads the same appliance: visibility, policy, control, evidence and spend.
Controls apply to traffic routed through the gateway. Visibility of other traffic depends on uploaded logs, endpoint agents and declarations.

What makes it different

The decision, the gate and the evidence, in one place that you operate

MERIDVAR is focused where a GRC suite or a security platform is broad. What sets it apart is its architecture.

No vendor cloud

There is no MERIDVAR control plane in our cloud and no telemetry. Prompt content is inspected, and evidence is kept, on your own infrastructure. No new data processor enters the path.

Governance tied to a gate that can refuse

The record of what was approved and the gateway that admits or refuses requests live in the same appliance and write to the same evidence log.

Decisions that visibly go stale

An approval keeps the basis on which it was granted. When an answer, a vendor decision or a classification changes, the approval reads “review required”, with the reasons.

Customer-controlled by design

Self-hosted, single-tenant and able to run offline, with signed licences and signed updates verified on the appliance.

Deployment model

How MERIDVAR relates to the categories you already know

CategoryWhat it does wellWhere MERIDVAR sits
AI governance platformsProgramme workflow, policy content and model riskGovernance tied to observed traffic and to a gate that can refuse, operated by the customer
AI security platformsBroad AI threat coverage, from models to agentsFocused on admission control, with no vendor in the data path and the governance record included
SSE, CASB and SASEInline access control at network scaleComplementary: AI-specific governance, evaluated on your network
DSPM and data securityFinding and protecting data at restComplementary: governs decisions about AI systems and the prompt itself, before the call
LLM gateways and AI FinOps toolsRouting, caching and developer adoptionSpend by team and by model, recorded beside the security and governance decision
GRC platformsEnterprise-wide risk and control librariesThe AI-specific record that a GRC programme can draw on

Where a buyer is comfortable with cloud processing, an incumbent platform is often the right choice. MERIDVAR is built for the buyer who will not add a vendor’s cloud to the AI data path.

Who it is for

One control plane for every team that answers for AI

CISO

Security

Know what AI exists and what it is doing, and control the risk.

  • Shadow AI discovered against your list of sanctioned providers
  • Prompt DLP, threat detection and data residency enforced before the call
  • Agents and MCP servers registered, reviewed and risk-rated
AI security

CIO and CTO

IT

Enable enterprise AI without losing control.

  • An OpenAI-compatible endpoint that your teams and SDKs already use
  • Approved model lists, with four providers supported for live dispatch
  • A defined route to approval: assess, review and approve, with conditions
Product

CFO and FinOps

Finance

Make AI financially accountable.

  • A ledger of governed requests, with tokens, model and actual cost
  • Spend by team and by model over time
  • Team budgets with hard or soft caps, enforced at admission
AI FinOps

DPO, compliance and legal

Privacy and compliance

Turn AI governance into auditable evidence.

  • Every decision recorded with who made it, when and on what basis
  • Approvals that read “review required” when the facts change
  • An audit package for each AI system and each vendor
AI governance

What the product looks like

Evidence and spend, read from the same appliance

MERIDVAR helps organisations operationalise governance controls and generate evidence relevant to the frameworks they answer to. Whether an organisation is compliant remains its own determination.

Control evidenceIllustrative

ISO/IEC 42001, Clause 8: operational controls Partial

Three of four observations are satisfied.

ObservationMeasuredResult
Prompt DLP blocking categories6Satisfied
Threat detection enforcing on live trafficYesSatisfied
Teams with an enforced residency policy0 of 4Not satisfied
Vendor risk requirements enforced at the callYesSatisfied

A control that the product cannot observe is reported as uncomputed, with the reason.

Control status computed from the running system

Control mappings ship for the EU AI Act, NIST AI RMF and ISO/IEC 42001. Records relevant to the GDPR, DORA, NIS2 and LGPD are kept as evidence, with no framework mapping.

Compliance

Spend ledgerIllustrative

Governed requests

Illustrative figures. Model names are placeholders.

TeamModel servedTokensCost
Customer OperationsModel A4,210€0.031
LegalModel B12,880€0.194
EngineeringModel A2,045€0.015
FinanceRefused at admission0€0.000

A refused request makes no provider call, so it incurs no provider cost.

Cost recorded beside the decision

A ledger of governed requests, with tokens, model and actual cost, by team and by model. Team budgets are enforced at admission.

AI FinOps

Deployment
A single-tenant appliance on your infrastructure. One appliance serves one organisation.
Data handling
No raw identifier is stored. Findings keep masked samples. Provider keys are never returned to the browser.
Access control
Administrator, operator and viewer roles, checked on the server. The approver is never the requester.
Auditability
An append-only, hash-chained log. A record edited on disk reads as an evidence mismatch.

Evidence

Measured, not promised

The product is held to the standard of evidence it applies to AI decisions. These results come from MERIDVAR’s own tests, not from an independent assessment.

Zero calls on refusal

23 gateway tests were run against a provider that logs every request it receives. Every refusal made zero calls, and every admission made exactly one.

No identifier in the clear

Prompt DLP findings keep masked samples. The raw identifier is not stored.

Offline updates

A signed incremental update was applied to a real appliance with no internet access. Licences were verified on the appliance.

Governance at scale

The status of 5,000 AI systems was computed in about 70 milliseconds.

For investors

Building the control layer for the AI economy

Every enterprise that adopts AI needs to know what it runs, decide what is allowed, enforce that decision and prove it. That is a new control layer, with several budget owners and a record that grows more valuable over time.

Investor overview

See MERIDVAR refuse a request on your own network

A working session with the founder, on a host you control.

What happens next

  1. You send the formYour request goes straight to the founder.
  2. We reply by emailWe agree a time and what you want to see.
  3. We run a working sessionWe install the appliance with you, route a test request through it and read the evidence it leaves.