> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/quickstart.md).

# Quickstart

Sign up, connect a scanner and your code, and get your first exploitability assessments on trial credits.

This page takes you from sign-up to your first exploitability assessments. The trial is free and needs no payment details.

You need:

* Findings from a scanner Konvu supports, such as GitHub Dependabot alerts, Snyk, Semgrep, Endor Labs, or Arnica. A CSV export works too.
* Permission to install an app on the GitHub organization or GitLab group that holds the code behind those findings.

## 1. Create your account

Sign up at [app.konvu.com](https://app.konvu.com). Your first sign-in creates an organization named after your email domain, with **50 free credits**. You can rename the organization later.

{% hint style="info" %}
If a colleague already uses Konvu, ask them to invite you instead. Each user belongs to one organization, and signing up on your own creates a separate one. See [Account Management](https://docs.konvu.com/konvu/administration/account-management.md).
{% endhint %}

Konvu then opens the welcome flow. The next four steps follow it.

## 2. Connect your scanners

Pick the scanner whose findings you want assessed. Konvu imports what the scanner already found. It does not re-scan your code.

| Source            | Setup guide                                                                                                        |
| ----------------- | ------------------------------------------------------------------------------------------------------------------ |
| GitHub Dependabot | [GitHub Dependabot](https://docs.konvu.com/konvu/get-started/bring-in-findings/code-scanners/github-dependabot.md) |
| Snyk              | [Snyk](https://docs.konvu.com/konvu/get-started/bring-in-findings/code-scanners/snyk.md)                           |
| Semgrep           | [Semgrep](https://docs.konvu.com/konvu/get-started/bring-in-findings/code-scanners/semgrep.md)                     |
| Endor Labs        | [Endor Labs](https://docs.konvu.com/konvu/get-started/bring-in-findings/code-scanners/endor-labs.md)               |
| Arnica            | [Arnica](https://docs.konvu.com/konvu/get-started/bring-in-findings/code-scanners/arnica.md)                       |
| CSV upload        | [CSV Import](https://docs.konvu.com/konvu/get-started/bring-in-findings/csv-import.md)                             |

Other sources, such as Wiz, AWS Inspector, and bug bounty reports, are covered in [Bring In Findings](https://docs.konvu.com/konvu/get-started/bring-in-findings.md).

## 3. Connect your code

Connect the repositories those findings come from. Konvu reads the code to check whether each finding can be exploited in your application, instead of only reporting it.

* **GitHub**: install the Konvu GitHub App. See [GitHub Installation](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/managed-analysis/github-installation.md).
* **GitHub Enterprise Server** or **GitLab**: see [Source Code](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code.md).

If your code can't leave your network, Konvu can run the analysis inside your own infrastructure. See [Self-Hosted Analysis](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis.md).

## 4. Choose where to focus

Pick up to 3 repositories for your first assessments. Konvu assesses findings in those repositories only, so your trial credits go to the code you care about most.

A dependency assessment costs 1 credit, and only when it reaches a confident result: **Exploitable** or **False Positive**. New organizations assess `CRITICAL` and `HIGH` findings only. You can add repositories and severities later in **Agents > Coverage**. See [Assessment Credits](https://docs.konvu.com/konvu/administration/assessment-credits.md) and [Assessment Settings](https://docs.konvu.com/konvu/administration/assessment-settings.md).

## 5. Start the assessment

Click **Start assessment**. Konvu assesses a first batch of dependency (SCA) findings in the repositories you picked. Results appear under **Triage** as they complete.

Each assessment ends with one of four results:

* **Exploitable**: the conditions for exploitation hold in your code. Fix these first.
* **False Positive**: Konvu found evidence that the vulnerability can't be exploited in your application.
* **Needs input**: Konvu needs an answer from you, such as how a service is deployed.
* **Inconclusive**: Konvu could not reach a confident result.

See [Reading an Assessment](https://docs.konvu.com/konvu/triage-and-remediation/exploitability-assessment/reading-an-assessment.md) for how to check the evidence behind a result.

## Next steps

* [Remediate](https://docs.konvu.com/konvu/triage-and-remediation/remediate.md): get remediation plans and fix pull requests for exploitable findings
* [Slack Daily Digest](https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/notifications/slack-daily-digest.md): get new exploitable findings in Slack
* [Assessment Credits](https://docs.konvu.com/konvu/administration/assessment-credits.md): buy more credits when the trial runs out
* [Pricing](https://konvu.com/pricing): plans and what they include


---

# 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.konvu.com/konvu/get-started/quickstart.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 `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.
