> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/introduction.md).

# Introduction

Harpe is a revolutionary security management tool that addresses a common problem faced by software startups - compliance with security standards.

Traditionally, introducing a security management system is a time-consuming and expensive process. Harpe offers an out-of-the-box solution that simplifies the process of getting audit-ready while delivering significant advantages.

Harpe promises to:

* Reduce real security risk.
* Increase competitive advantage.
* Lower the barrier to entry for startups.

With no complicated technical jargon, anyone can sign up to Harpe and immediately run an effective security management system that gets certified year after year. Unlike other tools that require complex integrations, Harpe does the work for you. This makes Harpe the ideal choice for your organisation's security and compliance.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://manual.harpe.io/start/introduction.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.