New: Loopmaxxing.Add a software factory to your repo with 1 prompt.→
Prezzi
GitHubAccediInizia

The CompanyOS

  • Multiplayer AI
  • Azienda come codice
  • Sovereign and open
  • Outcomes, 24/7

Building blocks

  • Agents
  • Skills
  • Apps
  • Drive
  • Connettori
  • Automazioni
  • Computers
  • Models

Use it from

  • Desktop
  • Mobile
  • Slack
  • Microsoft Teams

Run it

  • Sicurezza
  • Self-hosted
  • Enterprise
  • Compliance

Learn

  • Guide
  • Casi d'uso
  • Case studies
  • Blog
  • Changelog

Get Kortix

  • Download

Azienda

  • Informazioni
  • Lavora con noi
  • Contatti
  • Note legali
GitHubKortix is open sourcekortix-ai/CompanyOSView on GitHub

Sicuro per costruzione.Agents reach your tools only through gates you control.

Una persona concede a un agente l'accesso. L'agente opera come se stesso sul proprio computer isolato. Kortix decide quali chiavi raggiungono quel computer e verifica ogni chiamata alle app, ogni chiamata ai modelli e ogni modifica effettuata.

Parla con noiLeggi la documentazione sulla sicurezza
Una persona
Tu

Choose which agent may run, and grant it access.

Il proprio computer
L'agente

Agisce come se stesso, mai con il tuo ruolo.

Run a command
Kortix gate
Tool rules

Checked by the runtime, before the tool runs.

Risorsa
Files and commands

Reached only after the check.

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

Un computer per sessione. Connector logins and Kortix’s model keys never enter it.

Quattro garanzie. They hold whoever runs the agent.

  • Il proprio 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.

    • Kortix 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

Come funziona.One layer at a time.

Identità e ruoli

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.

Ruolo workspace
  1. Owner
  2. Admin
  3. Member
Ruolo di accesso
  1. Manager
  2. Member
Accesso
  • SAML 2.0 SSO
  • SCIM 2.0
  • Two-factor
  • Session timeout

Cosa applica ogni regola. All but one run outside the computer.

Cosa applica ogni regola.
RuleEnforced byOn deny
A valid credentialKortix API401
A role that allows the actionKortix API, IAM403, or 404 if hidden
The agent’s own permissionsKortix API, IAM403
No self-granted permissionsKortix 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 branchKortix git403
Merge needs project.gitops.mergeKortix API403 CR_SELF_MERGE_REFUSED
  • A valid credentialKortix API401
  • A role that allows the actionKortix API, IAM403, or 404 if hidden
  • The agent’s own permissionsKortix API, IAM403
  • No self-granted permissionsKortix 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 branchKortix git403
  • Merge needs project.gitops.mergeKortix API403 CR_SELF_MERGE_REFUSED

Eseguiilo dove la tua policy lo prevede.And read every line of what you run.

  • Kortix Cloud

    We run the control plane and the computers.

  • Self-hosted

    The app, API and database on your server.

  • Your VPC or on-prem

    A single-tenant deployment, scoped with us.

  • Open source

    Read it, fork it, audit it.

  • SAML 2.0 and SCIM 2.0

    Il tuo provider di identità decide chi può accedere.

  • Any model

    Your own provider keys, or Kortix-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 Kortix?

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. Kortix 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. Kortix 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 Kortix filter outbound network traffic?

Not today. A computer can reach the internet directly, for example to install packages. What Kortix 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 kortix agent holds every Kortix permission, 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?

Kortix-managed models run only through inference providers with zero data retention. With your own provider key, your agreement with that provider applies.

Where does a self-hosted Kortix run sessions?

The web app, API and database run on your server. Sessions still run on Platinum cloud computers, which call back to your server, so it must be reachable from the internet.

Own your company’s AI.Start today, in our cloud or yours.

Start for free

Open source · SOC 2 Type I · SAML SSO and SCIM · Any model, your keys

©2026 Kortix

Prodotto

  • Sicurezza
  • Self-hosted
  • Enterprise
  • Compliance
  • Prezzi
  • Scarica
  • Mobile

Sviluppatori

  • Guide
  • CLI

Azienda

  • Informazioni
  • Lavora con noi
  • Blog
  • Registro delle modifiche
  • Casi d'uso
  • Brand

Connetti

  • X
  • LinkedIn
  • Discord
  • Stato
  • Contact
  • Termini
  • Privacy