Skip to content
VITI Security
Contact

Vexta · Alongside your toolkit

What Vexta adds to your free, open-source toolkit

The open-source security community builds excellent tools, and most practitioners already run several of them. Vexta isn't a pitch to replace any of that - it's what we built for the step that comes after a scanner surfaces a candidate: proving it's real, tracking it, and getting it in front of a client or a bounty platform without re-doing the work by hand on every re-scan.

Start a free trial →See the full platform

Where it fits

It's a downstream step, not a replacement

Keep your recon tools, your template scanners, your fuzzers, and your proxy - Vexta doesn't ask you to change any of that. Point it at the same targets you're already working, or feed it a candidate finding your other tooling turned up, and it takes over from there: verify, de-duplicate against your scan history, track a triage state, and produce a report you can hand to a client or attach to a bounty submission.

  • No workflow to migrate - it sits alongside what you already run
  • Self-hosted as a single binary, so this step happens on hardware you control
  • Nothing here is a judgment on the tools you already trust - they're solving a different problem

What it adds

Seven things a raw scanner output does not give you

None of this requires giving up a tool you already use - it's what happens to a finding after your scanner surfaces it.

Verification (proof-of-exploitation)

Before a candidate finding reaches a report, a non-destructive verifier tries to safely confirm it. Findings come back proven, refuted, or unproven - a network hiccup never gets recorded as a false all-clear.

Dedup across scans

Every finding gets a stable fingerprint from the target, type, URL, parameter, and payload signature. Re-scan the same target next month and Vexta marks a re-discovery as one instead of reporting it twice.

Triage state

Every finding carries an operator-managed status - open, submitted, duplicate, paid, wont-fix, or ignored - plus a note and an assignee. Nothing sits in an untracked spreadsheet row.

Confidence scoring

A 0-100 score per finding, combining severity, detector confidence, proof status, reachability, exploit-probability, and known-exploited status - so the handful that matter float above the noise.

Reports a client can read

HTML, PDF, DOCX, SARIF, JUnit, and Markdown export, including bounty-platform-ready PoC packages - not a raw JSON dump you have to reformat before anyone else can read it.

Scans without a live feed

10,000+ community scan templates (ProjectDiscovery's open-source nuclei-templates, checked by our own verifiers) and a local CVE mirror ship inside the binary, so scanning does not wait on - or depend on - an external feed being reachable. Activation and license check-ins still need a connection.

Respecting scope

Scope is enforced at the network layer, not left to discipline: out-of-scope hosts are excluded from a scan, and a bounty program's published scope can be imported directly rather than re-typed by hand.

Frequently asked questions

Do I need to stop using my other tools?
No. Vexta is built to sit downstream of the recon and scanning tools you already run, not to replace them. Point your existing tooling at a target however you already do, then bring the candidate findings into Vexta for verification, triage, and reporting.
What does 'verified' actually mean here?
A non-destructive verifier attempts to safely confirm each candidate finding before it is shown to you. The result is recorded as proven, refuted, or unproven - a network error or an offline target never gets recorded as a false negative.
Can Vexta run offline or air-gapped?
Partly. Scan templates and a local CVE database are bundled into the single self-hosted binary, so scanning does not depend on reaching an external feed. Vexta does need to reach our license server to activate and to check in; if the server is briefly unreachable, it keeps working for a grace period. When connected it also fetches template and software updates, and AI-assisted triage calls out only if you turn it on with your own API key. Fully air-gapped use is not supported today.
Does Vexta respect a program or engagement scope?
Yes. Out-of-scope hosts are excluded at the network layer rather than left to manual discipline, and a bug-bounty program's published scope can be imported directly instead of re-typed by hand.
Is this only useful for pentesters and bug-bounty hunters?
No. An SMB running Vexta against its own application gets the same verified, de-duplicated, triaged list - just without the bounty-platform export step. The underlying engine is the same one we run on VITI engagements before we file a finding.
How much does it cost, and is there a trial?
Vexta has three plans that unlock features by license from the same binary. Pro and Enterprise can request a time-limited free trial. Current numbers, currencies, and trial length live on the pricing page.

Bring your next candidate finding into Vexta and see what changes.

Keep everything else in your workflow exactly as it is. This is just the step after your scanner already found something.

Start a free trial →See plans & pricing