Dosco TekDosco Tek
Preise
AnmeldenLoslegen

The CompanyOS

  • Multiplayer AI
  • Unternehmen als Code
  • Sovereign and open
  • Outcomes, 24/7

Building blocks

  • Agents
  • Skills
  • Apps
  • Drive
  • Konnektoren
  • Automatisierungen
  • Computers
  • Models

Use it from

  • Desktop
  • Mobile
  • Slack
  • Microsoft Teams

Run it

  • Sicherheit
  • Enterprise
  • Compliance

Learn

  • Guide
  • Case studies

Get Dosco

  • Download
  • Marketplace

Unternehmen

  • Karriere
  • Kontakt
  • Rechtliches
Dosco TekThe harness that powers companies that run agents.Explore Documentation

Sicher von Grund auf.Agents reach your tools only through gates you control.

Eine Person gewährt einem Agenten Zugriff. Der Agent läuft mit eigener Identität auf seinem eigenen isolierten Computer. Kortix entscheidet, welche Schlüssel diesen Computer erreichen, und prüft jeden App-Aufruf, jeden Modellaufruf und jede Änderung, die er vornimmt.

Sprich mit unsSicherheitsdokumentation lesen
Eine Person
Du

Choose which agent may run, and grant it access.

Sein eigener Computer
Der Agent

Handelt als er selbst, nie in Ihrer Rolle.

Run a command
Kortix-Gate
Tool rules

Checked by the runtime, before the tool runs.

Ressource
Files and commands

Reached only after the check.

The runtime checks allow, ask or deny before every tool runs.

Ein Computer pro Sitzung. Connector logins and Dosco’s model keys never enter it.

Vier Garantien. They hold whoever runs the agent.

  • Sein eigener ComputerEvery 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

So funktioniert es.One layer at a time.

Identität und Rollen

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.

Workspace-Rolle
  1. Owner
  2. Admin
  3. Member
Zugriffsrolle
  1. Manager
  2. Member
Anmeldung
  • SAML 2.0 SSO
  • SCIM 2.0
  • Two-factor
  • Session timeout

Was jede Regel durchsetzt. All but one run outside the computer.

Was jede Regel durchsetzt.
RuleEnforced byOn deny
A valid credentialDosco API401
A role that allows the actionDosco API, IAM403, or 404 if hidden
The agent’s own permissionsDosco API, IAM403
No self-granted permissionsDosco API, IAM403 agent_grant_escalation
Tool, command and path rulesRuntime, inside the computerAsk waits, deny refuses
Connector rulesConnector broker202 held, 403 denied
No connector calls to private addressesConnector brokerconnector_egress_blocked
Enforced secret, listed hosts onlySecret brokerNot swapped
Push only to its own branchDosco git403
Merge needs project.gitops.mergeDosco API403 CR_SELF_MERGE_REFUSED
  • A valid credentialDosco API401
  • A role that allows the actionDosco API, IAM403, or 404 if hidden
  • The agent’s own permissionsDosco API, IAM403
  • No self-granted permissionsDosco API, IAM403 agent_grant_escalation
  • Tool, command and path rulesRuntime, inside the computerAsk waits, deny refuses
  • Connector rulesConnector broker202 held, 403 denied
  • No connector calls to private addressesConnector brokerconnector_egress_blocked
  • Enforced secret, listed hosts onlySecret brokerNot swapped
  • Push only to its own branchDosco git403
  • Merge needs project.gitops.mergeDosco API403 CR_SELF_MERGE_REFUSED

Läuft dort, wo Ihre Richtlinie es verlangt.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.

  • Self-hosted

    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

    Ihr Identitätsanbieter entscheidet, wer Zugriff erhält.

  • Any model

    Your own provider keys, or Dosco-managed.

  • SOC 2Type IVerified

    SOC 2 Type I verified

    GDPR operated. We hold no other certification and imply none.

    Bring us your review

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.

Empower your company with agents that deliver finished work.Start today with real cloud compute and persistent drives.

Loslegen

SSO, RBAC & audit · Any model, your keys · No seat tax

Dosco TekDosco Tek
©2026 Kortix

Produkt

  • Sicherheit
  • Enterprise
  • Compliance
  • Preise
  • Herunterladen
  • Mobile

Resources

  • Guide
  • Dokumentation
  • Marketplace

Unternehmen

  • Karriere
  • Marke

Verbinden

  • Contact
  • Support
  • Bedingungen
  • Datenschutz
  • Subprocessors