Introduction

Overview

Kode gives each developer a complete development environment. It is a workspace with its own compute, its own tools, and access to the real services of your application. Developers create and control these environments from code.

To do these tasks with an AI agent, see Agentic workflows.

The platform is designed around three principles.

Short development loop

Software is built in iterations: change the code, run it, examine the result. The time of one iteration sets the pace of all the work, for developers.

In a Kode workspace, the change runs where it is made.

An intercept sends the traffic of a service in a shared environment to a workspace. The change is tested with real services and real requests before it is merged.

Isolation by default

Code runs in an isolated environment, never on your computer.

A workspace is the sandbox that you work in. A capsule is a short-lived container for one command. Each workspace and each capsule has a dedicated kernel, file system, and network stack, with allocated vCPU, RAM, and disk. A failed or harmful run stays inside the environment that ran it. Many workspaces run in parallel, and the work of one does not affect the work of another.

Everything from code

Workspaces, environments, desks, capsules, snapshots, and pipelines are all created, connected and removed from code. A team can repeat a set-up exactly. The web console shows the state of your resources.

Where to start

• Quick start: from sign-in to a running change.
• Concepts: the parts of the platform and how they connect.
• Workspaces: the environment in which the work runs.