What is real here
Classification, field extraction, line-item parsing, arithmetic reconciliation, duplicate detection, rule evaluation, routing, the approval checkpoint, and the execution log. The timings shown are measured, not decorative.
Cognitaski Studio
Run a real back-office workflow, right here.
Studio is the Cognitaski workflow engine, running in this page. Paste a document or open a sample, and it will classify it, extract the fields, check the arithmetic, evaluate your business rules, decide where the work goes, and hold it for approval when your policy says it should. No account, no waitlist, no sales call.
Live nowNo sign-upRuns in your browserNothing is uploaded
Incoming document
812 charsSupplier invoice
Business rules
4 activeThese are the policies the engine evaluates. Change a threshold or add a rule and run the document again — the result updates because the rules below are the ones actually executed.
Total is greater than 5000 → Finance approver
Currency does not equal USD → Currency review
PO number is missing → No purchase order matched
Priority equals high → Priority support queue
Decision
no run yetChoose a sample or paste your own document, then select Run workflow. The decision, the fields behind it, and the full execution log appear here.
Extracted fields
Fields the engine locates — document number, dates, currency, counterparty, totals — are listed here with how each one was found.
Execution log
Every stage records what it did, what it produced, and how long it took. Run a document to see the trace.
Run history
0 stored on this deviceCompleted runs are kept in this browser so you can compare them. They are never sent anywhere, and clearing your site data removes them.
What you just ran
The same engine, without the plumbing.
Studio is deliberately honest about its boundaries, because an automation tool that overstates what it does is worse than no tool at all.
How extraction works
Studio uses deterministic labelled-pattern and layout matching, not a language model. The same document always produces the same result, and every value shows the evidence it came from. That is why it runs offline in a browser tab.
What we set up with you
Connecting a workflow to your own mailboxes, ERP, ticketing, and databases — and running it on a schedule against live traffic — is the part we configure together. Studio is the engine; the integrations are the install.
Your data
Studio processes documents entirely inside your browser tab. The text you paste is never transmitted to Cognitaski or to any third party, there is no analytics call attached to a run, and run history is held in your browser’s local storage until you clear it. You can verify this in your browser’s network inspector — running a document produces no outbound request.