Skip to content

AI usage governance

Govern how your workforce uses AI, from evidence.

See which AI applications and MCP servers people use and what for, set their approval status, and enforce usage policies where Vekri has a control point. Activity is attributed to employees only from verified identity, and shown as pseudonyms when you choose.

Contact SalesRequest a Demo

The problem

Why it matters.

AI use spreads across chat apps, coding agents and MCP servers. Without evidence, governance becomes a policy document nobody can check, or surveillance nobody asked for.
  1. 01

    Collect

    One usage event per AI interaction, from endpoint inventory, agent hooks, the local MCP gateway and Vekri Gateway.

  2. 02

    Attribute

    An event names an employee only from verified evidence: an authorizing device binding, a gateway sign-in linked to your directory, or a local MCP decision. Anything else is counted, never assigned.

  3. 03

    Decide

    Approve, restrict or block applications, and write usage policies on applications, tools and detected data.

  4. 04

    Review

    The Usage Explorer breaks activity down by application, server, department and use case, with alerts for policy outcomes and blocked applications.

See it work

Step by step.

Workforce AI usage
Illustrative data

Endpoint inventory

Claude Code hooks

Local MCP gateway

Vekri Gateway

Attribution

Verified evidence only

Device binding: employee verified
No evidence: counted, not assigned

Vekri Observe · Usage Explorer

Last 30 days

  • Claude Code312
  • MCP: github148
  • MCP: linear64
  • Codex41

Engineering · 41 peopleSupport · 12 peopleLegal · below group size

Shown as pseudonymsEmployee 7f3aEmployee c21e

What happens

Capabilities

What Vekri does today.

Each item is in the current release and verified by tests in the product repository, with its limits beside it.

  • Vekri Observe

    AI usage telemetry and Usage Explorer

    One event per AI interaction across endpoint inventory, hooks, the local MCP gateway and Vekri Gateway, attributed to employees only from verified identity, with breakdowns by application, MCP server, department and use case.

    Vekri Endpoint · local MCP gateway · Vekri Gateway (remote MCP)

  • Vekri Control

    Employees, named or pseudonymous

    AI usage per verified employee, with no productivity score or ranking. Without permission, or if the organization chooses, people are shown as stable pseudonyms.

    Vekri Control

  • Vekri Control

    AI Applications inventory

    Every AI application and MCP server found across your organization, with approval status, an explainable risk score, owner, employees, first and last seen, and coverage taken from evidence.

    Vekri Control

    Limit: Approval status is enforced only where Vekri has a control point (the local MCP gateway); elsewhere it is recorded.

  • Vekri Protect

    AI usage policies on MCP calls

    Rules on applications, tools and detected data, compiled to Cedar and applied by the local MCP gateway: monitor, warn, require a justification or approval, deny, ask the agent to remove detected data and repeat the call, or suggest an approved alternative.

    local MCP gateway · macOS, Linux

    Limit: Applied only on MCP calls through the local MCP gateway; elsewhere a policy outcome is recorded, not enforced.

  • Vekri Observe

    AI usage alerts

    Sensitive data in an interaction, AI usage policy outcomes and use of blocked applications, from recorded evidence, with CSV export.

    Vekri Control

  • Vekri Control

    Privacy and retention settings

    Choose whether names are shown by role or never, the minimum group size for breakdowns, and how long usage is kept.

    Vekri Control

  • Vekri Observe

    Source and integration health

    Health of each telemetry source and integration, taken from the evidence it delivers; configuration alone is never shown as healthy.

    Vekri Control

In detail

Built for oversight, not surveillance.

Governance features are limited by design, and the limits are settings you control.

What Vekri shows

  • Which applications and MCP servers are used, and by how many people
  • Usage by department and use case, above a minimum group size you set
  • Policy outcomes and alerts, with the evidence behind each

What Vekri does not do

  • No productivity score and no ranking of people
  • No names for people without the permission to see them, or at all if you choose
  • No prompt or response content in usage records

Products

Where it comes from.

Related capabilities

Contact Sales

See Vekri with your own AI applications, agents and systems.

Talk to us about the AI your organization uses, the systems agents reach and how you deploy: in Vekri's cloud, or inside your own Kubernetes cluster.

Contact SalesRequest a Demo