Skip to content
ECZ‑IDfor MSPs & MSSPs

ECZ-ID · Machine Trust for MSPs & MSSPs

Know which AI can act for which customer.

Record customer authority, machine delegation, current state and evidence across your managed estate — and give every client an answer they can independently re-check.

Turn that accountability into a managed service without replacing your RMM, PSA, IAM or security stack.

Commercial outcomes

Make machine accountability a service your clients can use.

New managed service

Add Managed AI Accountability to an agreement you already hold.

Less evidence labour

Make reviews, supplier assurance and evidence requests repeatable.

Customer Authority

Separate what the customer authorised from what technology happens to permit.

Independent re-check

Give the client a current answer they can verify without your console.

Multi-client authority

One operator. Many clients. A separate authority record for each.

Machine identity tells you what a workload is. Customer Authority records whether it may act for this client. Operator Delegation must stay inside that client-specific scope, and each client's evidence remains isolated.

Topology diagram with one MSP connected to separate Client A, Client B and Client C authority records, each leading to its own machine identities, MCP and API surfaces, evidence and independent re-check.
MSP and client authority topologyMulti-client authority topology

Managed AI Accountability

A managed service line on an agreement you already hold.

Keep the client relationship, retail price and service wrapper. ECZ-ID provides the Machine Trust structure beneath the service: authority, delegation, lifecycle, Attention Required, client evidence and re-check.

MSP Partner Platform

  • Portfolio and participating-client operations
  • Machine actors, authority and current state
  • Attention Required across the managed estate
  • Client Evidence Packs and independent re-check
  • Workspace, REST API and CSV exports

Explore the managed service

Machine Trust Core

Per-client Register, Customer Authority, confirmation, Operator Delegation, lifecycle and current state, Attention Required, Evidence Pack and scoped independent re-check.

Machine Trust Assured

Core plus enhanced evidence review, stronger review cadence, enhanced client artefacts and priority operational support for higher-consequence estates.

Recurring service architecture

The Baseline starts the record. Core or Assured keeps it current.

Participating clients move into a repeatable operating cycle: confirm authority, maintain lifecycle and current state, respond to Attention Required, and issue recurring Evidence Packs and re-checks.

Architecture diagram showing the MSP Partner Platform supporting recurring Machine Trust Core and Machine Trust Assured services for participating clients.Per participating client
Recurring participating-client serviceRecurring service architecture

Product operating model

See the records and operating views behind the service.

These are product interface models using demonstration data. They show the intended operating structure, not an operating customer record or a live production screenshot.

Product interface model showing an MSP portfolio view with participating clients, machine actors, attention items and evidence status.
MSP portfolio workspaceProduct interface model · Demonstration data
Product interface model showing a client-specific Customer Authority record and bounded Operator Delegation.
Customer AuthorityProduct interface model · Demonstration data
Product interface model showing current lifecycle states, revocation history and Attention Required findings.
Lifecycle and Attention RequiredProduct interface model · Demonstration data
Product interface model showing a per-client Evidence Pack and independent re-check route.
Client EvidenceProduct interface model · Demonstration data

Integrations + API

Add a trust layer without moving the execution path.

Use the ECZ-ID workspace when you need it. Use the API, exports and Resolver when you don't. Native RMM, PSA, IAM, SIEM, EDR, MDR, MCP and API systems continue to execute and observe work while ECZ-ID records the client-specific authority, delegation, state and evidence around them.

Architecture diagram showing RMM, PSA, IAM, security, MCP and API systems connecting to ECZ-ID records, exports, Evidence Packs and the Resolver without routing execution through ECZ-ID.
Integration and API architectureIntegration and API architecture

Explore the platform model

The 2026 operating shift

Machine actors moved into the channel’s operating stack.

Dated facts from the organisations that made them. The interpretation is ours; none of these developments requires ECZ-ID.

  1. 28 April 2026

    Kaseya introduced an agentic IT management platform, powered by its Kaseya Intelligence engine, at Kaseya Connect Global.

    Primary source
  2. April 2026

    The Microsoft Entra Agent ID platform reached general availability. It provides the identity foundation for AI agents inside an organisation's own Microsoft Entra tenant: an agent identity is a service principal that, in Microsoft's words, “can only be issued tokens in the Microsoft Entra tenant where they're created” and “can't access resources or APIs in other tenants”.

    Primary source
  3. 16 July 2026

    ConnectWise announced the general availability of the ConnectWise Platform, which unifies ConnectWise PSA, ConnectWise RMM, ScreenConnect, ConnectWise SIEM, automation, orchestration and ConnectWise AI Agents into a single platform.

    Primary source
  4. 2 August 2026

    The transparency obligations in Article 50 of the EU AI Act (Regulation (EU) 2024/1689) have applied since 2 August 2026. They were not postponed by the Digital Omnibus on AI (Regulation (EU) 2026/1744, in force 27 July 2026), which deferred the high-risk requirements in Chapter III to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems.

    Primary source

Read the sourced Resources briefing

Client Evidence

Give every client an answer they can check themselves.

A per-client Register, confirmed Customer Authority, lifecycle and revocation history, an Evidence Pack and a scoped re-check route create an answer that does not depend on access to your console.

Starting record

£395 Client-Estate Machine Trust Baseline

Map representative machine and action paths, Customer Authority, operating surfaces and evidence, then identify which client estates should enter recurring Machine Trust. The Baseline creates the starting record. Machine Trust keeps it current.

Commercial activation journey showing the Free Trust Check, the £395 Client-Estate Baseline, partner activation, and recurring Machine Trust Core or Machine Trust Assured.
From free Check to recurring Machine TrustCommercial activation journey

Review the £395 Baseline

ECZ-ID MSP Partner Programme

Add Managed AI Accountability to your service portfolio.

Activate under private partner terms, retain control of retail and the service wrapper, and remain Partner of Record for your clients.

  • Private MSP partner wholesale terms
  • You control the retail price and service wrapper
  • Your MSP remains Partner of Record
  • Assisted activation for the starting client set
  • Client Evidence Packs plus API and export access
  • Core and Assured service levels
Start partner activation

Choose the next useful step

Start with the question, the service, or the starting record.