> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The application page

> What each view of an application's page in Ankra shows, where it is in the menu, its address, and the CLI command that reads the same thing.

Open an application from **Applications** and its page replaces the sidebar with the application's own menu. The menu starts with **Overview** and a **Deploy** group that holds **Environments**, **Pipelines** and **Previews**. Then comes one row per view, and last a **Technical details** group that holds **Where it runs**. This page lists every row, in menu order, with what it shows.

Every view lives at one address, `/next/applications/<application-id>?view=<view>`, and a view with sections or tabs adds `&section=<section>`. The **Overview** has no `view`. Links saved before the menu changed still open where they meant, except a bare `view=settings`: it opened Secrets, and it now opens Settings on **Address**.

Most views show one environment at a time: pick it in the environment menu at the top of the page. **Logs** and **Metrics** share their time range, and the place picked under **Running on** stays picked between **Logs**, **Metrics** and **Architecture**.

## The menu

| Row | `view=` | What it answers |
| - | - | - |
| [Overview](#overview) | none | Is it working, in each environment? |
| **Deploy** | | |
| [Environments](#environments) | `environments` | What each environment runs, how a new version gets there |
| [Pipelines](#pipelines) | `pipelines` | Every build, and how its pipeline is set up |
| [Previews](#previews) | `previews` | A running copy of a branch, to try before it is merged |
| [History](#history) | `history` | Every change, where, who did it and how it ended |
| [Logs](#logs) | `logs` | What its containers wrote |
| [Metrics](#metrics) | `metrics` | How it answers requests and what it uses |
| [Security](#security) | `security` | What the last scans found |
| [Data](#data) | `data` | Backups, the database and service bindings |
| [Cost](#cost) | `cost` | What it costs |
| [Secrets](#secrets) | `secrets` | The API keys, passwords and connection strings it reads when it runs |
| [Architecture](#architecture) | `architecture` | What receives requests, what runs, where it keeps data |
| [Settings](#settings) | `settings` | Address, deploys, who runs it, registry, repository, service goals, park or remove |
| **Technical details** | | |
| [Where it runs](#where-it-runs) | `where-it-runs` | Every place it runs, by environment |

## Overview

The application's front page: one card per environment, with what it runs and what it follows (such as **Follows pushes to main**). **Find an environment** filters the cards. **Add** beside the environments starts a new environment on another cluster: see [Environments and branch rules](https://docs.ankra.ai/guides/application-environments.md#add-an-environment-on-another-cluster).

When Ankra has a setup change for the application, the Overview says **A setup change is waiting for your approval.** When a release did not go live, the environment's card offers to put the previous version back: see [Roll back an application](https://docs.ankra.ai/guides/roll-back-an-application.md).

```bash theme={null}
ankra application get <application-id>
```

## Environments

What is live in each environment, and the way to change it. Environments is one page with these parts:

* **What’s live**: the version each environment runs.
* **Deploy a version** (`section=deploy`): choose where the application goes and which version. Ankra checks the cluster has what it needs, and nothing changes until you confirm. Until anything of a new application runs, this part shows its **Go live** steps instead, and opening the application lands here: see [Ship your app](https://docs.ankra.ai/guides/deliver-your-app.md#ship-from-the-portal).
* **Promote a version**: with two or more environments, move the build one environment runs onto the next.
* **Recent releases on** *environment*, with **Full history** linking to History.

```bash theme={null}
ankra application deploy <application-id> --cluster <cluster>
ankra application promote <application-id> --from staging --to production --dry-run
```

## Pipelines

Every build of the application, and how its pipeline is set up. Pipelines has four tabs and opens on the first. See [Ankra Pipelines](https://docs.ankra.ai/guides/ankra-pipelines.md).

| Tab | `section=` | What it shows |
| - | - | - |
| **Runs** | none | Every run, with **Run pipeline** to start one and the **Merge train** below the list. A run opens on its own page with its stages and steps; **Back to all runs** returns to the list |
| **Schedules** | `schedules` | **Scheduled runs**: **Add schedule**, and **Edit schedule**, **Pause schedule** and **Delete schedule** on each one |
| **Cache** | `cache` | The files a pipeline stage keeps from one run to the next: the key the stage declared, where it is mounted, its size and when a run last used it, with **Refresh caches** |
| **Configuration** | `configuration` | **Pipeline configuration and validation** (the stages and **Validate pipeline**), **Build infrastructure** (the build cluster, with **Enable build execution** when its agent has not reported pipeline execution support) and **Repository workflow history** |

```bash theme={null}
ankra pipeline list --application <application-id>
ankra pipeline caches --application <application-id>
```

## Previews

A running copy of a branch, to try before it is merged. Each preview has its own address, and Ankra removes it when its timer ends. **New preview** starts one from a branch that has a published build; each running preview has **Open preview** and **Stop preview**. What new previews start from is set in **Settings → Deploys**, under **Preview defaults**. See [Preview a branch](https://docs.ankra.ai/guides/branch-demos.md).

```bash theme={null}
ankra application demo list <application-id>
```

## History

Every change to the application: what changed, where, who did it and how it ended. A release line you may undo carries **Roll back to** *version* or **Undo this release**: see [Roll back an application](https://docs.ankra.ai/guides/roll-back-an-application.md).

```bash theme={null}
ankra application timeline <application-id> --limit 20
```

## Logs

What the application's containers wrote, read live or searched over a time range. See [Logs](https://docs.ankra.ai/platform/logs.md).

## Metrics

How the application answers requests and what it uses, for the place and the time range you choose. See [Cluster metrics](https://docs.ankra.ai/platform/cluster-metrics.md).

## Security

What the last scans found in the image the application runs and in its code. Filter the findings by severity and open one for what it is and how to fix it; **Fix with Ankra** (or **Ask Ankra how to fix it**) hands it to Ankra AI. See [Security scanning](https://docs.ankra.ai/concepts/applications.md#security-scanning).

```bash theme={null}
ankra application container-security <application-id>
ankra application code-security <application-id>
```

## Data

Data has three tabs and opens on the first:

| Tab | `section=` | What it shows |
| - | - | - |
| **Backups** | none | Backups of the environment, and whether restoring them has been tested |
| **Database** | `database` | Status, storage and backups of the application's database in the environment |
| **Service bindings** | `bindings` | The namespaces a managed service, such as a database, is allowed to connect to |

```bash theme={null}
ankra application backups <application-id>
```

## Cost

What the application costs, with **Explore application cost** for the detail. The row appears only where cost is enabled for the organisation; anywhere else the view reads **Cost is not enabled for this organisation**. See [Cloud Cost](https://docs.ankra.ai/platform/cloud-cost.md).

## Secrets

API keys, passwords and connection strings the application reads when it runs, kept per environment, and **Shared secret defaults** for every environment.

```bash theme={null}
ankra application env-secrets list <application-id>
```

## Architecture

What receives requests, what runs and where the application keeps its data, for the place picked under **Running on**.

## Settings

Settings has one tab per section and opens on **Address**. Each tab says what it is for under its title.

| Tab | `section=` | What it holds |
| - | - | - |
| **Address** | none | Where people reach the application in each environment: its **Ankra address** and **Your domain** |
| **Deploys** | `deploys` | What Ankra deploys on its own: **Deploy on every push** and the branches each environment follows, **Pull requests**, **Preview defaults**, and **Repository setup** with **Retry setup** |
| **Who runs it** | `ai` | What Ankra does on its own in each environment, and on your pull requests, with **Pause Ankra for this app** |
| **Registry** | `registry` | Where the application's images are kept, and how much room they take |
| **Repository** | `repository` | The repository Ankra builds the application from, and the **Deployment files** it keeps there. **Publish to the organisation catalog** offers the application as an add-on: see [Application add-ons](https://docs.ankra.ai/platform/application-addons.md) |
| **Service goals** | `goals` | What you expect from the environment, and what Ankra checks each target against |
| **Park or remove** | `runtime` | Stop the application running somewhere for a while, or take it off for good |

```bash theme={null}
ankra application auto-deploy get <application-id>
ankra application autonomy get <application-id>
ankra application registry get <application-id>
```

See [Environments and branch rules](https://docs.ankra.ai/guides/application-environments.md) for **Deploys**, and [PR preview environments](https://docs.ankra.ai/guides/pr-preview-environments.md) for **Pull requests**.

## Where it runs

Every place the application runs, by environment, and how each one is doing.

```bash theme={null}
ankra application deployments <application-id>
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.