> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/this-is-flow-connect/technical-overview.md). # Technical overview Novacura Flow Connect has been built from the ground up as a cloud native product, based on a microservice architecture which provides scalability and redundancy. Novacura Flow Connect was designed with security concerns at the forefront: runtime data is protected using per-organization encryption keys and system-wide authorization rules. ### System overview The Novacura Flow Connect platform consists of the following parts: * **Administration services**, where administrator users sign in to manage applications, users, groups and connectors. * **Clients** for iOS, Android, Windows and Web, in which end users sign in and run the applications developed in Novacura Flow Connect. For client download links, refer to the [downloads page](/flow-connect/reference/flow-connect-downloads.md). * **Runtime services**, which support the execution of applications in the clients. Physically and logically separated from the administration services, the Runtime services are designed for high availability under load. * **Agents** which provide connectivity to external systems. --- # 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.novacura.com/flow-connect/this-is-flow-connect/technical-overview.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.