Application Security Posture Management

Four scanners.
One signal.
Zero duplicates.

coudit aggregates Opengrep, Trivy, Betterleaks and TruffleHog into a single normalized stream. A cryptographic deduplication engine collapses the noise, and a local LLM writes the fix — so your source code never leaves your network.

No credit card. Self-hosted & SaaS. AGPL-safe.
0 scanning engines
0 license fees
0 local AI inference
SHA-256 deduplication
How it works

From repo to remediation in three moves.

No daemons. No long-lived agents on production. Just CI — or your laptop.

01

Run the agent

One Python binary spawns 4 scanners in parallel. Runs on your laptop, in CI, or as an ephemeral Docker container. License-safe by construction.

$ coudit scan ./repo --product api
DEDUP
02

Normalize & deduplicate

SARIF is parsed, severity reconciled (level, CVSS, CWE), paths sanitized. Each finding gets SHA-256(file·line·cwe·tool). Collisions merge. Hit count rises.

3 results → 2 unique, 1 merged
03

Fix with a local LLM

Qwen2.5-Coder or DeepSeek-R1 reads the finding plus a code window and returns a Pydantic-validated patch — explanation, impact, secure code, steps. No SaaS API. No data leaving.

{ "secure_code_patch": "..." }
How you use it

Three ways. Pick the one that fits.

Same engine, same API, same deduplication math — different operational model.

Most teams

Hosted SaaS

We host the backend. You install the agent in CI. Five-minute setup, zero ops on your side.

  1. Create an account, copy your API token.
  2. Add coudit-scan to your CI workflow.
  3. Open the dashboard. Triage. Export to Jira/CSV.
$ pip install coudit-agent
$ coudit scan . --product api \
    --backend-url https://api.coudit.com \
    --token $COUDIT_TOKEN
Solo / OSS

CLI only

Skip the backend entirely. Agent writes SARIF locally; pipe it into GitHub Code Scanning or read it yourself. Free.

  1. Run the agent on your repo.
  2. Get a single merged SARIF bundle.
  3. Upload to GitHub or open in VS Code.
$ coudit scan ./src --product me \
    --output ./out
$ gh code-scanning upload \
    out/coudit-bundle.sarif.json
Live demo

Sixty seconds, from clone to finding.

Run it on this very project. The backend you’re reading right now is the same one shipping to customers.

  • POST a SARIF bundle to /api/v1/ingest
  • Cryptographic deduplication runs synchronously
  • GET your findings as JSON or CSV
  • Optional: trigger an AI patch via local Ollama
Read the API reference
Features

Everything AppSec needs. Nothing it doesn’t.

SAST with taint tracking

Opengrep (LGPL-2.1). Cross-function dataflow for SQLi, SSRF, XSS, deserialization. 300+ rule families.

Secret discovery + verification

Betterleaks (MIT) for speed; TruffleHog (AGPL-3.0) to verify the key is actually live. Run separately at arm’s length.

SCA & CVE intelligence

Trivy (Apache-2.0) against NVD, GHSA, OSV. Direct + transitive dependencies, container layers, infra-as-code.

Deterministic dedup

Same file, same line, same CWE, same tool → same row. Forever. Your backlog stops doubling on every CI run.

Local AI remediation

Pydantic-schema-enforced JSON from your own LLM (Ollama, vLLM, llama.cpp). Your code never sees a third-party API.

License-safe by design

AGPL components are subprocess-isolated. No imports. No FFI. Your SaaS code stays proprietary.

Pricing

Pay for the platform. Not the scanners.

All four engines are open source. We don’t charge for someone else’s work.

Starter

€0forever

Solo developers & OSS maintainers.

  • 1 project
  • 50 scans / month
  • Full SAST + SCA + secrets
  • SHA-256 deduplication
  • SARIF + CSV export
  • Community support
Start free

Enterprise

Custom

Regulated industries & large orgs.

  • Unlimited everything
  • Self-hosted (K8s, air-gapped)
  • Bring-your-own LLM
  • RBAC, audit log, SCIM
  • Dedicated success engineer
  • 4h SLA, NDA, DPA
Talk to sales
FAQ

Questions we get every week.

Do I pay extra to use the scanners?

No. Opengrep, Trivy, Betterleaks and TruffleHog are open source. You pay for the platform that ties them together — deduplication, normalization, AI remediation, integrations.

Where does my source code go?

Nowhere it doesn’t already go. Scans happen on the machine running the agent (your laptop, your CI runner, your container). Only SARIF metadata is shipped to the backend. With self-hosted, even SARIF stays inside your perimeter.

What model does the AI remediation use?

Default is Qwen2.5-Coder-7B via Ollama on localhost:11434. You can point the client at any OpenAI-compatible endpoint — vLLM, llama.cpp, OpenLLM, even your own internal gateway. No call ever leaves your network.

How exactly does deduplication work?

For every incoming finding we compute SHA-256(file_path | line_number | CWE | tool_name). A matching active signature on the same product merges into the existing row, bumps hit_count, and appends to merge_log. New rows are only created when something genuinely new appears.

Is TruffleHog’s AGPL going to infect my codebase?

No. We never link, vendor, or import TruffleHog. The agent invokes it strictly as a separate OS process (binary on PATH or ephemeral Docker container) and reads JSON Lines from stdout. This is the textbook arm’s-length aggregation that the FSF and AGPL section 13 explicitly permit.

Can I bring my own SAST rules?

Yes. Opengrep accepts Semgrep YAML rules. On Pro and Enterprise you upload rule packs in the dashboard; the agent picks them up automatically.

Try it against a real repo today.

Fourteen-day Pro trial. No credit card. Five-minute install.