COMMERCIAL PLATFORM / PRODUCT DIRECTION

Operate authority at enterprise scale.

The future Verimand platform brings managed infrastructure, enforcement and operational governance around VAGP. The reference implementation establishes the foundations; a generally available commercial offering is still planned.

Product direction · availability not announced

OPEN PROTOCOL / COMMERCIAL IMPLEMENTATION

VAGP defines the model.
Verimand operates it.

VAGP 0.3 is publicly released: specification, schemas, test vectors and conformance assets are available under Apache-2.0. Its use does not depend on purchasing the Verimand platform.

View public VAGP resources

What the platform would add

Managed deployment, hosted services, administration, integration and enterprise support. Commercial software must preserve the protocol’s authority semantics.

The protocol license is Apache-2.0. No hosted-service availability, pricing, service levels or certification programme is announced here.

PLATFORM ARCHITECTURE

01 / PLATFORM AREA

Verimand Cloud

PLANNED

Managed authority infrastructure and a hosted Authority Service. A future Authority API would expose the system interface; SDK and MCP integrations would support developers and agent runtimes.

02 / PLATFORM AREA

Authority Gateway

REFERENCE RUNTIME / PRODUCT PLANNED

Enforce current authority between autonomous agents and protected services. A future MCP Authority Gateway would apply this boundary to agent-discovered tools.

03 / PLATFORM AREA

Control Plane

IN DEVELOPMENT / OFFERING PLANNED

An enterprise operating surface for agent inventory, Agent DNA, mandates, Authority Graphs, revocations and evidence. Repository development is not general product availability.

04 / PLATFORM AREA

Enterprise operations

PLANNED

Evidence retention, audit and compliance workflows, private deployment, multi-cloud operation and enterprise support. Scope and operational guarantees remain to be defined.

DEPLOYMENT & GOVERNANCE

Your boundaries.
Explicit authority.

Private deployment and multi-cloud operation are enterprise product directions. The existing cloud PoVs establish bounded 0.2 evidence, not a distributed production service.

VAGP stays vendor-, infrastructure- and jurisdiction-neutral. Enterprise implementations must preserve a deployment path without a critical dependency on a specific non-EEA-controlled provider.

Evidence for governance

The 0.3 reference profile signs intent and linked outcomes. Future retention, audit workflows and conformance services can build around that evidence. Signed records alone are not a compliance certification.

Inspect the enforcement architecture

DESIGN A BOUNDED PILOT

Start with one action
that needs a mandate.

Discuss the workflow, trusted state, protected resource and evidence requirements for an authority pilot.

DISCUSS AN AUTHORITY PILOT