Money brain · How we build · 11 Nov 2026 · 3 min read

Why Kairos runs on your servers, and a person approves every action

Two design choices we made first, before any feature, and what they mean for your IT and security teams.

A finance team should not have to choose between using AI and keeping control of its data and its money. So we made two choices before we built anything else.

It runs inside your perimeter

Kairos is installed in your cloud or on your own servers, and the model runs there too. Your bank data, invoices and forecasts don’t leave your environment to reach an outside AI service. Your IT team can see what runs and where.

It starts read-only

On day one Kairos can read, not write. It reads bank feeds, the ERP and the finance mailbox, and it produces a forecast and a list of findings. Nothing in your systems changes until you decide it should.

A person approves every action

Kairos recommends: hold this invoice, move this cash, place this amount. A named person on your team approves or declines each one. Kairos never holds your money and never moves it on its own. Your bank executes the payments, under your existing agreements.

Why this matters for results

These choices aren’t only about safety. A CFO who can see every recommendation and its reason ends up trusting the system faster. Trust is what lets the buffer come down and idle cash start working.

If your IT team has questions, our security page sets out the details in a form you can forward.

Want this worked out on your own numbers?