Product
ProcessProtectReconComply
Use Cases
PSPs & Payment ProcessorsFintechs & Digital BanksFinancial InstitutionsEnterprise TreasuryTransit & MunicipalMining & Resources
Developer
API-FirstMCP for Coding AgentsRuns in Your EnvironmentDeploy & Operate
Built for AI
Meet FloKnowledge BaseOperational ToolsContext-Aware UIDocument Intelligence About
Book a DemoSee It Live →
AI · Woven Through the Platform

An Analyst Inside the Ledger

AI here is not a bolted-on chatbot. Flo reads your ledger through read-only, permissioned tools, cites the records behind every answer, and operates under exactly the same access rules and audit trail as any human user — so an assistant never becomes the gap in your controls, whatever the underlying transaction represents.

Florence — Your In-Platform Analyst

Flo is a conversational assistant built into the operator console. Ask a question in plain language and Flo calls real, read-only tools against your ledger to answer it — then shows its working.

Ask in Plain Language
"What were yesterday's largest transactions?" "Which accounts are fraud-flagged?" Flo turns the question into the right tool calls — no SQL, no endpoint hunting.
A Tool-Calling Loop
Flo chains several read-only lookups together when a question needs them, and answers only from what it actually retrieved — so it will tell you it does not know rather than invent a number.
History & Starter Prompts
Conversations are saved to a History tab, and curated starter prompts get new users productive immediately — both managed from within the app.

Flo tells you exactly what it's doing — the chat sidebar shows a different status for each kind of work:

Flo is thinking… Flo is accessing data… Flo is observing… Flo is SIEM'ing…

Answers Grounded
in the Documentation

A retrieval-augmented knowledge layer lets Flo — and connected coding agents — answer product questions from LedgerFlow's own documentation, not from guesswork.

Semantic Search
Documentation is indexed by meaning rather than keyword, so a question finds the right passage even when the wording does not match.
Grounded Responses
Retrieved passages are handed to the model as context, so answers stay tied to what the platform actually does — with the source material behind them.
Public & Internal Corpora
Documentation is split by audience: external agents only ever reach material cleared for them, while your operators get the fuller internal knowledge base.

One Console for
"Is It Healthy? Is It Under Attack?"

Beyond the ledger, Flo can reach operational tools through the internal MCP server — so an operator asks, in natural language, the questions they'd otherwise jump between three dashboards to answer.

Ledger MCP
Read-only access to accounts, transactions, anomalies, reconciliation, maker-checker and more — the same data, exposed as agent tools.
Read-only
Observability Tools
Query live metrics and logs, search dashboards, and summarise firing alerts. "Is the platform healthy right now?" answered in the console instead of across three tabs.
Observability
Security Monitoring Tools
Search security alerts, summarise by severity and by MITRE ATT&CK technique, and check monitoring coverage. "Are we under attack?" — without leaving the console.
SIEM
Gated & Audited
The observability and SIEM tools require a dedicated permission, are off by default, and every call is audit-logged and traced. Read-only — no active response is ever exposed.
Permissioned

Flo Knows the Page
You're Standing On

Every operator page carries its own embedded context and a tailored set of prompts, so the assistant is always relevant to what's in front of you — no copy-pasting screens into a chatbot.

Embedded Page Context
Each page ships metadata describing what it is and what its data means, so Flo understands the screen it was opened from before you type a word.
Tailored Starter Prompts
Per-page suggested prompts reference that page's own data, turning a blank chat box into a guided set of useful next questions.
Inline Help & "Ask Flo"
The same dual-persona documentation that powers Flo also drives inline help on each page, and "Ask Flo" links hand a specific row straight to the assistant.

Paperwork In,
Structured Data Out

KYC means documents — IDs, proofs of address, registration papers. LedgerFlow reads them for you, so onboarding is not a retyping exercise — and so the same document produces the same fields every time, regardless of who is on shift.

Reads the Document
Uploaded KYC documents are read automatically — text and structure pulled from scans and PDFs before any decision is made, and before anyone has to retype them.
Fills In the Fields
The extracted text becomes the structured fields your KYC workflow needs, with mismatches raised for a human reviewer rather than quietly auto-approved. The decision stays with a person; the typing does not.
Serialised & Controlled
Document processing is queued and paced, so a batch of onboarding documents produces predictable load rather than a spike that degrades everything else.
Private by Deployment
Document understanding can run entirely inside your boundary, so identity documents never leave your perimeter. No off-shore round trip, and nothing to explain to a regulator about where a customer's passport went.

AI Shows Up
Everywhere It Helps

The AI layer isn't a fifth pillar — it amplifies the four you already have.

See what Flo can do with your ledger.
Meet the in-platform analyst that answers questions against your own ledger — with every answer traceable to the records behind it.
See It Live →Book a Demo