Every document.One timeline.Its own date.
FlowDox files each document under a flow number and stands it on that flow's timeline at the date on its face — issue date, signing date, effective date — never the day somebody uploaded it. Open a contract and you see its whole history, not a folder.
Dropped today, dated 4 September — it lands in September, not today.
See it work
Six things FlowDox does, shown moving. Every card, figure and date is the demo company's own.
Time is the axis
A flow is anything worth keeping a file on — a contract, a project, a tender. Everything on it sits on one spine in date order: incoming on the left, outgoing on the right, a quiet month folded into a gap marker. The file number is the organising principle; time is the axis.
Drop it. It is read.
Drop a PDF, a Word or Excel file, a photo or a scan. FlowDox hashes it, reads its text and proposes a type. With reading switched on, it reads the fields, the parties and the date off the page — every value with the line it came from, and nothing the page does not say.
A record you can stand behind
Originals go straight from the browser into locked storage that FlowDox's own credentials cannot delete from. Every file is hashed, every change is in an append-only activity log, and any past date can be replayed exactly as it stood.
Nothing was typed into a task list — the loops come from the documents themselves.
The Brief knows what is open
An invoice with a due date, a letter that asked for a reply, a bulletin with a deadline: each creates an expectation the moment it is filed. The Brief lists what has fallen due — overdue, due soon, waiting — worked out from the documents on the flow, with the day count and the document it came from. Nobody maintains a task list; the list is the paperwork.
- A flow timeline: our email of 14 April, "Missing items on DN-4402", on the outgoing side; INV-2026-201 for €120,000.00, due 1 August, on the incoming side. The Brief below is empty.
- Today is moved from 24 July to 6 September. As it passes 1 August the payment plan turns overdue and the invoice card is marked OVERDUE.
- The Brief derives an open loop: OVERDUE · INV-2026-201 · €120,000.00 unpaid · due 1 Aug · no Payment Advice filed — and the counter ticks from 3 to 36 days overdue as Today reaches 6 September.
- A second loop follows: DUE SOON · SB V400-53-4123 rev 2 compliance by 30 Sep · filed 9 Mar · 24 days left.
- And a third: WAITING · Missing items on DN-4402 — no reply · our email 14 Apr · 145 days.
- Nothing was typed into a task list — the loops come from the documents themselves.
Contract, invoices, payments — each figure is derived from a document on the timeline, never typed in.
Money, reconciled from the flow
The contract sets the value. Each invoice raises what has been invoiced; each payment advice settles what is outstanding; a variation order moves the contract itself. The five figures on the Money tab are derived from those documents at whatever date you are looking at — in each document's own currency, with the exchange-rate effect shown separately.
- The Money tiles read Contract value €2,400,000.00, Invoiced €0.00, Paid €0.00, Outstanding €0.00 and Still to invoice €2,400,000.00 — the contract, signed 3 February 2026, is the only document on the spine.
- Invoice INV-2026-118 for €48,300.00 lands on the incoming side at 12 March; a chain draws from the contract to the invoice.
- Invoiced ticks to €48,300.00, Outstanding opens at €48,300.00, and Still to invoice falls to €2,351,700.00.
- Payment Advice PA-0231 for €48,300.00, marked paid, lands on the outgoing side at 18 March; the chain draws on from the invoice to the payment.
- Paid ticks to €48,300.00 and Outstanding returns to €0.00.
- Variation Order 1 for +€85,000.00, signed 15 July, lands; a chain draws from the amendment back to the contract.
- Contract value ticks to €2,485,000.00 and Still to invoice to €2,436,700.00 — every figure is derived from a document on the timeline, never typed in.
Drop a file on its card: the next version, at its own date, and the old one stays on the spine as a ghost.
Versions, and what changed
Drop a file on a document's card and it becomes the next version. The card moves to the new version's own date; the old one stays on the spine as a ghost, so the history is still there to see. Compare any two versions and the difference is of the documents' own text — the line that was removed, the line that was added, the fact that changed.
- The stress report “Cargo door surround — stress”, SR-V400-53-002 rev A, sits on the flow at 8 July 2026 as version 1.
- A file is dropped onto its card.
- The card becomes version 2, rev B, and moves down the spine to 15 July 2026 — the new version's own date.
- At the old row a dashed, struck-through ghost stays: v1 · rev A → v2 · 15 Jul 2026.
- A compare panel opens beside it: v1 rev A against v2 rev B — one line removed, one added, one changed; +0 pages.
Every file is hashed before anything else — the same bytes are linked, whatever the file is called.
The same file is never filed twice
Before anything else, every file is hashed with SHA-256 in your browser. If the same bytes are already on a flow in your company, FlowDox shows you where and offers to link the existing card rather than file a copy — whatever the file happens to be called. A file with the same name but different bytes is offered as a question, not assumed.
- A file named INV-2026-201 (1).pdf is dropped onto the flow, where the invoice INV-2026-201 for €120,000.00 has been filed since 2 July 2026.
- Before anything else the file is hashed: sha256-a561f9b1b4d78df2…
- The checksum matches the existing card: the same bytes are already on this flow.
- FlowDox says "Already here — the same bytes are on this flow as INV-2026-201, 2 Jul 2026" and offers two choices: Show that card here, or Skip.
- The dropped file is not stored again; the existing card simply gains a "⧉ linked" chip. No second card appears.
What is read off a letterhead fills the blanks in the register — and says which document it came from.
A registry that learns from the documents
When FlowDox reads a letterhead it finds the company: legal name, address, phone, VAT number. A company the register does not know is added; a known one has its blanks filled. Every learned detail carries the document it was read from, and a value a person typed is never overwritten. The register grows from the paperwork, one document at a time.
- An incoming letter from NSB GmbH is filed: NSB-2026-0412, “Confirmation of inspection date”, 2 September 2026. The register's row for NSB GmbH holds only what a person typed — the code NSB — and its 61 documents; legal name, address, phone and VAT are blank.
- FlowDox reads the letterhead. Three fields appear beside the page: legal name NSB Nordstern Systembau GmbH, address Hafenstraße 12, 20457 Hamburg, phone +49 40 1234 5678.
- Each value moves into its empty cell in the register, and under each cell a line says where it came from: read from NSB-2026-0412.
- The typed code NSB carries a lock and does not change — a value read from a document never overwrites what a person recorded. The VAT number stays blank: the letterhead did not give one.
Pick a day and the flow, the Brief and the Money are exactly as they stood — nothing is stored, everything is derived.
As of any day
Pick a day and the flow shows itself as it stood: documents dated later disappear, the Brief's open loops and the Money figures are recomputed for that day, and the view is tinted so nobody mistakes it for today. None of it is stored — everything on the timeline is derived, so any past date can be reproduced exactly.
- The flow as it stands today, 6 September 2026: PO-0088, three invoices from NSB GmbH and Variation Order 1 on the spine; €488,300.00 invoiced, €368,300.00 paid.
- The date scrubber is dragged back from 6 September to 1 April 2026.
- As it passes each date, the documents filed after it fade: Variation Order 1 of 15 July, INV-2026-201 of 2 July, INV-2026-140 of 7 April.
- The Today pill becomes As of · 1 Apr 2026 and the Money tiles restate: €48,300.00 invoiced, €48,300.00 paid — only INV-2026-118 and its payment existed that day.
- Nothing was stored for that day; the view is derived from the documents and their dates.
What it does
Only things that work today.
- 01
Flow numbers
Issued by the database, one at a time, never reused. A deleted flow's number stays spent.
- 02
Its own date
A document stands on the spine at its issue, signing or effective date — never the upload date.
- 03
Read off the page
Type, fields, summary, parties and date come off the page. Every value quotes its line, or it is discarded.
- 04
Any file
PDF, Word, Excel, PowerPoint, text, photos and scans. OCR runs in your browser; the page never leaves it.
- 05
Duplicates by bytes
Every file is hashed with SHA-256. The same file is linked, not filed twice — whatever it is called.
- 06
Versions and compare
Drop a file on its card for the next version. The comparison is of the two documents' own text.
- 07
The Brief
Open loops derived from the documents: an unpaid invoice, an unanswered letter, a deadline in a bulletin.
- 08
Money
Contract, invoices, payments — reconciled at any date, each document in its own currency.
- 09
Plans
Expected payment, delivery or reply. When the document arrives, the plan is realised — early, late or short.
- 10
A registry that learns
Companies and people. A detail read off a page carries the document it came from; typed values are never overwritten.
- 11
As-of
Pick a past date and see the flow, the Brief and the Money exactly as they stood.
- 12
Access and audit
No view, View, Print or Edit — per workspace, project or flow. An append-only activity log for admins.
How it works
Open a flow
A number of your own: your company, workspace, project or category, and a counter or the contract reference. Issued once, never reused.
Drop what arrives
PDFs, Office files, photos, scans. FlowDox hashes each one first, so a file you already have is linked, not filed again.
Let it be read
The type, the fields, a summary, the parties and the date come off the page. You check them before filing; nothing is filled in that the page does not say.
Read the flow
The timeline, the Brief's open loops, Money from contract to payments, versions side by side — as of today or any day before.
Where it runs
- Built for companies anywhere: any currency, any time zone, any language of paperwork.
- Originals never pass through the app server. Your browser uploads straight to storage on a link signed for that one upload.
- Stored originals are locked: FlowDox's own credentials have no permission to delete them.
- Reading sends a document's text, never the file — and only when your administrator switches it on.
- Each company's data is kept apart by row-level security on every query, whatever the application code does.
- More than 1,500 automated tests, including tests against a real database.
Built for
- Any company that runs on contracts, orders and correspondence
- Any project, from the first quotation to the last payment
- Any team that has to answer what came in, when, and what is still open
Prices
Per user per month, excluding VAT. Annual billing is ten months for twelve. Every plan reads documents.
Free
- Users
- Up to 3 users
- Reads
- 50 reads a month
- Storage
- 1 GB
- Timeline at the document's date
- Reading off the page
- Versions and compare
- Duplicates by bytes
- Registry
Starter
- Users
- 3 to 15 users
- Reads
- 30 reads per user a month
- Storage
- 5 GB per user
- Everything in Free
- Plans: expected payment, delivery, reply
- Money: contract to payments
- Project budget and commitments
- Recycle bin, 30 days
Team
Most chosen- Users
- 3 to 100 users
- Reads
- 60 reads per user a month
- Storage
- 20 GB per user
- Everything in Starter
- Access levels per workspace, project or flow
- Approval workflows and a signature queue
- Activity log for admins
- Recycle bin, 90 days; keep documents after a flow closes
Business
- Users
- 10 to 500 users
- Reads
- 100 reads per user a month
- Storage
- 50 GB per user
- Everything in Team
- Retention windows you set
- Invoice billing on annual plans
- Priority support
Enterprise
- Users
- 100 users and up
- Reads
- Read pools to fit
- Storage
- To fit
- Everything in Business
- Contract and data-processing agreement
- Onboarding of your document control
A read is one document of up to about 50 pages, measured by the text sent. Filing and storing never count; only reading does. Extra reads are €0.12 each on every paid plan.
- What counts as a read?
- One document being read — automatically when it is filed, or when you ask again. About 50 pages of text is one read; a longer document counts as more. Filing, storing, previewing, comparing and searching never count.
- What happens when the reads run out?
- Nothing is lost. The document is filed, on the timeline and previewable; its fields, summary and parties wait until the next month or until you buy extra reads at €0.12 each. On Free, reading pauses until the next month.
- Annual or monthly?
- Annual is ten months for twelve and is billed once a year; monthly can be cancelled any month. Overage is always billed monthly in arrears.
- Tax and currency
- Prices are shown in euros and exclude tax. The tax that applies to your business, if any, is added on the invoice.
Help
The questions people ask first.
What is a flow?
Anything worth keeping a file on: a contract, a project, a tender, a supplier, a work item. It gets a number — issued once, never reused — and everything about it sits on one timeline.
What can I drop?
PDFs, Word, Excel and PowerPoint files, plain text, photos and scans. Text is read in your browser; a scan can be OCR'd there too, so the page never leaves your machine. Pictures can be read too.
What is read, and where does my document go?
Reading sends the document's text — never the file — and returns the type, the fields, a short summary, the parties and the date. Every value must quote the line it came from, or FlowDox discards it. Reading is off until your administrator switches it on.
Where is my data?
In one system run by FlowDox: the application, the database and the originals. Originals go straight from your browser to locked storage and are never routed through the app server, and FlowDox's own credentials cannot delete them.
Can a document be deleted?
A document can be removed into a recycle bin and restored within your retention window. The stored original is never deleted by FlowDox — its credentials cannot. An admin can delete a whole flow with a typed confirmation; its number stays spent.
How do versions work?
Drop a file onto a document's card and it becomes the next version. The card moves to the new version's own date; the old one stays on the spine as a ghost. Compare shows the two versions' own text side by side.
What about duplicates?
Every file is hashed with SHA-256 before anything else. If you already have the same bytes, FlowDox shows you where and links it rather than filing it twice. A file with the same name but different bytes is offered as a question, not assumed.
Can my counterparty see the flow?
You can preview a flow as the counterparty would see it — internal notes, plans, Brief and Money hidden. Inviting a counterparty to view it themselves is not built yet.
Can I email documents in, or file from my phone?
Not yet. Today documents come in through the browser: drop, paste or browse. FlowDox works in a phone's browser; a phone app and email-in are on the list, and we say so rather than promise a date.
What about the documents I already have?
Drop them. Each one is dated from its own page — a contract signed in February lands in February however long it sat in an inbox — so a year of history files into the timeline it belongs on.
Support
A person answers.
Write to support@flowdox.app with the flow number and, if it is about a document, its title. We aim to reply within one working day, wherever you are. Business and Enterprise plans have priority.
Found something wrong? Say what you expected and what you saw — a screenshot helps.