> For the complete documentation index, see [llms.txt](https://docs.catchify.sa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catchify.sa/readme.md). # Welcome to Catchify Welcome to the Catchify Client Portal! This documentation is designed to help you confidently navigate our platform and take full advantage of our Penetration Testing as a Service (PTaaS) offering. ### 🚀 Our Mission At **Catchify**, our mission is simple:\ **We aim to automate penetration testing and deliver the highest impact for your organization.** We believe in reducing noise, accelerating response times, and giving you full control and visibility over your security testing process, all in one secure, easy-to-use platform. ### 📘 What You’ll Find Here * How to set up your account and company profile * How to manage users, assets, and contacts * How to request, track, and manage pentests * How to review and respond to security findings * Tips for collaborating with your pentesters in real time Whether you're a security lead, a developer, or a compliance officer, this guide will walk you through everything you need to know. *** Let’s get started. You’re in good hands! --- # 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.catchify.sa/readme.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.