Resolve Platform · AppSec operations

One ranked queue for findings from 216 security tools

The Resolve Platform reads what your scanners and the Vulnesis CLI already produce, ranks each finding against your business context, and routes the fix to the person who can make it. Software Factory is how the fix ships: its agents hand back verified pull requests for a person to approve.

Request a demo Start free See Software Factory
Vulnesis Software Factory

Findings go in. Verified pull requests come out.

Software Factory takes findings, issues and failing builds through a decision step, a crew of agents and quality gates that are plain rules. People approve the changes that matter. What comes out is a pull request with the run trace and the evidence behind it.

  1. 01 Findings in. A scanner finding, an issue label, a webhook event, a schedule or a board change starts a run.
  2. 02 Agents work. 31 built-in agents in 6 crews patch, test and review on a Pix Sandbox, or on a machine you host.
  3. 03 Gates decide. The quality gate and the release jail are plain rules with no model in the loop.
  4. 04 People approve. Plans, merge reviews and publish reviews wait for a person. Checkpoints queue everything that needs you, and the cockpit shows the head of the queue.
  5. 05 Pull request out. A draft pull request arrives with the run trace, the decision rationale and the evidence files.
  6. 06 Call Pix. Phone Pix to ask how runs are going. Pix reads a plan back before it starts or stops a session, and acts on a plain yes.

Work arrives on the left, passes four stations and leaves as a verified pull request. A person holds the gate at the approval station.

On a call. Pix opens with what is running and what needs you.

After the call. Past calls keep the transcript, and Call Pix picks one up again.

Run it free on your machine · Pix Sandbox from $85 a month · Request a demo

Community includes one self-hosted Belai host. Run belai rc on your machine and the factory runs there.

How Software Factory works · Read the announcement

Resolve Platform · Safe Harbour

Start from a hardened base, not an endless patch queue.

Most findings arrive with the base image and the versions you pinned. Safe Harbour moves both to sources with no known vulnerability, exploit or malware report, so those findings never arrive and the weekly patch run gets shorter.

  1. 01 Compare the base. Each image is matched with hardened bases that run the same runtime, libc and release, scored by Vulnesis and checked against what the vendor claims.
  2. 02 Get a migration plan. The plan reads the SBOM, the Dockerfile your CI builds and where the image runs, then writes the Dockerfile, pinned packages, registry access and checks.
  3. 03 Pin clean versions. One policy across every manifest, lockfiles generated for you, and a pull request to review.

Pix finds out why the checks failed on a Safe Harbour pull request, and upgrades a package to its Safe Harbour pick in a repository that uses it.

How Safe Harbour works · Hardened containers in detail · Request a demo

Safe Harbour: Hardened base, same runtime, libc and release, signed and verified.

Two firewalls · one control plane

Governed before it ever reaches your build

The same policy point sits in front of every LLM call your teams make and every dependency they install, so a refusal happens at the proxy rather than in a report written afterwards.

# Pin a blocked version and the answer is a semantic status:
# 423 malware · 426 vulnerable · 425 cooldown · 428 bad actor
$ npm install @example/telemetry-client@2.4.0
npm error code E428
npm error 428 Precondition Required
# Refused before the tarball downloads, so no postinstall
# script ever runs on the build agent.
Add-on · Package Firewall

Prevention, not another finding

A scanner tells you the malicious package is installed. The firewall means it never was. One policy engine sits in front of 24 package registries and the pkg.go.dev API, from npm and PyPI through Debian and RPM to OCI images, Helm charts and Terraform modules. Every refusal names its reason in the status code and the body. The pkg.go.dev API and AUR are free on every plan; every other registry is the Package Firewall add-on.

Set up the firewall · Explore the AI Firewall · What's free · Package Firewall docs · AI Firewall docs

One platform, every AppSec category

Retire the point tools and their dashboards

The Resolve Platform is an Application Security Posture Management (ASPM) platform that also delivers Unified Vulnerability Management (UVM), Application Security Orchestration and Correlation (ASOC), Continuous Threat Exposure Management (CTEM) and Risk-Based Vulnerability Management (RBVM) in one place, on top of the DevSecOps scanning (SCA, SAST, secrets, IaC and container) you already run.

ASPM

Application Security Posture Management

One live view of application security posture across every repository, scanner and environment, with an owner and business context attached to each finding.

UVM

Unified Vulnerability Management

