> For the complete documentation index, see [llms.txt](https://docs.beeta.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beeta.one/platform/orchestration.md).
# Orchestration
Orchestration is a central feature of our beeta.one platform that enables you to deploy data flows on a variety of edge devices. With orchestration, users can seamlessly manage and coordinate the execution of data flows on multiple edge devices to ensure efficient and scalable data processing.
By providing a centralised platform for orchestrating data flows, beeta.one enables you to efficiently distribute workloads, optimise resource usage and scale your deployments on demand. The benefits of beeta.one's orchestration feature are manifold.
Firstly, you now can easily deploy and manage data flows on a large number of edge devices regardless of their geographical location. This enables the efficient processing of data close to its source, reducing latency and improving overall system performance.
Secondly, orchestration simplifies the management of complex data flow topologies. You can define dependencies between different components of data flows to ensure that data is processed in the correct order and results are delivered accurately. This ensures data integrity and consistency across the entire edge computing infrastructure.
In addition, beeta.one's orchestration feature provides scalability and flexibility. Dynamically scale your deployments by adding or removing edge devices as needed without disrupting the overall data flow. This enables seamless expansion and contraction of the edge computing infrastructure according to changing business requirements.
In summary, beeta.one's orchestration feature is a powerful platform feature that enables you to deploy and manage data flows on edge devices in small to large fleets.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.beeta.one/platform/orchestration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
