FAQ
Questions or feedback?
- Help: Contact — product questions or issues
- Guided implementation: Founding Customer Pilot — $3,500 fixed-scope commercial pilot
- Updates: Subscribe — release notes (not a sales call)
How do I contact you?
Use the paths above: Contact for feedback or help, Founding Customer Pilot for guided implementation ($3,500 fixed-scope commercial pilot), and Subscribe for updates. Setup help is also in the setup prompts.
What is Decision Execution Governance?
It is the product-model control layer for organizations that need automated systems and AI agents to operate inside defined business boundaries. For supported integrations and configured execution surfaces, it evaluates covered actions before execution and returns an allow, constrain, deny, or escalation result, with a decision record for review. Implemented coverage is narrower than the model—see the compatibility matrix.
What is Agent Execution Governance?
It is Decision Execution Governance applied to AI agents. On supported adapters, it evaluates covered AI-agent actions before execution instead of relying only on the user permissions behind the agent. Not every host path or interactive mode is gated today (for example, some Codex host paths have limited coverage).
What is dexgate?
dexgate is the product family for Agent Execution Governance on coding and devops agents: free local hard-gate adapters plus a paid early-access / pilot Agent Action Passport Runtime (Dexgate policy runtime) for production-bound shell, patch, and deploy-class actions.
What is an action passport?
An Action Passport is a scoped, single-use authorization record for one supported agent action, issued only after policy decides, and re-checked before protected execution so production side effects stay allow-with-proof. When cryptographic signing is enabled, the record can be independently verified. The Passport path (decide, issue, verify, act-with-proof, and record) is the paid pilot path—not free mode with audit logging added after execution. Free local hard gates do not mint Passports. See free vs paid and the flow on the Product page.
What is the difference between the free adapter path and paid dexgate?
The free adapter path is local hardening only: adapter-specific hard gates with conservative read-only defaults (for example OpenClaw allows only read_file, list_files, and search_files unless you expand the list; Codex allows a conservative read-only shell allowlist and blocks apply_patch, interpreters, chaining, redirection, and mutations by default). Exact free surfaces are on the compatibility matrix. Free mode has no governed Passport or org-wide decision history. Paid pilot dexgate adds Dexgate policy decisions, Action Passport policy evaluation, workspace plan access, central decision history and evidence records, and plan-based limits.
What is the first use case?
Governed production change for coding and devops agents: shell commands, code patches, file mutation, and deploy-class actions.
Which runtimes are supported now?
Available free on npm: OpenClaw (recommended free path) and Codex (controlled host coverage). Roadmap: Grok Build, Claude Code, Cursor, and GitHub Copilot. See the compatibility matrix for coverage and paid pilot status. dexgate does not sell or license the underlying host applications.
Is this generally available production software?
No. Free adapters and paid runtime are early access / pilot offerings, not a general production SLA. Current integration status is only on the compatibility matrix (AVAILABLE, PILOT, ROADMAP).
How should an enterprise roll this out?
Pilot first: free evaluation on one runtime (recommended OpenClaw), then a one-team paid pilot with one Linux Docker host for the Dexgate policy runtime, then expand. See the Enterprise rollout guidance for phases, change management, and what not to do on day one.
Do you offer a support chat agent?
Not on the public site. Use the setup prompts with your own agent (OpenClaw, Codex, Grok, Claude, Cursor, Copilot) for install, paid wire-up, dashboard observe-then-configure, and Day-2 verify. For guided implementation, use the Founding Customer Pilot.
Does this replace permissions, sandboxing, or monitoring?
No. It works alongside them and fills the decision gap between a capable automated system and a risky action. Identity and host permission modes (ask / auto / always-approve, including fleet-wide remote or managed config on some hosts) control access and how often the human is prompted—they do not mint Passports or produce shared governed evidence. Free dexgate hard gates and the paid Action Passport path still apply on top. See Action Passports and comparison.
How does dexgate relate to agent host permission modes?
Host permission mode (ask, auto/classifier, always-approve—sometimes set fleet-wide via remote or managed config) is harness UX. dexgate is action governance: free local hard gates, and on paid pilot a shared Dexgate policy runtime that decides, issues Passports on allow-with-proof, verifies before protected execution, and records evidence. Always-approve on the host does not disable the free wall or paid fail-closed path. Details: enterprise rollout and the compatibility matrix (roadmap hosts such as Grok Build are labeled as such until their adapters ship).
Can I review evidence before contacting anyone?
Yes. Start with the sample decision record, review kit, compatibility matrix, and release notes. Paid-path evidence should show the proposal, policy decision, passport fields, verification result, and outcome record when available.
How does pricing work?
The local hard-gate adapter path is free. dexgate uses a shared pricing ladder across adapters, shown monthly first on the pricing page.