Glossary
The canonical vocabulary used across the ERun docs. Where two words could mean the same thing, only one is canonical here — pick that one when writing for or about ERun.
Tenants and environments
ERun is built around two ideas:
Environment types
Every ERun environment is one of three types, determined by where its project worktree lives. Operator and Agent collaborate in agent envs (local-agent or remote-agent); runtime envs serve deployed services.
Inside an environment
When you open an environment, ERun creates (or reuses) a dedicated Kubernetes namespace for it. Everything that belongs to the env lives in that namespace — both ERun's own developer-access surface and the application services your project deploys.
Networking
How traffic gets into an environment, and how services inside an env talk to each other.
Observability
What can you see when something goes wrong (or right). ERun doesn't ship a built-in observability stack — Kubernetes is the substrate, and you reach for the cluster's normal tools.
Security model
ERun's security story is one sentence: identity, isolation, audit — for every action, every Operator, every Agent. This page is the consolidated view; the details live in other pages and are linked from each section.
Conventions and folder layout
Why conventions
Skills
For the Operator workflow — install commands, the v1 catalogue, when to use each one — see Skills. This page is the conceptual model: why skills instead of scaffolding.
Cloud contexts
A cloud context is a cloud VM running k3s that ERun provisions for you, starts on demand, and stops when it goes idle. Same workflow as local, just hosted somewhere else — your environments live there, your IDE and Agent connect to them exactly as if the cluster were on your laptop.
Hosted platform
A hosted erun platform is a deployed erun-backend-api plus its database, serving one or more tenants their own environments over a REST API — the same API the hosted console drives, and the same one erun platform talks to directly. This page specs the provisioning model: what a hosted environment's lifecycle looks like, where it is allowed to land today, and what RBAC the control plane provisions it with.