Sourced / Access pilot
Sourced Access.
Start with the boundary.
A pilot exploring how teams manage secrets, agent access and offboarding. Help define what should be granted, who owns it and how it should end.
Pilot discussions only. Not a production or audited product.
- 01 / Grant
What is needed?
Which secret or resource does the agent need for this task?
- 02 / Use
Where is the limit?
Who owns the access, and what actions should be allowed?
- 03 / Offboard
How does it end?
What must be revoked or rotated when a task or role ends?
Pilot status
A conversation.
Not a production promise.
Access is a separate pilot from the security review service. There is no production product to sign up for on this page.
Request pilot details- What we want to understand
- Your current secrets workflow, how agents receive access, and what happens when a person, agent or project is offboarded.
- What is not claimed
- Production readiness, an independent audit, general availability, specific integrations or a finished set of controls.
- A key limitation
- Ending an agent session does not revoke a copied API key. The provider must revoke or rotate that key, and the result must be verified.
- Before participation
- Agree separately on pilot scope, data handling, access, responsibilities and terms. Do not connect production systems or send secrets with an inquiry.
A useful starting point
Bring the workflow.
Leave out the secrets.
- How your team gives agents access today.
- Where access ownership is unclear.
- What is hard to revoke or verify during offboarding.
Start a pilot conversation
Tell us where access gets difficult.
Describe your workflow. Do not send credentials or production secrets.