Every finding from every source deduplicated and normalised into one prioritised queue, instead of a separate backlog per tool.

ASOC

Application Security Orchestration and Correlation

SARIF, SPDX and CycloneDX from 216 documented security tools, normalised against one schema. Overlapping results from four scanners collapse into a single decision with one owner.

CTEM

Continuous Threat Exposure Management

Exposure is scoped and scored against reachability and live exploit intelligence, then re-validated as the intelligence moves. Remediation is tracked against your SLA.

RBVM

Risk-Based Vulnerability Management

Rank open findings against an ordered risk strategy your organisation owns: malware, KEV, EPSS, Coalition ESS, CVSS, CWSS and custom scores.

How risk prioritization works

Drag a rule above another and every open finding re-tiers against it, in the order your organisation decides.

Resolve Platform

Your existing stack, turned into a live monitoring system

1 · Unify

Bring your tools, workflows and data sources onto one platform

Connect the scanners and data sources you already run. Nothing gets ripped out, and nobody has to change how they work.

2 · Prioritise

Apply your business context and GRC frameworks

Set policies that reflect how your environment is actually built and what your auditors ask for.

3 · Automate

Take the grind out of the queue

Deduplication, triage and evidence capture run without a human, and Software Factory agents turn findings into pull requests. Checkpoints queue the few things only a person can decide.

See what Software Factory does
4 · Report & assure

Track performance, decisions and compliance

Board reporting and assessor evidence are byproducts of the daily work. Nothing is reconstructed at quarter end.

See the ten reports it produces
Resolve Platform · Agents and Pix

31 built-in agents for the work behind a finding

Each agent has one job: scan a repository, patch a finding, re-check a verdict, plan a feature, reproduce a bug, fix a failing test, review a pull request or resolve a merge conflict. Belai, the open source coding harness, runs them, and Pix coordinates them by phone.

Pix, the AI Firewall and the agent guides in full · Belai, the Apache-2.0 harness behind the agents

Pix Call

Run the factory from your phone

Tap the phone icon in the Resolve Platform, or the Call Pix shortcut in the installed app, and talk to Pix. It answers from your factory's own records, and it does nothing to a session until you say yes. The same phone carries every stop the factory has, down to the sandbox container.

What Pix can do on a call · Pix Personal Assistant: the factory from your phone

Software Factory

31 built-in agents in 6 crews

Findings in, verified pull requests out, with people approving.

Pix Call

Run the factory by phone

Pix reads the plan back and acts on a plain yes.

MCP server

31 tools in any coding agent

One URL and one header, with live KEV, EPSS and exploit data.

All AI features

AI-BOM, AI inventory and governance

See every model, agent and MCP server your teams actually use.

Where your teams already work

Pipelines, agents, editors, browsers and the phone.

$ vulnetix agent install detects the agents you have and wires each one.

30 CI/CD platforms

GitHub Actions to Tekton, with SARIF out and one exit code. Docs

10 Coding agent add-ons

A dependency guard at the tool call, plus skills and MCP. Docs

13 Editors with the VS Code extension

Findings on the line that causes them, scanned locally. Docs

31 Identifier schemes in the browser

Every CVE on any advisory page, sorted KEV first. Docs

31 Built-in agents in Software Factory

Run them from the Resolve Platform, on a Pix Sandbox or by phone. Docs

Resolve Platform · For every team
CISO and leadership

Exec-ready clarity

Give CISOs and leadership a live read on AppSec posture without waiting for a slide deck.

AppSec and engineering

Stop re-checking the advisory

Most triage time is spent verifying whether the record is even correct: the affected range, the fix version, whether a patch exists at all. Vulnesis settles that before the ticket opens.

GRC and audit

Live GRC visibility

Compliance status is tracked while the work happens. Audit season stops being an archaeology exercise.

Exec-ready reports

Ten reports, produced from the daily work

Nothing here is filled in by hand. Each report is assembled from findings, SBOMs, firewall telemetry and the triage decisions your team already recorded, including the VEX statements Vulnesis mints when someone marks a finding not affected. Period-scoped, org-wide or per repository, exportable as PDF, OSCAL and evidence bundles.

Explore reporting · Read the announcement · Compliance report docs

Resolve Platform · Why now

The four sentences we hear on every first call

SOC operations

Turn vulnerability intelligence into controls the SOC can run today

When a patch is missing, risky, or waiting on a maintenance window, VDB intelligence still gives analysts something concrete to deploy and validate.

