---
title: "Cordium: Open Source Identity-Based Sandbox Platform"
description: "Cordium is an open source, self-hosted sandbox platform for developers and AI agents, with identity-based, secretless access to infrastructure via Octelium."
canonical: "https://octelium.com/cordium"
---

# The open source, identity-based, secretless sandbox platform

Run isolated, reproducible sandboxes for developers, AI agents and automated workloads on your own infrastructure, with identity-based, policy-driven, secretless access to databases, SSH servers, APIs and Kubernetes clusters, without credentials ever reaching the sandbox.

[Get started](https://octelium.com/docs/cordium/latest/overview/quick-install.md)[Live Demo](https://demo.octelium.com)[What is Cordium?](https://octelium.com/docs/cordium/latest/overview/intro.md)[GitHub repo](https://github.com/octelium/cordium)

- Free and open source
- Designed for self-hosting
- Built on Octelium

Why Cordium

## Isolated execution is only half of the problem

Sandboxes for developers, AI agents and automated workloads need isolated, reproducible execution as well as access to real infrastructure. Existing platforms solve one side and leave the other to the user. Cordium unifies both in a single platform.

1. 01

   ### Credentials inside the sandbox

   API keys, database passwords, SSH private keys and kubeconfigs end up in environment variables, files and shell history, where a leaked log or a prompt injection can exfiltrate them.

   In Cordium

   Upstream credentials stay at the Octelium identity-aware proxy and are injected at the protocol layer once a request is authorized. The Workspace never holds them.

2. 02

   ### Isolation without identity

   Most sandbox platforms isolate processes but leave infrastructure access to whatever credential the sandbox holds, so the credential itself becomes the authorization boundary.

   In Cordium

   Every Workspace run gets a dedicated Octelium Session as its identity, and every request it makes is authorized against that identity with policy-as-code.

3. 03

   ### One tool per workload

   Remote development environments, AI agent sandboxes and CI runners are usually separate products, each with its own identities, its own credentials and its own audit trail.

   In Cordium

   The same Workspace serves long-lived coding sessions and short-lived automated runs, through the browser, SSH, the CLI and the SDKs.

4. 04

   ### Incomplete visibility

   Network and container logs rarely explain which agent ran which query against which database, or why it was allowed to.

   In Cordium

   OpenTelemetry-native, L7-aware access logs tie every request back to the Workspace Session, its owner and the Policy that decided it.

Unified sandbox platform

## One sandbox platform for developers, AI agents and automation

A Workspace is an isolated, rootless container sandbox on standard Kubernetes. The same Workspace serves as a remote development environment for engineers and as an execution sandbox for AI agents, CI/CD jobs and automated scripts.

- [Access Workspaces through the browser-based terminal, the cordium CLI, standard SSH for VS Code, Zed and JetBrains, or programmatically through the gRPC API and SDKs.](https://octelium.com/docs/cordium/latest/use/access-methods.md)
- [Persistent Workspaces preserve their filesystem across restarts, while ephemeral Workspaces start clean every time and can stop on their own once their tasks complete.](https://octelium.com/docs/cordium/latest/overview/concepts.md#workspaces)
- [Full root capability inside the sandbox to install packages, run services and run nested containers, with no VMs, bare-metal nodes or specialized hardware.](https://octelium.com/docs/cordium/latest/examples/dev/containers.md)

[Read about access methods](https://octelium.com/docs/cordium/latest/use/access-methods.md)

Secretless access

## Access infrastructure without credentials inside the sandbox

Every Workspace run gets a dedicated Octelium identity. Processes inside the Workspace reach authorized resources with standard tools, while the upstream credentials stay at the Octelium identity-aware proxy.

- [Covers HTTP API keys and access tokens, SSH passwords and private keys, PostgreSQL and MySQL passwords, kubeconfigs and mTLS client certificates.](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)
- [psql, ssh, curl and kubectl work unmodified, with no SDK, no credential injection and no secrets in environment variables.](https://octelium.com/docs/cordium/latest/examples/security/octelium.md)

[Read about accessing Octelium Services](https://octelium.com/docs/cordium/latest/examples/security/octelium.md)

Least-privilege access

## Identity-based access control on every request

Access from a Workspace is authorized on a per-request basis against the identity behind it, the context around it and the content of the request itself, with policy-as-code using CEL and OPA.

- [Application-layer access control on HTTP methods, paths and bodies, database names and users, Kubernetes verbs, resources and namespaces, and MCP and LLM operations.](https://octelium.com/docs/octelium/latest/management/guide/cel.md)
- [Humans authenticate through OIDC and SAML 2.0 identity providers, GitHub OAuth2 and passkeys, while agents and workloads use OAuth2 or federated OIDC assertions.](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)
- [Zero standing privileges. There is no admin or superuser User, and all access must be granted by a Policy that can be revoked on the next request.](https://octelium.com/docs/octelium/latest/overview/zero-trust.md)

[Read about Policies](https://octelium.com/docs/octelium/latest/management/core/policy.md)

Visibility

## Real-time, L7-aware visibility for every Workspace

Every request a Workspace makes to infrastructure is logged in real time with its full identity context and exported to your OpenTelemetry OTLP receivers.

- [Application-layer detail in every entry: HTTP methods and paths, database queries, Kubernetes operations, recorded SSH sessions, and MCP and LLM calls with token usage.](https://octelium.com/docs/octelium/latest/management/core/visibility.md)
- Every entry correlates back to the Workspace Session and its owner, which is what post-incident analysis of an agent run actually needs.
- OpenTelemetry-native visibility. Logs go to the log management and SIEM tools your organization already operates.

[Read about visibility and logs](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

Programmable

## A programmable sandbox platform for agents and automation

Everything the CLI and the web portal do is available over the gRPC API, with official SDKs for Go, TypeScript, Python and Rust. Create, start, drive and destroy sandboxes from a CI pipeline, a scheduler, an internal developer platform or an AI agent.

- [Run commands and stream their output, move files, attach to persistent terminals, follow initialization logs and watch Workspace state changes.](https://octelium.com/docs/cordium/latest/use/api.md)
- Manage Templates and pre-builds, snapshots, Volumes, Spaces, Secrets and Memberships through the same clients.
- [Authenticate workloads secretlessly with OIDC assertions from platforms such as GitHub Actions and Kubernetes, or with OAuth2 and access tokens.](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)

[Read about the APIs and SDKs](https://octelium.com/docs/cordium/latest/use/api.md)

Reproducible environments

## Declarative, reproducible environments

Workspace environments are defined in YAML specs covering the container image, repository cloning, lifecycle tasks, environment variables, resource limits, variable substitution and application ports.

- [Build Workspace filesystems from OCI images, Dockerfiles, git repositories and devcontainers, with multi-repository cloning including private repositories.](https://octelium.com/docs/cordium/latest/workspaces/templates.md)
- [Templates reuse one configuration across many Workspaces, and variables let a single Template serve many different tasks.](https://octelium.com/docs/cordium/latest/overview/concepts.md#templates)
- [Spaces group Workspaces, Templates, Secrets and Volumes, with resource limits resolved across the Workspace, Space and Cluster levels.](https://octelium.com/docs/cordium/latest/overview/concepts.md#spaces)

[Read about Workspace configuration](https://octelium.com/docs/cordium/latest/workspaces/templates.md)

Storage

## Kubernetes-native storage, snapshots and Volumes

Workspace storage is backed by Kubernetes persistent volumes on any CSI driver, including Longhorn, Ceph, OpenEBS, AWS EBS, GCP Persistent Disk and Azure Disk.

- [Snapshots capture a Workspace's storage while it keeps running, so it can be cloned into new Workspaces or restored after a risky change.](https://octelium.com/docs/cordium/latest/overview/concepts.md#workspacesnapshots)
- [Volumes outlive the Workspaces that mount them, mounted by one Workspace at a time or shared by several, read-only or read-write per mount.](https://octelium.com/docs/cordium/latest/overview/concepts.md#volumes)
- [Template prebuilds that reduce cold startup for heavy Workspaces from minutes to near instant.](https://octelium.com/docs/cordium/latest/workspaces/templates.md#pre-builds)
- [Storage classes and snapshot classes are selected through CEL rules, routing different Workspaces to different storage backends.](https://octelium.com/docs/cordium/latest/management/clusterconfig.md)

[Read about Volumes and snapshots](https://octelium.com/docs/cordium/latest/overview/concepts.md#volumes)

Isolation

## Rootless sandboxes with egress network policies

Each Workspace runs as a rootless container inside a restricted outer container, with dropped capabilities, a custom seccomp profile and enforced resource limits. Egress network policies decide where it can connect.

- Egress rules allow or deny destinations by CIDR and port. By default public networks are reachable and private ones are not, and DENY rules always take precedence.
- [Read-only root filesystems and per-Workspace Linux capabilities, merged with the Space and Cluster configuration.](https://octelium.com/docs/cordium/latest/workspaces/runtime.md#filesystem-and-capabilities)

[Read about Workspace configuration](https://octelium.com/docs/cordium/latest/workspaces/templates.md)

Use cases

## Use Cordium across development and automation

Start with remote development environments or AI agent sandboxes, then apply the same Workspaces, identities, Policies and audit trail to CI/CD, automation and secretless access to infrastructure.

### Development

04

- [Remote development environmentsPersistent Workspaces for VS Code, Zed and JetBrains over standard SSH, or a full terminal in the browser.](https://octelium.com/docs/cordium/latest/use/access-methods.md)
- [Reproducible project environmentsTemplates, devcontainers and pre-builds, so every engineer starts from the same initialized filesystem.](https://octelium.com/docs/cordium/latest/workspaces/templates.md)
- [Nested containersRun Podman inside a Workspace, including databases and services for integration tests.](https://octelium.com/docs/cordium/latest/examples/dev/containers.md)
- [Secretless infrastructure accessReach databases, SSH servers, Kubernetes clusters and internal APIs from a Workspace without distributing credentials.](https://octelium.com/docs/cordium/latest/examples/security/octelium.md)

### AI agents and automation

06

- [Claude Code sandboxesRun Claude Code in an isolated Workspace with policy-controlled, secretless access to the infrastructure it works on.](https://octelium.com/docs/cordium/latest/examples/ai/claude-code.md)
- [Codex sandboxesRun OpenAI Codex against real APIs, databases and clusters, with no raw credentials inside the Workspace.](https://octelium.com/docs/cordium/latest/examples/ai/codex.md)
- [OpenCode sandboxesLet OpenCode plan, modify repositories and run tests inside an isolated, auditable execution environment.](https://octelium.com/docs/cordium/latest/examples/ai/opencode.md)
- [CI/CD executionEphemeral, auto-stopping Workspaces that build, test and deploy with secretless access to clusters and registries.](https://octelium.com/docs/cordium/latest/examples/automation/cicd.md)
- [Sandboxes from codeCreate, drive and destroy Workspaces from Go, TypeScript, Python and Rust in any orchestration system.](https://octelium.com/docs/cordium/latest/use/api.md)
- [Identities for AI agentsAgents act under their own identities and Policies, rather than holding long-lived, over-privileged credentials.](https://octelium.com/docs/cordium/latest/overview/ai-agents.md)

On every Cordium Cluster

The same capabilities ship with every installation, from a single VM to a multi-node production cluster.

- [Web portal and browser terminal](https://octelium.com/docs/cordium/latest/use/web-portal.md)
- [SSH for VS Code, Zed & JetBrains](https://octelium.com/docs/cordium/latest/use/ssh.md)
- [Devcontainer support](https://octelium.com/docs/cordium/latest/workspaces/image.md#devcontainers)
- [Pre-built Templates](https://octelium.com/docs/cordium/latest/workspaces/templates.md#pre-builds)
- [Snapshots & Volumes](https://octelium.com/docs/cordium/latest/workspaces/snapshots.md)
- [GitHub & GitLab OAuth2](https://octelium.com/docs/cordium/latest/workspaces/secrets.md#gitproviders)
- [OIDC & SAML 2.0 SSO](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)
- [Policy-as-code with CEL & OPA](https://octelium.com/docs/octelium/latest/management/core/policy.md)
- [OpenTelemetry auditing](https://octelium.com/docs/octelium/latest/management/core/visibility.md)
- [Go, TypeScript, Python & Rust SDKs](https://octelium.com/docs/cordium/latest/use/api.md)

Questions

## Frequently asked

- Is Cordium free and open source?

  Yes. Cordium is free and open source under the Apache 2.0 license and is designed for self-hosting. There is no proprietary cloud-based control plane, no tiered feature set, and it is not a limited version of a separate paid SaaS product. Cordium is built on Octelium, whose Cluster components are licensed under AGPLv3.

- How is Cordium different from other sandbox platforms?

  Remote development environments such as GitHub Codespaces and Coder, and sandbox platforms such as E2B and Daytona, provide the execution environment and leave infrastructure access to whatever credentials are placed inside it. Cordium additionally gives every Workspace its own identity and provides secretless, policy-driven access to SSH servers, databases, HTTP APIs, Kubernetes clusters and mTLS services, so no upstream credential is ever exposed, distributed or managed inside the sandbox.

- How are Workspaces isolated?

  Each Workspace runs as a rootless container inside a restricted outer container, with all Linux capabilities dropped except a small explicit set, a custom seccomp profile, a restricted /proc and enforced CPU, memory and storage limits. It runs on standard Kubernetes with no VMs, bare-metal nodes or specialized hardware, and egress network policies decide which destinations it can reach.

- Can AI agents use Cordium programmatically?

  Yes. Everything the CLI and the web portal do is available over the gRPC API, with official SDKs for Go, TypeScript, Python and Rust. Agents and orchestrators authenticate as workload Users, including secretlessly through OIDC assertions issued by platforms such as GitHub Actions and Kubernetes, and every Workspace they run gets its own Session identity.

- Do I need an existing Octelium Cluster?

  Cordium runs on top of Octelium. The quick installer can automatically set up a complete Octelium Cluster and installs Cordium on top of it. If you already run an Octelium Cluster, Cordium can be installed on it as a package.

- Do I need Kubernetes experience to run Cordium?

  No. Cordium runs on Kubernetes, but the quick installer provisions a complete single-node Cluster, Kubernetes included, on any Linux machine or VM with at least 4GB of RAM and 20GB of disk storage. Production installations can run on managed or on-premises multi-node Kubernetes.

Get started

## Install Cordium on your own infrastructure in minutes

One fresh Linux VM/server and a domain you own. The installer takes care of Octelium, Cordium and all of their dependencies, Kubernetes included.

[Quick install guide](https://octelium.com/docs/cordium/latest/overview/quick-install.md)[GitHub repo](https://github.com/octelium/cordium)

```
$ curl -o install-cluster.sh https://octelium.com/install-cluster.sh$ chmod +x install-cluster.sh$ ./install-cluster.sh --domain <DOMAIN> --cordium
```
