> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/overview/runtime.md).
# Run concepts
Learn about Run concepts in the Digibee Integration Platform
## Deployment
Deployment refers to the process of activating pipelines that have already been configured with a trigger. This activation can happen in either test or production. If you want to learn more about how to deploy a pipeline, read the [documentation](/documentation/development-cycle/overview/deployment/deployments.md).
The deployment has three related concepts:
### Pipeline size
The pipeline deployment size depends on the processing capacity and memory of each replica. There are three sizes for deployments:
* SMALL, 10 consumers, 20% of 1 CPU, 64 MB memory
* MEDIUM, 20 consumers, 40% of 1 CPU, 128 MB memory
* LARGE, 40 consumers, 80% of 1 CPU, 256 MB memory
For example, if you configure a SMALL deployment size for your pipeline executions, it means that 10 messages can be concurrently processed.
### Concurrent executions
Concurrent executions represent the number of executions each deployed replica can run at the same time. The maximum number of concurrent executions depends on the deployment size configured.
Learn more about these concepts in the [Pipeline Engine documentation](/documentation/development-cycle/overview/runtime/pipeline-engine.md).
### Replicas
Choosing the adequate number of replicas will support your integrations with high availability, guaranteeing their autonomy and the efficiency of their concurrent executions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digibee.com/documentation/development-cycle/overview/runtime.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
