HUMAN | AGENT
Same facts.
A different interface.
A compact, machine-readable view of DriftGate. Product scope, limitations and pricing status stay consistent with the human experience.
{
"name": "DriftGate",
"category": "Enterprise Agent Control Plane",
"revision": "2026-09-22.website-v1",
"publication": "public-platform-overview",
"summary": "A governance and learning control plane for agentic systems. Bring approved tools, identity, policy, execution and evidence into one system.",
"website": "https://driftgate.ai",
"capabilityCount": 59,
"availability": "This site presents DriftGate’s full platform direction. Release and integration qualification are not established by this website build.",
"solo": {
"currency": "USD",
"amount": 19,
"interval": "month",
"plan": "Solo",
"state": "selected-launch-target",
"purchasable": false
},
"pillars": [
{
"key": "T",
"title": "Tooling & Environment Control",
"url": "https://driftgate.ai/platform/tooling-environment-control/"
},
{
"key": "I",
"title": "Identity & Policy",
"url": "https://driftgate.ai/platform/identity-policy/"
},
{
"key": "E",
"title": "Execution Governance",
"url": "https://driftgate.ai/platform/execution-governance/"
},
{
"key": "O",
"title": "Observability & Assurance",
"url": "https://driftgate.ai/platform/observability-assurance/"
},
{
"key": "L",
"title": "Lifecycle Management",
"url": "https://driftgate.ai/platform/lifecycle-management/"
},
{
"key": "D",
"title": "Data & Context Governance",
"url": "https://driftgate.ai/platform/data-context-governance/"
}
],
"links": {
"capabilities": "https://driftgate.ai/agent/capabilities.json/",
"markdown": "https://driftgate.ai/agent/overview.md/",
"human": "https://driftgate.ai/platform/"
},
"boundaries": [
"Qualified integration and effect paths only.",
"Discovery is not authorization; observation is not enforcement.",
"Unknown outcomes require reconciliation before another effect.",
"Private knowledge is shared only through explicit scope and review."
]
}One source. No alternate claims.
These representations come from the same versioned content as the website. They do not expose the internal knowledge base, grant permissions or provide a live execution endpoint.
Stable IDs identify capability definitions, not proof of runtime availability. The machine-readable record preserves that distinction.