Different by Design We start with humans, not AI

One platform for document-heavy operations.

Knowledge of your customers and vendors, captured by your team and applied by the platform. Activities run the automated work. Tasks are how your people show up. One audit trail across the lot.

In production · streaming 1,547,332 Activities · this month
Invoice processing 912k / 30d
847Tasks
Financial spreading 1.1k / 30d
194Tasks
Covenant compliance 980 / 30d
127Tasks
KYC refresh 3.2k / 30d
73Tasks
Loan packet review 1.4k / 30d
412Tasks
Claims intake private beta
12Tasks
How it works

Two kinds of work. One workflow.

The work your people do, where judgment matters: reviewing, approving, handling exceptions. We call those Tasks. The runs of automated work the platform takes off your team's plate: extraction, validation, posting to systems. We call those Activities.

Activities create Tasks when they need a human. Tasks finishing fires the next Activity. The choreography is a workflow, and it sits in one audit trail.

Task · In Review
Review the four covenant fields the system flagged as low-confidence
Owned by an analyst on Lending Operations Document and system context attached
Maker Q3 Statements Borrower: Northwind Foods

A row a person sees in their queue. Owned, reviewable, completable. When the Task completes, the workflow carries on.

Activity · Running
Loan Packet Intake — running against today's arrivals
  1. 1 Ingest Pull packet from client SFTP & classify document types
  2. 2 Service call GET /borrowers/{id} on client core banking API for entity profile
  3. 3 AI agent Extract fields with borrower-specific rules & score per-field confidence
  4. 4 Decision If confidence < 0.92 or rule mismatch → branch to review
  5. 5 Task Create reviewer Task & wait for analyst sign-off
  6. 6 Service call POST results to client LOS & write audit row to ledger

One run of automated work — service calls, AI agent steps, branch decisions, and human Tasks composed in order. Every step writes to the same audit trail.

Process, not paperwork

Activities are your business processes.

We don't sell extraction. We run the process the document is part of. Three live today on Kodexa:

Same workflow shape, different document types. What one team builds, the next team binds.

Live operations · workflows in production
Streaming 1,547,332 Activities · this month
Activities · 30d 1.5M+ across regulated industries
Tasks · open right now 2,418 in customer queues
Tenants live 28 banks, insurers, lenders
Audit trail 100% human + automated work
Activity Plan
24h trend
In flight
Volume · 30d
Tasks open
Status
Invoice processing3-way match · vendor rules · posting
247
912kinvoices · 30d
JLMRSK 847 open
Live
Financial spreadingmulti-year · multi-standard · maker/checker
62
1.1kstatements · 30d
DPAT 194 open
Live
Covenant compliancecross-check · breach detection · attestation
34
980checks · 30d
RBHN 127 open
Live
KYC refreshperiodic review · entity rules · adverse media
18
3.2kreviews · 30d
EK 73 open
Pilot
Loan packet reviewstructuring · stips · approval routing
91
1.4kpackets · 30d
TCWO 412 open
Live
Claims intakeFNOL · policy match · packet routing
9
private beta
12 open
Beta
Knowledge

The rules your team already applies. Captured.

Every borrower files differently. Every vendor invoices differently. Your analysts know this — which line items Vendor X always misplaces, how Borrower Y reports operating expenses, why Customer Z's accruals need a second look. Today that lives in their head. On Kodexa, it lives as the rules and exceptions inside the workflow.

Captured at the right grain. Customer-level rules where the work is customer-specific. Vendor-level rules where it's vendor-specific. The way your team thinks, not a single global model that flattens the differences.

Reviewable and editable. A rule isn't a black box. It's a row in a library — what the rule does, when it fires, who last changed it. Edit it the way you'd edit a spreadsheet formula your team owns.

Customer-owned. Model-portable. The rules belong to your tenant. They never cross customers. Foundation models change underneath; the Knowledge layer stays.

See how Knowledge works
Knowledge / Library
Vendors
Northwind Foods 14
Acme Capital 9
Aperture Logistics 7
Initech 5
Hooli Manufacturing 4
Borrowers
Cyberdyne Systems 11
Stark Holdings 8
Search rules… 14 rules · 0 drafts
PO number lives in comments Edited 4d ago · M. Chen
when document.vendor == "Northwind Foods"
map  po_number ← regex(comments, /PO[-\s]?(\d{6,})/)
fires on Activity: AP-Intake · last run 12m ago
Vendor scope Auto-applied · 1.2k docs
Tax line is VAT_RECOVERED, not VAT 2w ago · S. Patel
Freight charge expected on every invoice ≥ $5,000 3w ago · M. Chen
Net-45 default, override on terms_text 5w ago · A. Rivera
Agent proposal · Promote "Group line items by ship-to" — Review
tenant: northwind-prod Tenant-isolated
Agents

Agents work in service of the knowledge your team has built.

Three places agents show up inside Kodexa. None of them act without human review.

Studio

Agents draft the routine pieces of an Activity Plan from a use-case description: schemas, validations, review screens, test cases. Configuration that used to take a services engagement starts as a draft an analyst edits.

Workflow

Agents work routine exceptions alongside humans. The clear cases come off the queue automatically. The judgment calls stay with the people who should make them.

Knowledge

Agents propose new rules from the corrections analysts make. Your team's edits become Knowledge with one click, instead of being lost in an email thread.

The platform can't do anything your team couldn't do. Agents are the same.

See how agents fit
Built for regulated industries

The platform can't do anything your team couldn't do.

Same rules. Same guardrails. Same audit trail. No black boxes, no surprises. SOC-2 Type II, cloud native, API first.

1.5M+
Activities a month, in production
SOC-2
Type II
One
Audit trail across automated and human work

Trusted by regulated industries worldwide

SOC 2 Type II Cloud Native Enterprise Ready API First SSO Ready Audit Trail SOC 2 Type II Cloud Native Enterprise Ready API First SSO Ready Audit Trail
Two ways in

See it on your process, or see how the platform works.

If you want to see Kodexa on your business process, schedule a demo and we'll run it on documents that look like yours. If you want to see how the platform itself fits together, the Product page is where Knowledge, Workflow, and Studio live.

SOC-2 Type II · Enterprise Ready · One audit trail across the lot.