Frequently asked questions

AWS DevOps Agent is a ready-made, autonomous incident-response agent. B.O.R.I.S is a context layer you build on. B.O.R.I.S connects to your engineering systems — cloud, version control, and team chat — and builds a constantly updating knowledge graph of your infrastructure. You use that context wherever you need it: ask in chat, plug it into your coding agent or CI code review, or point your own agents at it through MCP. So the same context serves development, review, and operations, not just incidents. It answers infrastructure questions for the whole team, captures knowledge that survives when someone leaves, and — unlike AWS DevOps Agent, which stores your data in a managed service — keeps your data at rest in your own environment.

B.O.R.I.S supports all major cloud providers. If you're using other clouds, reach out to our team for confirmation.

Yes, completely. Each customer is kept fully separate, so nothing is ever shared between them. Your data stays yours and never mixes with anyone else's.

Yes. For teams that need full control, we offer a private cloud installation, keeping all data and operations inside your own cloud. On any installation, you can bring your own encryption key and your own AI model.

Yes. There's an agent that runs a cloud bill optimization check — it reviews your monthly cloud spend and tells you where to act.

Yes — Claude, Hermes, OpenClaw, Codex, and anything else that supports MCP. B.O.R.I.S sets up each of your coding agents on install, so they know it's there and use it to look up your cloud and infrastructure.

Yes, Slack is supported today. Teams and Discord are coming. In the meantime, you can plug B.O.R.I.S into your own agents running inside Teams or Discord through MCP.