How it works — every flow in the open.
Every capability across the three planes — Visibility, Control, Protection — shown as the flows it actually runs. Each diagram is illustrative of the enforcement path; every path is fail-open by design.
# deploy the hub on your own cloud terraform apply ✓ ST Hub live · your-vpc # enroll a machine (read-only) stl enroll --hub hub.internal ✓ stl spoke connected # push an org-wide guardrail stl policy push --rule "deny: curl | bash" ✓ enforced on 126 machines
Detection & enforcement — ST Shield.
One detection engine runs at three enforcement points. Sensitive data is caught before it leaves — and every value is masked in the record.
Whatever the outcome, ST Shield writes a masked audit record — the matched secret is never stored in the clear — and can export it to your SIEM or a webhook.
The approval loop — fail-open by design.
Approve an agent's next command from your dashboard or your phone. If the decision can't reach you in time — or our software is down — the agent keeps working. We are in the path, never in the way.
ST Gate — one governed door for MCP.
Every MCP client — CLIs, desktop apps, Cursor, Windsurf, VS Code — routes through one gateway. Only approved servers are reachable; every tool call is audited; credentials are brokered, never handed to the client. Read the full ST Gate page →
- Claude Code
- Cursor
- Windsurf
- VS Code
- Desktop apps
Integrations — with a purpose, not a logo wall.
Every integration exists to answer a specific question or close a specific gap. We integrate with your stack; we don't ask you to replace it.
| Integration | What connects | Purpose |
|---|---|---|
| MCP clients (via ST Gate) | Claude Code, desktop apps, Cursor, Windsurf, VS Code | Route every MCP tool call through one governed door — approved-server registry, tool-call audit, credential brokering. |
| Vendor compliance APIs | OpenAI Compliance Logs Platform, Anthropic Compliance API, Google Vault for Gemini | Retrieve prompt/response content for org-managed enterprise desktop accounts — the only sanctioned way to see desktop-app conversations. |
| SIEM & webhooks | Any SIEM or HTTP endpoint | Stream ST Shield findings and audit events into the tooling your SOC already watches. |
| CASB & enterprise browser | Netskope, Zscaler, Microsoft Purview | Enrich endpoint and web signal for desktop-app coverage — filling the gap where CASB can't see terminal agents. |
| Identity provider | SSO (SAML / OIDC), SCIM | Tie RBAC and the identity graph to your directory, and discover shadow-AI logins via OAuth. |
| Deployment & IaC | Docker Compose, Helm, Terraform, offline bundle | Install ST Hub the way your platform team already ships infrastructure — including fully air-gapped. |
What leaves each machine — you choose.
Reporting is a ladder, set per policy. It starts at anonymous metrics and only climbs to full content where you deliberately enable it. The active tier is always visible to the employee on their own dashboard.
The full feature matrix.
Everything below is included in the single plan — nothing is gated.
| Plane | Capability | What it does |
|---|---|---|
| See it | Unified spend | Token spend and API-equivalent cost by hour, day, model, project, cost center. |
| See it | Live sessions | Live context fill and activity per session, every coding agent. |
| See it | Search & recovery | Full-text search and transcript recovery across every session. |
| See it | Budgets & chargeback | Department rollups, alerts at 80/100%, showback and chargeback exports. |
| See it | Cross-agent compare | Claude vs Codex vs Gemini vs Kimi, side by side. |
| Govern it | Remote approvals | Approve or deny a tool call from dashboard or phone — fail-open. |
| Govern it | Central policy | Org-wide guardrails pushed to every machine, enforced by local fail-open hooks. |
| Govern it | ST Gate | MCP gateway with approved-server registry, tool-call audit, credential brokering. |
| Protect it | ST Shield engine | Cards (Luhn), national IDs, keys, private keys, entropy heuristics, custom patterns. |
| Protect it | Three enforcement points | Prompt pre-send, command pre-execution, and hub ingest. |
| Protect it | Block / redact / flag | Per-pattern policy actions with a disposition workflow. |
| Protect it | Masked audit & SIEM | Sensitive values masked everywhere; export to SIEM or webhook. |
| Platform | Identity graph | CLI, desktop, MCP, endpoint, and IdP signal stitched to one employee. |
| Platform | Deployment | On-prem or your own cloud — Docker, Helm, Terraform, or air-gapped bundle. |
| Platform | Access & SSO | RBAC with SSO / SCIM for org, department, and per-user views. |
Installation — running in an afternoon.
Deploy the hub on infrastructure you own, enroll machines with a lightweight agent, set policy, connect your integrations. No SaaS account, no data leaving your walls.
Deploy ST Hub
Stand up the hub on your own servers or cloud — Docker Compose, Helm, or Terraform. Air-gapped? Load the offline bundle.
Enroll machines
Install the stl spoke on each machine. It reads AI session logs read-only and reports to your hub.
Set policy
Choose a reporting tier, push org-wide guardrails, and configure ST Shield detection and ST Gate's approved-server registry.
Connect integrations
Wire up SSO/SCIM, your SIEM, CASB, and the vendor compliance APIs for desktop-app content.
Illustrative — exact commands ship with your licensed bundle.