This page defines the core terms and concepts of the Control Hub.
Agent
An agent is an AI agent that answers questions and performs tasks on the platform. It is not built and deployed on its own: an agent is a feature of a service component, and one service can provide more than one agent.
You reach an agent through the service that provides it. An agent therefore has no endpoint of its own, and it is available only while the service deployment that hosts it is running.
Component
A component is part of a project. A project groups its components so they are versioned and deployed together. Components come in the following types:
|
Type |
Description |
|---|---|
|
Service |
A component that provides functions and data to apps and to other services. |
|
App |
A web frontend that users open in the browser. |
Some deployments are deployments of standalone services that are not part of any project. They carry a Legacy badge next to their name. A legacy service has no components, so it cannot be expanded, and it shows no version and no endpoint.
Refer to Working With the Deployment Detail Page for more information on the component details.
Configuration
Configuration holds the runtime settings of a deployment. It exists at two levels:
-
Project-level configuration applies to the whole deployment.
-
Component-level configuration applies to a single component.
You edit configuration in the configuration editor. When you apply a change, the deployment reloads the new settings without a full restart.
Refer to Configuring a Deployment for details.
Deployment
A deployment is a running instance of a project in an environment. Each deployment has a name, so you can run more than one deployment of the same project, for example in different environments. You monitor and manage deployments in the Deployments view.
Refer to chapter Deployments for details.
Environment
An environment is the target you deploy a project to. Environments keep deployments separate from one another, for example a development environment and a production environment. One project can be deployed to several environments at the same time.
Refer to chapter Deployments for details.
Project
A project is a versioned, deployable unit made of one or more components. Projects are published to the platform and appear in the Projects Catalog, where you browse them and deploy them.
Refer to chapter Projects Catalog for details.
Status
Status tells you whether a deployment or a component is running. A deployment reports one of the following states.
|
Status |
Description |
|---|---|
|
Started |
All component deployments are running. |
|
Starting |
The deployment is starting up. |
|
Stopped |
The deployment is not running. |
|
Multiple |
The component deployments are in different states, for example some started and some stopped. The Multiple status applies to a project deployment as a whole. It indicates that the component deployments currently have different statuses.
|
|
Failed |
The deployment has failed and is in an error state. |
While a project or component deployment is starting, its indicator is animated.
Refer to Working With the Deployments View for further information.
Version
Each time a project is published, it becomes a new version. When you deploy, you select which version to use.
Refer to Managing Deployments for details.
Related Content
Related Pages: