> 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/hybrid-architecture.md). # Hybrid Architecture The hybrid architecture of beeta.one combines the advantages of a cloud-based application with local data processing. This approach allows organisations to take advantage of the latest features and capabilities of the cloud-based application, while data processing takes place on-premises to ensure increased security and performance. The cloud-based application, represented by the beeta.one user interface, provides you with an intuitive and user-friendly interface to design and manage their data flows. Users can benefit from the latest updates and features of the cloud-based application to ensure they have access to the most advanced functionalities. However, the actual processing of the data takes place on edge computers that are located on-premise. This means that sensitive data remains within the organisation, addressing data privacy and security concerns. By processing data locally, organisations can benefit from lower latency, improved response times and increased efficiency. The hybrid architecture of beeta.one enables organisations to strike a balance between the benefits of cloud-based applications and the security and benefits of local data processing. It enables seamless integration of the latest cloud-based capabilities while providing the control and compliance required for on-premise processing of sensitive data. --- # 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/hybrid-architecture.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.