Cloud/Connectors/Deployments
Deployments
The edge deployment ledger for your own connector: every version shipped, its integrity digest, its entitlements, the four-eyes approval, the drift report and the audit chain.
Deployments is the tab for connectors you build and ship yourself, the ones created through Connector Deploy or the OpenAPI and Manual paths. The subtitle says the two jobs: "Manage edge deployments and monitor version drift." Marketplace connectors do not show this tab; deployments are your release history.
Deployments
Manage edge deployments and monitor version drift.
Edge Deployments
| Status | Version | Server ID | Deployed | Size | Tools | Drift |
|---|---|---|---|---|---|---|
| Active | v42 | srv_8f42…a1c7 | Sep 10, 2025 14:02 | 128 KB | 6 | |
| Inactive | v41 | srv_8f42…a1c7 | Sep 03, 2025 09:17 | 127 KB | 6 | |
| Inactive | v40 | srv_8f42…a1c7 | Aug 27, 2025 18:40 | 125 KB | 5 |
Deployment Details
Identity
- Server ID
- srv_8f42a1c7
- MCP Fusion version
- 2.4.1
- Integrity digest
- sha256:8f42a1…c7
- Generated at
- Sep 10, 2025 14:02
Entitlements
Capabilities granted to this deployment. Red indicates a high-risk permission.
Approval (Art. 14)
Drift Report (Art. 15)
Audit Chain (Art. 73)
The mockup is the real tab. Click a row to open Deployment Details, and on the pending deployment write a justification and press Approve to watch the four-eyes flow complete.
The deployment ledger
The table lists every version under the EDGE DEPLOYMENTS header: a status dot (emerald for the Active deployment, pulsing amber while approval is pending), the version, the server id, the deploy timestamp, the bundle size, the tool count, how many deploys this connector has shipped, and a drift dot. One row is always the live one; the rest is history you can inspect.
Deployment Details
Clicking a row opens the drawer, and the drawer is where Vinkius turns a deployment into evidence:
- Identity: the Server ID, the MCP Fusion version that built it, the hash and the Integrity digest;
- Entitlements: the capabilities this deployment was granted, Network, Crypto, Filesystem, Code Eval, Subprocess, with "Red indicates a high-risk permission";
- Approval (Art. 14): the four-eyes principle. When approval is required, a new deployment sits in Pending until a different team member writes a justification, "Justification (min 10 chars required for approval)", and presses Approve or Reject. Auto-approved deployments record it;
- Drift Report (Art. 15): what changed between what was approved and what is running, tools added or removed, destructive actions added, entitlements added, inflation risk, or "No drift detected.";
- Audit Chain (Art. 73): the tamper-evident chain verdict, "Audit chain valid" or "Audit chain compromised", with the deployment audit exportable as a PDF report.
The article numbers are not decoration: this is the evidence chain the EU AI Act expects from high-risk AI systems, attached to every deploy by default.
Why this tab exists
Shipping a connector to the edge is a production event: it can add tools, widen entitlements, change what agents can do. This tab makes every one of those events reviewable, attributable and provable, after the fact and before it: drift is detected, approval is a human decision, and the chain proves nobody rewrote the history.
What comes next
The record continues in Audit Logs, every request the deployments served, and Log Streaming, forwarding those logs to your own systems.