Seguro por construção.Agents reach your tools only through gates you control.
Uma pessoa concede acesso a um agente. O agente é executado como ele mesmo em seu próprio computador isolado. O Kortix decide quais chaves chegam a esse computador e verifica cada chamada de aplicativo, chamada de modelo e alteração que ele faz.
Choose which agent may run, and grant it access.
Atua como ele mesmo, nunca com seu papel.
Run a commandChecked by the runtime, before the tool runs.
Reached only after the check.
The runtime checks allow, ask or deny before every tool runs.
Um computador por sessão. Connector logins and Dosco’s model keys never enter it.
Quatro garantias. They hold whoever runs the agent.
Computador próprioEvery session runs isolated.
- One cloud computer per session
- Its own branch of the repository
- Nothing shared with another session
Its own identityAn agent never borrows your role.
- Grants are deny-by-default
- It cannot grant itself more
- You choose who may run it
Logins stay outConnector logins never enter the computer.
- Dosco makes each app call
- Secrets encrypted per project
- Enforced secrets swapped outside
Checked and recordedRules first, then the audit log.
- Allow, Ask or Block per action
- One approval per exact call
- Every action on record
Como funciona.One layer at a time.
Identidade e funções
People sign in with SAML single sign-on, or a password with two-factor.
Each person holds an account role and a role in each project. Groups grant a project to many people at once.
- Owner
- Admin
- Member
- Manager
- Member
- SAML 2.0 SSO
- SCIM 2.0
- Two-factor
- Session timeout
O que aplica cada regra. All but one run outside the computer.
| Rule | Enforced by | On deny |
|---|---|---|
| A valid credential | Dosco API | 401 |
| A role that allows the action | Dosco API, IAM | 403, or 404 if hidden |
| The agent’s own permissions | Dosco API, IAM | 403 |
| No self-granted permissions | Dosco API, IAM | 403 agent_grant_escalation |
| Tool, command and path rules | Runtime, inside the computer | Ask waits, deny refuses |
| Connector rules | Connector broker | 202 held, 403 denied |
| No connector calls to private addresses | Connector broker | connector_egress_blocked |
| Enforced secret, listed hosts only | Secret broker | Not swapped |
| Push only to its own branch | Dosco git | 403 |
Merge needs project.gitops.merge | Dosco API | 403 CR_SELF_MERGE_REFUSED |
- A valid credentialDosco API
401 - A role that allows the actionDosco API, IAM
403, or 404 if hidden - The agent’s own permissionsDosco API, IAM
403 - No self-granted permissionsDosco API, IAM
403 agent_grant_escalation - Tool, command and path rulesRuntime, inside the computerAsk waits, deny refuses
- Connector rulesConnector broker
202 held, 403 denied - No connector calls to private addressesConnector broker
connector_egress_blocked - Enforced secret, listed hosts onlySecret brokerNot swapped
- Push only to its own branchDosco git
403 - Merge needs
project.gitops.mergeDosco API403 CR_SELF_MERGE_REFUSED
Execute onde sua política determina.And read every line of what you run.
Kortix Cloud
We run the control plane and compute sandboxes.
Dedicated cloud
A single-tenant deployment in a cloud account we scope with you.
Auto-hospedado
An isolated enterprise deployment, scoped with us.
Governance & control
Audit every run, inspect every diff, verify every boundary.
SAML 2.0 and SCIM 2.0
Seu provedor de identidade decide quem entra.
Any model
Your own provider keys, or Dosco-managed.
- Bring us your review
SOC 2 Type I verified
GDPR operated. We hold no other certification and imply none.
Security questions.Answered from the code.
Anything else, write to the team.
How does an agent authenticate to Dosco?
Each session computer gets KORTIX_TOKEN. It acts as that session’s agent, limited to its project, and ends with the session. It holds the agent’s permissions, never the role of the person who started it.
Which API keys and tokens exist?
Every credential names its kind in its prefix: kortix_pat_ acts as you, kortix_sa_ as a service account, kortix_oat_ as a person who approved an app for 1 hour, kortix_gw_ reaches only the LLM gateway, and kortix_scim_ only directory sync. A missing or invalid token gets 401. A valid one without the permission gets 403.
Can an agent read our connector logins?
No. Dosco stores the login and makes each call itself. The login never enters the session’s computer.
Can code in a session read a secret?
A secret delivered as an environment variable is a real value, so code in the session can read it. Mark a web API key Enforced and the computer gets a stand-in instead. Dosco swaps in the real value outside the computer, only on requests to the hosts you list, and an echoed value comes back as [REDACTED].
Does Dosco filter outbound network traffic?
Not today. A computer can reach the internet directly, for example to install packages. What Dosco enforces: enforced secrets go only to listed hosts, connector calls never reach private addresses, and a copied session token gets no enforced secret outside its own computer.
Who can approve a held action?
A project manager, or the person who started the session. An approval covers one exact call. A held call expires after 24 hours unless the project sets another time, from 5 minutes to 30 days.
Can an agent merge its own changes?
Only with the project.gitops.merge permission. Without it, the merge answers 403. The built-in Orchestrator agent holds full project permissions, so remove the merge permission from it to require a person every time.
What does the audit log record, and can we export it?
Who did what, when, how they signed in, and whether it was allowed, refusals included. When an agent acts, the row names the person it acted for. The log shows the last 14 days; older events sit in a locked archive to day 365, and the export reads them. Reading, exporting and streaming the log is an Enterprise feature.
Do the models keep our data?
Dosco-managed models run only through inference providers with zero data retention. With your own provider key, your agreement with that provider applies.
Where does Dosco run agent sessions?
Sessions run in isolated cloud microVM sandboxes (E2B) that connect back securely to the Dosco API. Each session receives a fresh, disposable environment with zero cross-tenant access.