Pricing · Browse the malware STIX feeds

Malware STIX feeds

STIX bundles for CTI platforms, SIEM enrichment, EDR blocklists and network controls.

No-patch detection rules

YARA plus Suricata/Snort rules for vulnerable software that cannot be patched today.

Exploit payload validation

Verify IDS, IPS, WAF, EDR and detection-control effectiveness with mapped payloads.

Malscan on-device checks

Find malicious scripts and known-bad packages already on disk.

Package Firewall coverage

Bad packages refused at download, across 24 registries.

End-of-life visibility

Unsupported runtimes and software surfaced as their own queue.

Resolve Platform · Enterprise ready

Built to survive an enterprise estate

Integrations · change management

Slots into the workflows you already run.

Each source connects with one click, and the coverage report shows which are active, stale or missing. Teams keep working the way they do today, so the evidence Vulnesis collects is a side effect of practices already in place rather than a new process to roll out or a business intelligence project to staff.

1 click per source · 216 documented tools · 15 min to first data. See every integration and ecosystem

The platform in action

Take the full platform tour

Vulnerability database

150+ sources behind one API

Aggregated, normalised and enriched. Query it from the CLI or your coding agent while the decision is still open.

$ vulnetix vdb vuln CVE-2021-44228

Explore the VDB · Vulnesis KEV · VDB API docs
Open source

Tools we use ourselves

The same binaries and specifications Vulnesis runs in production, ready to inspect, fork or run without an account. CLI · AGPL-3.0, Belai · Apache-2.0, Pix skills · Apache-2.0, SSVC SDKs · MIT, IETF CRIT draft.

Every open source project · What is free · CLI docs
Vulnesis CLI · Reachability

Is the vulnerable function ever called?

A tree-sitter call graph from your entry points to the symbol in the advisory, with the working shown either way.

How reachability is computed · Reachability docs

Each piece is useful alone. Together they close the loop.

The firewall refuses the malicious package. The CLI proves whether the vulnerable one is reachable. The VDB says whether anyone is exploiting it today. Software Factory agents write and test the fix on a Pix Sandbox and open the pull request. People approve it, and the monitor tells you when the answer changes.

Every step writes a standard file that outlives us: CycloneDX, SPDX, SARIF, OpenVEX, STIX. Take them to a competitor tomorrow if we stop earning the renewal.

Why we build it this way

Common questions

Which Vulnesis product is right for me?

The Resolve Platform suits enterprise AppSec teams and CISOs who need unified visibility and prioritisation across many tools. Vulnesis SCA is built for engineering teams tracking dependency and package vulnerabilities. The Vulnerability Database (VDB) and free Community tier serve security researchers and tooling teams who need programmatic access to enriched vulnerability intelligence. Software Factory is for teams who want agents to turn findings into verified pull requests that a person approves.

What is Software Factory?

Software Factory is the Vulnesis automation layer. Findings, issues and failing builds go through a decision step, a crew of agents and plain-rule quality gates, and come out as pull requests with their run trace and evidence. People approve the changes that matter. It runs on a Pix Sandbox that Vulnesis operates or on machines you host Belai on, and it does not merge code: a person merges.

Who's the team behind it?

Vulnesis was founded by Christopher Langton (CISO/CTO) and Sean Marshall (CEO). Chris has spent 20+ years in enterprise security and holds a NSW Government Innovation Award. Sean is an exited founder who has been building products for just as long. Before starting Vulnesis, they built internal versions of it for 4 enterprise companies and government organisations.

How is Vulnesis different from other AppSec platforms?

Most platforms unify findings from their own scanners only. The Resolve Platform ingests the tools you already run, and 216 of them are documented one by one, each with a page showing the exact format it emits and how Vulnesis reads it. The open source Vulnesis CLI adds its own SCA, SAST, secrets, IaC, container and malware scanning alongside them. Browse them at /integrations.

How long does it take to set up?

Most teams are up and running within 15 minutes: connect your GitHub org, set a starting policy, and unified vulnerability data begins to flow. There is no collector or sensor to install and nothing for developers to change. A full organisation rollout usually takes a few days.

Ready to make AppSec work the way it should?

The Vulnerability Database, Resolve, SCA and Software Factory cover the whole path from raw advisory to a verified pull request. Each team adopts the piece built for it, on its own timeline.

Request a demo Start free Explore Software Factory