---
title: "Welcome to open·kritt"
description: "Orchestrate AI agents to find real vulnerabilities in code."
---

open·kritt is an open-source, AI-driven security research platform. Instead of pointing
a model at a whole repository and hoping, you break the work into small, well-defined
tasks, run them across AI agents in parallel, and turn the results into de-duplicated,
ranked findings you can validate and enrich with per-finding post-scripts.

<Frame caption="The overview dashboard - blueprints, scans, and findings at a glance.">
  <img src="/images/overview.png" alt="open·kritt overview dashboard" />
</Frame>

## Who it's for

<CardGroup cols={2}>
  <Card title="Security researchers" icon="magnifying-glass">
    Fold AI into your research process without giving up control over prompts, data, or
    models.
  </Card>
  <Card title="Security-minded developers" icon="shield-halved">
    Get AI help writing - and auditing - secure code against a repository you own.
  </Card>
</CardGroup>

<Note>
  **From the team at Kritt.** We built and used this system internally to find real,
  high-impact vulnerabilities, earning **over $1,500,000 in bug-bounty payouts** under the
  researcher name **Blockian**
  ([Immunefi](https://immunefi.com/profile/Blockian/) ·
  [HackenProof](https://hackenproof.com/hackers/Blockian) ·
  [blockian.xyz](https://blockian.xyz) · [@Kritt_AI](https://x.com/Kritt_AI)).
  open·kritt is the open-source distillation of that workflow.
</Note>

## The idea

If you point an AI at a whole repository and ask "find the vulnerabilities," it usually
won't. But if you point it at **one function in one file** and ask a focused question, it
often will. The most effective way to use AI for security research is to give it small,
well-defined, digestible tasks.

open·kritt is deliberately opinionated. It gives you freedom where it matters - your
prompts, your data, your models - and enforces structure where it pays off: a fixed
finding schema, automatic de-duplication, per-finding follow-up scripts, and severity
ranking.

You do not have to begin with a blank workflow. open·kritt includes a
[built-in entrypoint-flow workflow](/workflows/built-in-workflows) that you can inspect,
run, and adapt. An open marketplace for sharing and discovering community workflows is
planned.

## How the pieces fit together

<CardGroup cols={2}>
  <Card title="Workflows" icon="diagram-project" href="/workflows/steps">
    A reusable blueprint: a tree of prompt **steps** the engine runs, feeding each step's
    output into the next.
  </Card>
  <Card title="Post-scripts" icon="list-check" href="/post-scripts/difference-from-workflow">
    Per-finding follow-up that runs after the workflow - validate a finding, build a PoC,
    or write a report.
  </Card>
  <Card title="Severity rankers" icon="signal" href="/severity-ranker/why">
    Markdown rules that tell the model how to prioritize findings for your program.
  </Card>
  <Card title="Scans" icon="radar" href="/scans/create">
    A single run of a workflow against a target repository, with your chosen model and
    harness.
  </Card>
</CardGroup>

## What happens in a scan

<Steps>
  <Step title="Run the workflow">
    Steps execute in depth order and turn focused analysis tasks into candidate findings.
  </Step>
  <Step title="Combine and prioritize">
    open·kritt automatically clusters duplicates and ranks the canonical findings using
    the scan's severity rules.
  </Step>
  <Step title="Validate and enrich">
    One or more post-scripts run on each canonical finding to add verdicts, reports,
    proofs of concept, and other structured context. Post-scripts enrich the result; they
    do not silently delete it.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Explore built-in workflows" icon="boxes-stacked" href="/workflows/built-in-workflows">
    Start from preinstalled research patterns and learn about the upcoming open workflow
    marketplace.
  </Card>
  <Card title="Installation and setup" icon="terminal" href="/getting-started/installation-and-setup">
    Install the Docker stack and configure model access through the guided CLI.
  </Card>
  <Card title="AI provider setup" icon="key" href="/ai-provider-setup/overview">
    Configure Codex, Claude Code, or OpenRouter and understand how each option is billed.
  </Card>
  <Card title="Run your first scan" icon="rocket" href="/first-scan/workflow">
    Build a workflow, add a post-script and a ranker, and scan a repo end to end.
  </Card>
  <Card title="Self-hosted vs managed" icon="scale-balanced" href="/getting-started/self-hosted-vs-managed">
    Understand what you get from the open-source project versus a managed Kritt scan.
  </Card>
</CardGroup>
