Concurrent Spaces
Capacity for the number of trusted collaborations running at the same time.
Trusted collaboration for AI agentsEarly access
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.
The new way work moves
One workflow can involve your agent, a partner’s model, private data, external tools, and a human approver. The collaboration is still held together by copied context, shared credentials, and approvals that sit outside the execution path.
Trust
Every Standard Space provides isolated execution, scoped access, short-lived authority, policy-controlled release, and verifiable evidence—then destroys transient state when the work is complete.
The Standard Space
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 the code, data, logic, capabilities, or evidence the collaboration needs.
Each principal decides what assets enter the Space and under what conditions.
Participants receive only the context and derived information policy permits.
Capabilities become available only when their conditions are satisfied and expire automatically.
Only policy-approved outputs leave. Transient assets, credentials, and working state can be destroyed afterward.
See it in action
Any principal can contribute protected code, data, models, logic, capabilities, or evidence. Standard governs how those contributions can interact and what may leave.
This simulation shows several principals contributing protected assets and authority into one temporary Space. Their agents and services may continue running where they already live; only the trust-sensitive part of the workflow enters Standard.
What enters the Space
Your stack stays
Your agents stay where they are. Standard appears only when work crosses a trust boundary.
Keep the tools you already use. Standard is designed to step in only where participants need to work together under one agreement.
Keep planning, routing, memory, and ordinary agent-to-agent work in your existing framework.
Keep your identity provider and delegated credentials. Standard is designed to use them to verify participants and scope authority.
Keep threat detection and runtime guardrails. Standard is intended to define what collaboration is permitted in the first place.
Use the execution substrate your assurance level requires. Standard is designed to apply the same portable collaboration model above it.
One ephemeral agreement across everyone involved: separate access, conditional authority, an approved release, and a clean end.
Product preview
These early interface previews show how Spaces are intended to fit an existing workflow. The planned portal makes participation, live activity, decisions, approved evidence, what left the Space, and teardown reviewable.
standard space create --policy production-review
standard space run sp_01J8Q4K7 --task change.json
standard space inspect sp_01J8Q4K7
standard receipt verify rcpt_01J8Q4M2space = standard.Space(
policy="production-review",
)
result = await space.run(task)
result.receipt.verify()POST /v1/spaces
GET /v1/spaces/{id}
POST /v1/spaces/{id}/context-requests
POST /v1/spaces/{id}/actions
POST /v1/spaces/{id}/destroyspace.create
space.run
space.inspect
context.request
action.submit
receipt.verifyThe portal shows
Why it matters
Frameworks, identity, and guardrails stay in place. Standard is designed to govern the ephemeral agreement where private inputs meet, authority is earned, and only an approved result leaves.
Target contract
Early access is validating a contract that ties every important decision to the rules, the participants, and the exact version of the work.
Early access
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.
Identify the participants, private assets, trust assumptions, and exact result that needs to cross the boundary.
Walk through admission, scoped context, conditional authority, approval, release, and teardown against the real workflow.
Define what your security, platform, and business owners must be able to inspect and verify before a pilot.
Early access is scoped around one workflow, with deployment assumptions and success criteria agreed up front. Ready to start? Apply for early access.
Commercial direction
Three envelopes—Developer, Team, and Enterprise—scale with concurrent Spaces, compute inside each Space, and how long evidence is retained. Public list prices are not fixed yet; early access and design-partner terms are scoped around one workflow.
Capacity for the number of trusted collaborations running at the same time.
Compute capacity matched to the work running inside each Space.
Retention windows for receipts and the evidence approved to remain.
If agents, people, or services with different authority or access need to work together, bring us one workflow that crosses a trust boundary.