> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/overview/kumu-io-and-kumu-enterprise.md). # Kumu.io and Kumu Enterprise We offer two Kumu products: Kumu.io and Kumu Enterprise. **Kumu.io** is the online version—you can [sign up at any time online](https://kumu.io/join) for a free account. **Kumu Enterprise** has the same software and features as Kumu.io under the hood, but you can keep your activity fully separate and isolated from the activity of everyone who uses Kumu.io. ## Which product is right for me? Kumu Enterprise is the right choice for teams that are working with highly sensitive data and need deep control over how it's secured—more control than you get when uploading data to Kumu.io. Enterprise versions are also a great option for teams that are legally required to store their data in a specific geographic location (Kumu.io stores data across the world). To get started with Kumu Enterprise and learn more about its security features, please [visit our Enterprise website here](https://kumu.io/enterprise). If you need help with installing, configuring, or upgrading your Enterprise version, [see our full Enterprise guides](/enterprise/index.md). For anyone who doesn't have these higher security needs, Kumu.io will be a much more streamlined, and a just as powerful option. For any additional questions on Kumu Enterprise, please reach out to ! --- # 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.kumu.io/overview/kumu-io-and-kumu-enterprise.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.