---
title: "Glossary"
url: https://docs.corefinity.com/start/glossary
type: page
last_updated: 2026-11-13
feature: start
---
# Glossary

The words these docs, the API and the MCP server use, each in one sentence.

## Hosting

| Term                     | Meaning                                                                                      |
| ------------------------ | -------------------------------------------------------------------------------------------- |
| **Site**                 | One website or application on Corefinity, with all its environments.                         |
| **Environment**          | One running copy of a site, with its own files, database and address.                        |
| **Production**           | The environment visitors reach on the site's domain.                                         |
| **Staging**              | An environment for testing changes before they reach Production.                             |
| **CoreStack**            | One managed site with its environments, on Corefinity's platform or inside your CoreCluster. |
| **CoreCluster**          | Your own managed cluster, whose package sets the capacity its sites share.                   |
| **CoreStack Enterprise** | A larger site that Corefinity's engineers size and set up with you.                          |
| **Managed Websites**     | The list of every site you can open, whichever product it is on.                             |
| **Package**              | The CPU, memory, disk and backups a CoreStack site or a CoreCluster pays for.                |
| **Capacity**             | Cores, memory, disk or log storage added to a package by the unit.                           |
| **Server type**          | The kind of server a site runs on: **Standard** or **Performance**.                          |
| **Platform**             | The application a site runs, such as WordPress, Magento 2 or Laravel.                        |

## People and access

| Term                    | Meaning                                                                                            |
| ----------------------- | -------------------------------------------------------------------------------------------------- |
| **Organisation**        | The account that owns your sites, users and billing.                                               |
| **Agency**              | An organisation that manages sites for its clients.                                                |
| **Client organisation** | An organisation linked to an agency.                                                               |
| **User**                | A person with a sign-in to the Control Panel.                                                      |
| **Owner**               | The role that can do everything in an organisation.                                                |
| **Role**                | A named set of permissions given to a user.                                                        |
| **Two-factor**          | A code from an app or a text message, asked for after your password.                               |
| **SSH user**            | A login to a site's shell; an SFTP user reaches one folder for file transfer only.                 |
| **SSH key**             | A public key that lets a person or a server log in over SSH without a password.                    |
| **Firewall**            | The list of IP addresses allowed to connect over SSH and to see a site that is closed to visitors. |
| **Password protection** | A browser login in front of an environment or one of its paths.                                    |

## Code and changes

| Term                    | Meaning                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------------- |
| **Deployment**          | One run that builds your code from Git and puts it live.                                    |
| **Release**             | The code a deployment put live; a roll back returns to the one before.                      |
| **Deployment mode**     | How changes reach a site: by manual uploads or by deployments from Git.                     |
| **Pipeline**            | The stages a deployment runs through, each with its commands.                               |
| **Deployment template** | An organisation's pipeline for every site of one platform.                                  |
| **Variable**            | A value a deployment's commands can read, kept out of the repository.                       |
| **Private registry**    | An npm scope or Composer repository a build signs in to.                                    |
| **Backup**              | A saved copy of an environment's files and database that you can restore.                   |
| **One-off backup**      | A backup you take yourself, beside the scheduled ones.                                      |
| **Restore**             | Putting a backup's files, database or both back onto an environment.                        |
| **Copy**                | Moving one environment's files, database or both onto another environment of the same site. |
| **Maintenance mode**    | A switch that shows visitors a maintenance page while you work on a site.                   |
| **Maintenance window**  | The four hours of the day in which routine maintenance and queued changes happen.           |
| **Pending change**      | A change waiting for the maintenance window, which you can apply sooner or cancel.          |
| **Scheduled task**      | A command a site runs on a schedule.                                                        |
| **Redirect**            | A rule that sends visitors from one path to another address.                                |
| **Web server rules**    | Your own nginx rules for a site.                                                            |
| **Primary URL**         | A live site's main domain.                                                                  |
| **Canonical address**   | The one of `www` and the bare domain that visitors land on.                                 |

## API, MCP and AI

| Term             | Meaning                                                                                                    |
| ---------------- | ---------------------------------------------------------------------------------------------------------- |
| **API token**    | A key that lets a script use the API as you, with the scopes and expiry you choose.                        |
| **Scope**        | What a token may do: `read`, `write`, `exec` or `destructive`.                                             |
| **Operation**    | One change the Control Panel is carrying out, such as a create or a restore, with a status you can follow. |
| **Refusal**      | An answer that says why a request was not carried out, with a `reason` to act on.                          |
| **MCP**          | The Model Context Protocol, through which an AI assistant uses the Control Panel for you.                  |
| **AI assistant** | A program such as Claude or ChatGPT that you connect to your organisation.                                 |
| **Grant**        | A personal MCP token or a connected app, with its scopes, limits and expiry.                               |
| **Pin**          | A limit that ties a grant to chosen clusters, sites or environments.                                       |
| **Confirmation** | A value an assistant must send back, such as the site's domain, before a destructive or billable call.     |
| **Playbook**     | A step-by-step prompt the MCP server offers for a common job, such as `go-live`.                           |
| **App**          | An interactive view, such as a log viewer, that an assistant can show inside the chat.                     |

## The Control Panel

| Term             | Meaning                                                               |
| ---------------- | --------------------------------------------------------------------- |
| **Dashboard**    | A page of widgets; **Home** is your own.                              |
| **Widget**       | One tile on a dashboard: a status, a count, a list or a chart.        |
| **Display link** | An address that shows a dashboard on a wall screen without a sign-in. |
| **Ticket**       | A conversation with Corefinity's support team.                        |
| **Order**        | A purchase of a CoreStack site or a CoreCluster, with its status.     |
| **Demo**         | A free trial site or cluster that ends unless you keep it.            |

## Names that changed

| You may still see         | It means                                                                                    |
| ------------------------- | ------------------------------------------------------------------------------------------- |
| Managed Clusters          | CoreCluster. The Control Panel's menu entry keeps the old name.                             |
| Company, Company settings | Organisation.                                                                               |
| Website                   | Site. CoreStack Enterprise screens and endpoints say website.                               |
| Snapshot                  | Backup. The API, the MCP tools and the organisation's **Snapshots** page keep the old name. |
| Manual backup             | One-off backup.                                                                             |
| Cron, cron job            | Scheduled task.                                                                             |
| HTTP authentication       | Password protection. The API and the MCP tools keep the old name.                           |
| Personal access token     | API token.                                                                                  |

The same list is published for agents as [`taxonomy.json`](/ai/docs-for-agents).
