---
title: Environments
description: An environment is one deployment of a project, such as staging or production, running on one cluster with its own components and configuration.
---

An **environment** is one deployment of a [project](/concepts/projects), for example `staging` or `production`. It is the boundary that owns components: each environment has its own applications, jobs and databases, its own [variables and secrets](/concepts/variables-and-secrets) and its own [pipelines](/concepts/pipelines).

## Type and cluster

When you create an environment you choose:

- its **type**: `development`, `staging` or `production`, which tells your team what the environment is for (see [Environment types](/reference/environment-types));
- its **cluster**: the [cluster](/concepts/clusters) its components run on. Environments of the same project can run on different clusters, for example production on a dedicated cluster.

## Isolation

Each environment gets its own Kubernetes namespace on its cluster. Components of an environment reach each other inside that namespace; a database in one environment is not shared with another.

## Access

A role grant on an environment covers the environment and every component in it. See [Organizations and roles](/concepts/organizations-and-roles).

## Billing

Kapten bills the time each environment exists, by the minute. See [Billing](/concepts/billing).
