Features
The full list, with no plans in it.
Everything listed here exists in the product and is covered by automated tests. What does not exist yet is named at the bottom of the page rather than left out.
Documents
Upload and storage
The file's type is determined from its bytes, not from its name.
Reading, page by page
The PDF's own text where it exists, character recognition otherwise, with French and Arabic.
Recognising the document kind
Invoice, purchase order, contract, or one of the kinds you defined.
Capturing information
Amounts stay as printed, dates are normalised, what is absent stays empty.
Source page
Every value keeps the page it was taken from.
Corrections
What you correct is kept beside the original proposal, not in place of it.
Document centre
Kind, counterparty, amount, status and who uploaded it, with business-language filters.
Review screen
The document on one side, the captured information on the other, each marked captured, needs checking, or not found.
Information to capture
Three built-in kinds
Invoice, purchase order and contract work from the first upload.
Your own kinds
Describe in plain language what you want captured, field by field.
Six field types
Text, number, money, date, yes/no and list.
Fields a person must check
Mark a field as one that has to be checked by a person before any approval.
Protected deletion
A kind used by past documents cannot be deleted; it can be disabled.
Automations and approvals
Rules in business language
When, if, then, otherwise — read back as a sentence before being saved.
Templates
Four templates build a working rule from two questions.
Shadowed rules flagged
A rule another will always beat to the match is pointed out to you.
Approvals inbox
Grouped in three: for you, for someone else, already decided.
Findings in the open
A possible duplicate appears on the decision card, not in a log.
Decisions on the record
Approve or decline with a note; the author and the date are kept.
What follows a decision
Notify another system, or record an internal event.
Knowledge and assistants
Questions about your documents
Streamed answers, with the sources shown before the first word.
Refusing to guess
With no relevant document, no model is called and the absence is stated.
Permissions inside the search
Permissions filter the search itself, never its results after the fact.
Citations you can open
An extract does not cross a page, so every citation leads somewhere you can look.
Knowledge base
Notes you type or documents already processed, with access by role.
AI Assistants
Standing instructions, with capabilities chosen from a list of what can actually be carried out.
Real trial run
A trial against the real model, from the configuration screen.
Runs recorded
Duration and estimated cost of every run; a failure is a failure, never a substitute answer.
AI quality
Test case sets
A fixed set of cases, run against one pinned model, so a score belongs to that model.
Two kinds of case
A free-text answer, or capturing information from text the case carries itself.
Three ways to grade
Exact match, contains, or judged by a model.
Errors count as failures
A case that errors is not skipped: it is graded as failed.
Team, access and languages
Seven roles
Each described from the permission table, including where the answer is uncomfortable.
Invitations
A public page to join the organization; revoke, change role, remove.
Two-factor authentication
TOTP, with single-use recovery codes.
Sessions
The list of your open sessions, revocable immediately on the server.
Three languages
French, English and Arabic, with a full right-to-left layout.
Light and dark
Verified against WCAG 2.1 AA in all three languages and both themes.
Tracking, reports and cost
Reports
Documents processed, approvals requested and decided, average time, over 7, 30 or 90 days.
A shareable window
The period lives in the address, so a figure can be passed on as it is.
AI usage
What the AI cost, per day and per use, computed from the provider's published rates.
A cost stated as an estimate
Never presented as an invoice, because it is not one.
Notifications
In the application, with preferences per kind of event.
Background watching
Stuck work, a provider failing repeatedly, a budget approached, a broken integration.
Outbound connections
A signed message
After a decision, Intelliflow notifies a web address you provide.
Signed over the bytes sent
HMAC-SHA256 over the exact message, with the timestamp inside what is signed.
Protection against internal addresses
Every resolved address is checked, IP literals included.
Delivery history
Response status, latency and errors, all kept.
Security and traceability
Isolation by the database
Every customer-data table carries a policy enforced even against the owner of the table.
Audit trail
Update and delete rights are withdrawn from the application account.
Secrets out of the browser
AI provider keys never leave the server.
Encryption at rest
Sensitive stored values are encrypted with a key derived per use.
Rate limiting
On sensitive routes, against repeated attempts.
What does not exist yet
We would rather you read it here than find out afterwards.
- No connector to any named accounting package, CRM or storage service.
- No public API and no API keys for customers.
- No email sending configured: an invitation produces a link you share yourself.
- No mobile app. The web application works on a phone.
- No single sign-on (SSO, SAML, OIDC).
- No visual drag-and-drop workflow builder.
- No folders or tags on documents.
- No online billing: no payment provider is connected.