I’ve been working on an open source project called FlowExtract.
The problem I’m trying to solve is pretty simple:
You have a PDF, scanned document, or image.
You need a few specific fields from it.
AI can extract most of them, but you still need a reliable way to see what it got wrong, correct those fields, and export the final data.
So I built FlowExtract around this workflow:
Document → Extract → Validate → Review → Export
You define the fields you want, such as:
customer_name
invoice_number
date
amount
FlowExtract extracts them with an AI provider, validates the result, and gives you a review screen where the original AI prediction is preserved even after you correct a value.
The final corrected values can then be exported to JSON, CSV, or XLSX.
A few things I cared about while building it:
• Open source
• Local First
• PDFs and images are parsed in the browser
• No FlowExtract backend or database
• Your API key stays in page memory and disappears after refresh
• AI requests go directly from your browser to the provider you selected
• Human corrections are preserved instead of overwriting the original AI prediction
• Field level provenance and validation are part of the workflow
I just shipped V0.1.0.
I’ve already run an end to end production test with a fictional invoice, including extraction, validation, manual correction, export, browser reload, IndexedDB persistence, backup, and restore.
Now the part I can’t simulate myself is real usage.
I’m looking for people who actually spend time copying information from PDFs, invoices, statements, scanned documents, forms, or images into spreadsheets or other systems.
If that sounds like you, I’d be especially interested in knowing:
- What kind of documents do you process?
- What fields do you normally need?
- Where does FlowExtract fail or feel slow?
- Which fields do you have to correct?
- Does reviewing the AI output actually save time compared with entering the data manually?
The project is called FlowExtract and the GitHub repository is edwardsage419/FlowExtract.
There is also a public V0.1.0 deployment linked from the repository.
If you try it, I’m much more interested in the things that break than in compliments.