Kodexa
ContactSchedule Demo
The Product How Kodexa runs your business processes

Knowledge first.
Workflow that runs it.
All designed in Studio.

Three surfaces of one workflow. Agents draft the routine pieces; your team reviews and binds.

Schedule a Demo See Solutions
Knowledge

The rules your team already applies. Captured.

Customer-level and vendor-level rules captured by the workflow as it runs. Reviewable, editable, customer-owned, model-portable. The Library is where the rules live and where your team edits them.

  • Customer- and vendor-grain rules
  • Reviewable and editable, like spreadsheet formulas your team owns
  • Tenant-isolated, never crosses customers
  • Foundation models change; the layer stays
Go to Knowledge
Knowledge / Library · Vendor: Northwind Foods
PO number in comments, not header
M. Chen · 4d ago · 1.2k docs
Tax line is VAT_RECOVERED
Freight on every invoice ≥ $5,000
Agent proposal · Group line items by ship-to
Workflow

Where Activities run and Tasks land.

The runtime. Activities show their live state. Tasks queue up for the right person with context attached. Exceptions get reviewed by your team or worked by an agent. One audit trail across all of it.

  • Tasks land in the right person's queue, with document and system context
  • Activities show live state, step by step
  • Agents work routine exceptions; humans handle judgment
  • One audit trail across automated and human work
Go to Workflow
Workflow · AP-Intake ● Running
Tasks (12)
Covenant review
Northwind · 4m
Three-way mismatch
Acme · 12m
Maker review
Stark · 18m
INGEST Email watcher · 312ms
API GET /vendors/v3 · 187ms
AGENT Classify · 0.97 conf
AGENT Extract fields · running
DECIDE conf ≥ 0.85 ?
TASK Maker review (if <)
API POST /erp/invoice
Studio

The platform configures the platform.

Where Activity Plans, Task Templates, validations, and document models are authored. Agents draft the routine pieces from a use-case description; your team handles the judgment calls. Test before you bind.

  • Compose Activity Plans as a typed graph of Steps
  • Author Task Templates that match how your team works
  • Agents draft the routine plans for your team to review
  • Test against real documents before binding to a project
Go to Studio
Studio / Activity Plans / AP-Intake-v3 ● Validated · 14 tests
Plan graph
INGEST Email watcher
API GET /vendors/v3
AGENT Extract fields Agent draft
DECIDE conf ≥ 0.85 ?
API Post · ERP
TASK Maker review
Inspector — Extract fields
Model claude-haiku-4-5 · temp 0
Task template (on exception) vendor_review_v2
in doc, vendor_rules
out {fields, confidence, exceptions[]}
Validations · 4
total = subtotal + tax
vendor ∈ approved_list
currency = USD | EUR
12/14 · last run 4m ago Bind
The shape

One workflow, three product surfaces, agents threaded through.

Studio is where you author. Workflow is where the work runs. Knowledge is where what your team learns persists. Agents work in all three: drafting in Studio, working exceptions in Workflow, proposing rules in Knowledge. None of them act without human review.

Studio where you author agent drafts plans Workflow where the work runs agents work exceptions Knowledge where it persists agents propose rules authors captures feeds back

Authored in Studio. Run in Workflow. Captured in Knowledge. Knowledge feeds back into Studio when rules and Plans are edited together.

1.5M+
Activities a month, in production
SOC-2
Type II
One
Audit trail across the lot

Live in production at regulated-industry customers in banking, specialty lending, and AP.

See the product on your process.

A demo runs on documents that look like yours. We'll show all three surfaces working together against a real Activity Plan.

Schedule a Demo Contact Sales