Akadenia Security docs
Continuous external security scanning for the hosts and domains you own. Start with getting started, or pick a topic.
- Getting startedSign up, create your organization, add your first domain and see its first findings.
- Members and rolesInvite your team and choose what each person can see and change.
- Verifying domainsProve you control a host before it's scanned, by a DNS record or an emailed code.
- Scanners and schedulesWhat each scanner checks and reaches, and how to run scans on a schedule or right away.
- Scanning signed inGive the web scanners a test account so they check what's behind sign-in, including APIs that use expiring tokens.
- Triaging findingsSeverities, how to fix each finding, verifying a fix, setting findings aside, history and alerts.
- ReportsA target's report by topic, printing it, email security reports, and pentest reports.
- Plans and billingFree, pay-as-you-go and Enterprise; what each includes, the spending cap, and paying by card or through AWS Marketplace.
- Connecting AI agents (MCP)Let Claude, ChatGPT, Cursor, VS Code and other MCP clients read your findings and, with your consent, run scans.
- Rate limitsHow many calls the dashboard, the API and AI agents can make, by plan, what each answer says about it, and how to wait and retry.
- Webhooks and ticket automationSend findings to Jira, Plane, Asana or any tool through n8n, Zapier or Make, one ticket per finding, closed when it's fixed.
- Tickets in GitHub and LinearOne ticket per finding in GitHub Issues or Linear, opened when a scan finds it and closed when a scan confirms the fix.
- AccessibilityThe standard Akadenia Security is built to, what follows your device's settings, how it's checked, what's still to do, and how to tell us about a problem.