Nine products. One trust plane.

Which one do I need?

• Start with the platform. Every deployment begins with Control Vector — discovery, identity, policy, trust, audit.
• Add the Endpoint Container when agents must work where the endpoint is — desktops, branch sites, disconnected or regulated environments.
• Add the Web App Workspace to give operators a governed place to converse with and supervise agents.
• Pick an App Pack when you want a complete outcome (access review, SOC triage) running in days, governed on day one.
• Build Governed Workflows when your team orchestrates multi-agent work itself — and wants each workflow one step from becoming an AutoLet™.
• Start with AutoX™ when the process lives in people's heads, documents, or legacy automations — describe it, point at it, or import it, and AutoCreate the agent and its workflow on a Canonical Execution Graph.
• Use the Gateway or SDK when agents already exist — LangChain, CrewAI, AutoGen, or plain code — and need governance without a rebuild.
• Use the Governed API Gateway when your apps, scripts, and partners should drive the platform programmatically — every call scoped, limited, metered, and sealed.
• Install Governed Agents when your security team needs capacity now — pre-built SOC, IR, threat-hunting, vulnerability, cloud, identity, and compliance agents that install in minutes and earn autonomy through Build · Decide · Act.

Frequently asked