Documentation

Everything Akesis does, and how to get the most from it. Start with Getting started if you're new.

Start

Getting started
What Akesis does, who can do what, and the first steps from connecting a repository to the first reviewed fix.

Code hosts
Connect GitHub, GitLab or Bitbucket, choose repositories, and what access Akesis asks for.
Scanners and uploads
Dependabot, Snyk, Strix and any SARIF scanner, plus coverage uploads from your CI.
Jira and Slack
Jira issues for findings that can’t become a pull request, and Slack alerts with a daily digest.

Backlog and findings
How findings are merged and re-scored, what reachability means, statuses, accepted risks and the vendor’s own fix.
Autonomy and policies
Tiers T0 to T3, repository policies, the gates every auto-merge passes, and the emergency stop.
Fix pull requests
How Akesis adopts Dependabot, Snyk and Renovate fixes, opens its own npm fixes, merges, watches and reverts.
AI narratives and assistants
Plain-English risk narratives, and asking Claude or other assistants about your backlog through MCP.
Public API
Read findings, remediation status, narratives and the audit log from your own tools or a SOAR platform, with a scoped token.
SIEM and SOAR recipes
Splunk (CIM-mapped), Microsoft Sentinel, Cortex XSIAM, Torq, Tines and any other SOAR: events in, actions back.

Audit log
What is recorded, verifying the hash chain, exporting it, and how long it is kept.
Administration
Users and roles, single sign-on, and leaving Akesis.
Security and your data
What Akesis reads, stores and never keeps; isolation between organisations; AI and where data is processed.

Troubleshooting
Why a fix is waiting for review, why a pull request isn’t linked, and other common questions.