What we are building, and what we are only researching.
Seven entries, each marked with where it actually stands. There are no dates on this page on purpose: a date published pre-launch is a promise made with somebody else’s calendar. Status changes as work does.
Meet the documents where they already arrive.
The first entry is the largest, so it gets shown rather than described. A document lands in a channel a team already uses, an intelligent triage decides whether it belongs in the pipeline, processing shapes it to that organisation’s rules, and the result is posted to the system that needed it.
The switchboard · illustration of an entry in design
Swipe to follow the line.
- Waiting for the first arrival. Tap a channel to send one.
Channel and destination names above are the ones this category integrates with most; none is shipped yet, and every run on the board is generated. Event-driven ingestion is the intended mechanism — object-created events, drive change feeds and folder subscriptions — rather than polling a bucket on a timer.
The book of entries.
Ordered by how much they change what the product is, not by when they land. Follow the trail down from what is live today; pick a waypoint to see that entry at work.
Today. Extraction that remembers is live; the trail starts here.
In design — Shape being decided
- Email inbox
- Object storage
- Shared drives
- SFTP drops
- Office scanners
- API
- Attachment triage
- Validate to your rules
- ERP · CRM · warehouse
- Webhooks
Planned — Committed, not started
- Watched folders
- Bulk directory runs
- Results beside source
- No upload step
- Air-gapped pairing
Planned — Committed, not started
- Camera capture
- Same pipeline
- Clear flagged fields
- Same governance
Planned — Committed, not started
- Record-event trigger
- Governed write-back
- Source attached
- Salesforce first
Planned — Committed, not started
- Chunking
- Embeddings
- Vector-store connectors
- Chunk provenance
- Chunk confidence
Planned — Committed, not started
- JPG to PDF
- PDF to JPG
- Split
- Merge
- Rotate
- Resize
- Compress
- No account
- In the browser
Research — May not ship
- Pixel edit detection
- Font mismatch
- Cloned regions
- Metadata conflicts
- Synthetic documents
Illustration of an entry in design · not built yet
Webhooks and integrations
In design— Shape being decided
Documents already arrive somewhere — an inbox, a bucket, a shared drive. The pipeline should meet them there instead of asking anyone to upload.
Connect the channels a team already uses, then let an intelligent triage decide which arrivals belong in the pipeline at all. What is routed gets processed, normalised and validated to your rules, and posted onward to the system that needed it. The plate above runs the whole path end to end.
- Ingestion
- Email, object storage, drives, SFTP, scanners, API
- Routing
- Attachment-level, so only what matters is processed
- Export
- ERP, CRM, warehouse, database, webhook
Need one of these sooner?
Design partners move the order of this list. If an entry here is the reason you cannot adopt yet, tell us and it stops being theoretical.