Akmatori vs B.O.R.I.S.
Akmatori
akmatori.com
B.O.R.I.S.
getboris.aiSide by side
| Figure | Akmatori | B.O.R.I.S. |
|---|---|---|
| Price from | Free | $500/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · AI DevOps Assistants | 9.1 (#1) | 7.8 (#12) |
| Data residency | Self-hosted deployments keep incident data inside the operator's infrastructure, and local-model mode avoids external AI egress. | The maker says B.O.R.I.S runs inside the customer's cloud account and stores data on the customer's side. |
| Deployment | Akmatori can be deployed with Docker Compose or Helm, including fully on-premises with local models for air-gapped setups. | The FAQ says private cloud installation keeps all data and operations inside the customer's cloud, and allows customers to bring their own encryption key and AI model. |
| Support | The maker directs bug reports and product questions to its public GitHub issue tracker and provides separate email contacts for general inquiries, technical support, and security reports. | The maker invites prospective customers to contact the team for questions, demos, or technical discussions. |
Plans
In their own words
Akmatori
Akmatori turns production alerts into AI-assisted incident response workflows for SRE, platform, and DevOps teams. Its agents collect logs, metrics, deployment context, and runbook knowledge to investigate incidents and suggest next actions. Alerts can come from Alertmanager, PagerDuty, Grafana, Datadog, and Zabbix, while Slack channels can also be monitored. Agents access infrastructure through SSH, Kubernetes, scripts, and API clients. Proposed risky actions require approval in the web interface or Slack before execution. Akmatori supports OpenAI, Anthropic, Google, OpenRouter, NVIDIA NIM, MiniMax, and OpenAI-compatible endpoints, including on-premises models. Recurring investigations can run as cron jobs with configured prompts and tool allowlists, posting results to Slack. Deployment uses Docker Compose or Helm and can be fully on-premises for air-gapped setups. The maker says incident data stays in the customer’s infrastructure unless an external provider is configured. The Apache 2.0 project provides a REST API with documented incident operations, authentication, webhooks, and OpenAPI 3.0.