> Index of every page on this site: [llms.txt](https://docs.a-line.cloud/llms.txt)

# Projects and apps

> How apps are grouped on a cluster.

## Projects

A project groups related apps on one [cluster](/concepts/clusters-and-pools).
Its `name` is also its Kubernetes namespace; `display_name` is what the
dashboard shows.

- **Isolated projects**: apps in the project cannot reach each other over the
  network unless a connection allows it. You choose this when you create the
  project and can switch it later; isolating an existing project blocks
  traffic between apps that are not declared as connections.
- **Outbound traffic**: in `public` mode apps may reach any public address
  (except TCP port 25) plus an allowlist. In `isolated` mode they only reach
  the allowlist and the platform's own endpoints. Apps can override the mode.

## Apps

An app is one workload in a project. Its name is 1 to 63 lowercase letters,
digits or hyphens, unique in the project. An app runs one of:

- **An image** you name, such as `nginx:1.27`.
- **A template** from the catalog, such as a database.
- **A Git repository**: the platform [builds](/concepts/builds-and-deploys)
  an image from a GitHub repository and branch, with your Dockerfile or a
  build preset.

Each app has environment variables, secrets, a container port, a replica
count or autoscaling, and optional [domains](/concepts/domains).
