What is Standard?
Standard is building infrastructure for agents, people, and services to work across trust and control boundaries—without sharing full context, handing over credentials, or giving up control.
Product FAQ · Early access
How agents, people, and services collaborate across trust and control boundaries—and how early access is scoped.
Standard is building infrastructure for agents, people, and services to work across trust and control boundaries—without sharing full context, handing over credentials, or giving up control.
A Standard Space is a temporary execution domain for the part of a workflow that cannot safely happen in either party’s environment. Agents and services can stay where they already run. Each principal contributes only what the collaboration needs; participants receive only policy-permitted context; capabilities are granted just in time and expire; only approved outputs leave; then the Space ends.
No. Keep the tools you already use. Agent frameworks keep planning, routing, memory, and ordinary agent-to-agent work. Identity providers and delegated credentials stay in place. Threat detection and runtime guardrails stay in place. Use the execution substrate your assurance level requires. Standard is designed to step in only where participants need to work together under one agreement.
Early access is for design partners with a real cross-organization or cross-control-boundary workflow. We will use that workflow to test the Space model, expose missing controls, and agree on the evidence required before broader use.
Bring one workflow that crosses a trust boundary. Identify the participants, private assets, trust assumptions, and exact result that needs to cross the boundary. We will walk through admission, scoped context, conditional authority, approval, release, and teardown against that workflow, then define what your security, platform, and business owners must be able to inspect and verify before a pilot.
Early interface previews on the homepage show how Spaces are intended to fit an existing workflow. They are not a generally available runtime.
Early access is validating a contract that ties every important decision to the rules, the participants, and the exact version of the work. The target contract requires access, capability, and release requests to be evaluated against the accepted Space policy. Ephemeral authority must be scoped to the Space, participant, purpose, and lifetime. The final receipt must bind the released result to the recorded policy, evidence, approvals, and artifact versions.
Standard does not promise that every participant is honest or every approved output is safe. A passing test does not prove universal correctness—it proves the named test passed. Standard does not promise that information can be recalled after an authorized recipient receives it.
Plans scale with Space capacity—not the number of agents, reviewers, or services. Developer is free for evaluation (one Space, limited hours). Team adds concurrent Spaces and included runtime. Enterprise adds committed capacity, isolation options, and longer evidence retention. Public dollar amounts are not locked yet; design-partner pilots are scoped around one workflow.
The planned portal makes participation, live activity, decisions, approved evidence, what left the Space, and teardown reviewable: who joined and what access each one received; what is happening in the Space right now; which requests were allowed, denied, transformed, or escalated; the claims, test results, approvals, and artifact versions behind what may leave the Space; and what left the Space, what was retained, destroyed, or is still pending deletion.
Use Apply for early access on the homepage or FAQ. You will land on a short contact form scoped to one workflow—participants, what must cross the boundary, and the evidence you need before a pilot.
If agents, people, or services with different authority or access need to work together, bring us one workflow that crosses a trust boundary.