Bring it in
The macOS uploader sends original file bytes to an authenticated intake. Hash verification and idempotency make retries safe.
authenticated intakeA paperless office system for people who care where things land
Paperwork in.
Order out.
Paperline gives every document a deliberate path from intake to filing — with the source kept intact, the decisions recorded, and a human in the loop when confidence is low.
IN
Ready to fileroute recorded
originaloutbox
The workflow
A straight line from a messy desk to the right destination.
Paperline separates the act of receiving a document from the decision about where it belongs. That makes the path inspectable, retryable, and ready for an agent or a person to finish.
Make the path
An ordered chain attests, validates, deduplicates, extracts what it can, applies rules, names the document, and creates a route.
bubble pipelineFile with proof
Routing creates a durable outbox item. An authorized agent can claim it, file it, and leave an audit trail of the result.
outbox + auditThe Paperline difference
Automation you can inspect.
The point is not to hide work behind a magic button. It is to make routine filing predictable while preserving the context you need when something deserves a second look.
Originals stay original
Uploads are stored immutably. Transforming a document creates a new object; the source is never quietly rewritten.
Routing is a decision, not a side effect
A route becomes an outbox item instead of writing straight into a store. That gives filing retries, claims, and confirmations a clear boundary.
Low confidence has somewhere to go
Configured approval policies can hold uncertain targets for triage. Corrections are recorded without changing the original upload.
A calm core
Start with Cloudflare.
Add capability as needed.
Paperline’s core is built around Workers, R2, Queues, and Durable Objects. Optional OCR and extraction services plug into the same pipeline; they are not required to define the system.
CORE
Cloudflare Workers · R2 · Queues · Durable ObjectsServerless foundation
OPTIONAL
OCR · structured extraction · agent toolingProgressive capability, explicit configuration
The honest status
What Paperline can do today
This site describes the current repository implementation, not a promise about a future tier. The working slice includes authenticated uploads, immutable staging, extraction fallback to an agent-triage outbox, deterministic Evernote routing, filing leases, approvals, and an admin/triage console.
Implemented path
Upload → stage → process → route → agent filing
Optional path
OCR and OpenRouter extraction when explicitly configured
Less filing. More knowing.
Give every document
a line to follow.
Paperline is being built for the office where “I’ll file it later” stops being a workflow.
Read the implementation