> For the complete documentation index, see [llms.txt](https://docs.oveka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oveka.io/links-and-resources/product-sheets.md). # Product Sheets Downloadable product sheets about the Oveka platform and features
Cover image

Oveka Platform Overview

Oveka is a holistic solution to data security and AI governance. Learn about the three core features in our platform overview.Screenshot 2026-10-07 at 1.04.02 PM.pnghttps://oveka.io/hubfs/Oveka/Product%20Sheets/Oveka%20Platform%20Overview.pdf?hsLang=en-us

PromptGuard Overview

PromptGuard sits between users and AI as a protective layer that stops sensitive data from being used in prompts and responses.Screenshot 2026-10-07 at 1.04.08 PM.pnghttps://oveka.io/hubfs/Oveka/Product%20Sheets/Oveka%20PromptGuard%20Feature%20Overview.pdf?hsLang=en-us

Databridge Overview

Databridge enables you to give users and AI secure, controlled, and auditable access to data in platforms across the business.Screenshot 2026-10-07 at 1.04.12 PM.pnghttps://oveka.io/hubfs/Oveka/Product%20Sheets/Oveka%20Databridge%20Feature%20Overview.pdf?hsLang=en-us

Radar Overview

Radar can integrate with hundreds of SaaS products and scan data stores to find sensitive data where it shouldn’t be.Screenshot 2026-10-07 at 1.04.17 PM.pnghttps://oveka.io/hubfs/Oveka/Product%20Sheets/Oveka%20Radar%20Feature%20Overview.pdf?hsLang=en-us
--- # 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.oveka.io/links-and-resources/product-sheets.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.