Dradis vs Reconmap

Dradis supports security assessment work from kickoff through collaboration, reporting, remediation and workflow automation. It organizes assessment information with structured data, templates and automation to create consistent deliverables, and its review process lets teams examine work in a PR-style format before it reaches a report. Risk tools include CVSSv4, DREAD and MITRE ATT&CK calculators, with OWASP, PTES, OSCP, HIPAA, PCI and custom methodologies. Dradis lists more than 47 integrations across scanners, ticketing and SSO, including Nessus, Burp Suite, Nmap, Qualys, Jira and Okta. A REST API, webhooks and rules engine support integrations and automated workflows. Remediate adds tracking of fixes and integrations with Jira, Azure DevOps and ServiceNow. The software is self-hosted and can run without an internet connection; the maker says it cannot access customer data. Community Edition is free for one project at a time. Assess costs $3,600 a year and Remediate costs $7,200 a year, each with a three-seat minimum.

Reconmap is a free, open-source collaboration platform for planning, conducting, and documenting penetration test projects across assets and clients. It supports multiple top-level organisations and includes project templates, task management, and client management. Vulnerability tracking and a templates database help organize findings, while users can automate security commands and schedule them with cron expressions. Reports can be generated in Word, Markdown, and Typst formats, with custom whitelabel reporting. Integrations can send vulnerabilities to Jira or Azure DevOps and deliver event-driven HTTP notifications through webhooks. Security features include SSO, OpenID and SAML user federation, two-factor authentication, email verification, and an audit log. A REST API with token authentication supports connections to external tools and scripts. Deployment options include Docker Compose, Kubernetes, manual installation, and hosted SaaS maintained by the project’s lead developers through Netfoe. The documentation positions Docker Compose for small teams and Kubernetes for production deployments and large teams; it also cautions that Compose is not designed for high availability or horizontal scaling out of the box.