The Resolve loop: discover, prioritise, remediate and prove, each feeding the next. The monitor re-scores daily.
- 150+ vulnerability sources, reconciled
- 216 security tools ingested, each documented
- 10 exec-ready reports from the daily work
- 15 min from GitHub org to first data
Four jobs, one platform, one record of every decision.
01 · Discover: Everything you ship, in one inventory
Your own scanners plus the Vulnesis CLI, tied to repositories, owners and assets. SCA, SAST, Secrets, IaC, Containers, Licences, Malware, AI-BOM, CBOM, 216 tools.
02 · Prioritise: Your order, not a vendor score
Fifteen signals in a strategy you own, from malware and four KEV lists to reachability and your own scores. Risk strategy, KEV Watch, Reachability, Policies, Threat model.
03 · Remediate: Agents write the fix, people approve it
Software Factory runs 31 built-in agents in 6 crews that patch, test and open the pull request on a Pix Sandbox, and checkpoints queue what needs a person. Safe Harbour starts images from a hardened base and pins clean versions, so less needs patching, and defences cover what cannot be patched today. Software Factory, Pix Sandbox, Agents and Pix, Safe Harbour, Dependency curator, Campaigns, Virtual patching, Package Firewall.
04 · Prove: Evidence as a by-product
Reports, gates and attestations assembled from decisions your team already recorded. 10 reports, Release jails, Quality gate, TEA.
Resolve Platform · The platform
See the platform in action
Real screens from the Resolve Platform, grouped by the job they do. Each one links to the page that covers it in depth.
Discover
- Org-wide Findings Analytics: One live view of reachability, fixability, exploitability and aging across every repository, with time-series trends and exposure breakdowns.
- AI Bill of Materials: Every model and dataset your applications load, catalogued in one AIBOM with provenance, licensing and supply-chain risk attached.
- Cryptography Bill of Materials: Algorithms, certificates, key lengths and crypto libraries, scored for post-quantum readiness against nine national compliance lenses.
Prioritise
- Your Prioritisation, Not Ours: An ordered rule strategy you write and reorder yourself. Impact, exploitation prediction and your own recast scores decide the priority tier, and the ladder that produced it is on the page.
- Threat Modelling from your evidence: A data-flow diagram built from what your scans actually found: trust zones, entry points, the third parties your code reaches, and the threats on each, decorated with STRIDE, LINDDUN, DREAD, PASTA or OCTAVE without rearranging the diagram.
Remediate
- Safe Harbour: Start from a hardened base: each image compared with hardened equivalents and a migration plan written for it, and every dependency moved to the closest clean version.
- Remediation Campaigns: Freeze the set, say what done means, and burn it down against a denominator that cannot move. Progress and proof stay two numbers.
- The Questions Before The Sprint: Is a patch even possible, how far the version has to move, will a bump break a peer, who is still here to do the work.
- Detection Rulesets: Snort, Suricata, YARA and Nuclei rules matched to the CVEs in your stack, ready to deploy on your IDS and IPS.
- Intelligence Where You Read Advisories: The browser extension reads the CVEs on whatever advisory page you are already on and sorts them KEV first, with exploitation status and your own exposure attached.
Prove
- Exec-ready Compliance Reports: Built from your findings and SBOMs rather than a questionnaire. Exportable as PDF, OSCAL and an evidence bundle.
- Exposure and Remediation Performance: Mean time to remediate against your triage policy, KEV and aging pressure, firewall blocks, and findings mapped to MITRE ATT&CK.
- Release Jails: Evidence older than the window you set, or missing entirely, fails rather than passing quietly.
- Transparency Exchange: A TEA provider you can query rather than a folder of SBOMs. Every insight tile is labelled with the CEL predicate that produced its number, so the count is auditable rather than asserted.
Resolve Platform · Architecture
Built to survive an enterprise estate
- Asset-first design: every vulnerability arrives already tied to an asset, an owner and its business context.
- Contextual prioritisation: AI and decision trees that learn from your environment and past decisions.
- Unified vuln control: one platform for all vulnerability data, regardless of source or tool.
- Flexible data orchestration: connect any tool that exports a standard format such as SARIF, SPDX or CycloneDX.
- The scan does not end with the pipeline: Vulnesis keeps re-scoring the dependencies already in your SBOM. You hear about it the day a package you shipped last quarter turns exploitable.
- Enterprise-ready architecture: runs on Cloudflare's edge network. Data residency and latency are handled before you ask.
- Low-friction adoption: start in 15 minutes with no agents to install and no infrastructure to change.
- Same rules as the CLI: Resolve consumes the same OPA rules used by the open-source Vulnesis/cli. Browse the registry · Quality gate policies
Standards in, standards out: CycloneDX 1.7, SPDX 2.3, SARIF, OpenVEX, CSAF, OSCAL, STIX 2.1 and TEA.
Identity: Sign in the way your organisation does
SSO and passkeys on every plan, with enforced SSO and company-domain provisioning on Business and Enterprise.
Deployment: SaaS on the edge, or yours
Cloudflare-native SaaS by default. Enterprise runs on your premises or fully air-gapped with a custom SLA.
Disclosure: A GCVE Numbering Authority
As GCVE GNA 110 we run coordinated disclosure and publish every record in public. Disclosure programme · Security at Vulnesis
Plans: Community free, Pro $20 a month, Business $450 a month, Enterprise custom. Compare plans
Ready to make AppSec work the way it should?
Each team adopts the piece built for it, on its own timeline.
Request a demo