Docen
PLATFORM

Everything you need to turn documents into data.

Five processors, a playground to try them, managed batch for scale, and deployment options that keep your data where it belongs.

[P0]PLAYGROUND

Try it on a real page.

Drop in a document or pick an example, then switch between Markdown, HTML, and structured JSON.

DOCEN PLAYGROUNDRun
INPUT
Drop a PDF, image, or scanChoose file
EXAMPLES
# Invoice DX-40218

**Bill to:** Northwind Supply Co.
**Date:** 2026-05-14  **Due:** 2026-06-13

| Item            | Qty | Unit    | Amount     |
| --------------- | --- | ------- | ---------- |
| Filtration unit | 4   | $2,150  | $8,600.00  |
| Service, on-site| 12h | $145    | $1,740.00  |

**Total due:** $18,204.50
CONFIDENCE0.991
[P1]PROCESSORS

Five models, composable into one pipeline.

P · 01Parsing

Docen Parse

The core parsing model. It reads a document the way a person would — top to bottom, column by column — and returns clean Markdown, HTML, or JSON with the layout intact.

  • Reading order across columns and pages
  • Tables preserved as structured cells
  • Math, code, and lists kept faithful
  • One call from file to clean text
parse → markdown
# Quarterly Report

| Metric | Q1 | Q2 |
| --- | --- | --- |
| Revenue | 4.1 | 4.8 |
P · 02Recognition

Docen OCR

High-fidelity text recognition tuned for the hard cases: faint scans, handwriting, dense multilingual pages, and heavy mathematical notation.

  • 90+ languages and mixed scripts
  • Word-level bounding boxes
  • Per-token confidence scores
  • Handwriting and historical type
ocr → tokens
{ "text": "Indenture", "conf": 0.99 }
{ "text": "of", "conf": 0.99 }
{ "text": "Grant", "conf": 0.98 }
P · 03Structure

Docen Layout

Detects regions, tables, and section hierarchy, and keeps them aligned across long documents so the structure holds together end to end.

  • Region and table detection
  • Section hierarchy across pages
  • Figure and caption pairing
  • Stable across hundreds of pages
layout → tree
§ 1 Introduction
  ├─ 1.1 Background
  └─ 1.2 Scope
§ 2 Methods
  └─ Figure 1
P · 04Extraction

Docen Extract

Schema-driven extraction. Describe the fields you need and Docen returns them as structured data, each with a citation back to the exact source span.

  • Bring your own JSON schema
  • Citations to page and span
  • Balanced and high-recall modes
  • Long-document handling
extract → fields
{ "total_due": "$18,204.50",
  "cite": { "page": 1, "span": [412, 423] },
  "conf": 0.99 }
P · 05Evaluation

Docen Eval

An evaluation harness that scores parsing and extraction against your own labeled documents, so you can catch regressions before they reach production.

  • Score against your labels
  • Per-field and per-type metrics
  • Regression tracking over time
  • Exportable reports
eval → report
field       f1     Δ
total_due   0.99  +0.01
vendor      0.97   0.00
date        0.98  +0.02
[P2]MANAGED BATCH·SCALE

Run the whole queue.

Send a backlog and get structured output back, with throughput that scales to the work in front of it.

Point Docen at a queue and walk away.

Managed batch takes a backlog of documents and runs it end to end. Throughput scales up when the queue is deep and settles back down when it drains, so you pay for the work rather than idle capacity.

  • Per-document status and structured output
  • Automatic retries and back-pressure
  • Millions of pages without standing infrastructure
Read about managed batch
01
Queue
02
Route
03
Process
04
Structure
05
Deliver
[P3]BENCHMARKS·PUBLIC

The numbers we hold ourselves to.

HOW WE MEASURE
BM · CER↓ better
0.42%

Character error rate on scanned pages

Docen OCR0.42%
Baseline OCR3.10%
BM · TABLE↑ better
98.7%

Table-cell accuracy on complex layouts

Docen API98.7%
Open parser91.4%
BM · EXTRACT↑ better
94.3%

Field-level F1 on schema extraction

Docen Extract94.3%
Prompt-only82.0%
BM · LATENCY↓ better
~2.1s

Median processing time per page

Docen API~2.1s
Self-host baseline~6.4s
[P4]MIGRATE·DROP-IN

Migrate to Docen without a rewrite.

Point your pipeline at the Docen API and keep the output format you already parse. Most teams switch one endpoint and compare results side by side.

01

Swap the endpoint

Replace your current parser or OCR call with a single Docen API request. Same file in, cleaner structure out.

02

Compare on your docs

Run both in parallel and use Docen Eval to measure the difference on the documents you actually process.

03

Cut over when ready

Move traffic on your schedule. Keep the same output format, so nothing downstream has to change.

[P5]DEPLOYMENT·MODES

Deploy where your data has to live.

D · 01

Managed Cloud

The fastest way to start. Send documents to the Docen API and get structured output back, with capacity that scales with your queue.

  • No infrastructure to run
  • Usage-based pricing
  • Regional processing options
D · 02

VPC Deployment

Run Docen inside your own cloud account. Documents stay within your network boundary while you use the same models and outputs.

  • Runs in your VPC
  • Your keys, your logs
  • Private networking
D · 03

On-prem · Air-gapped

Deploy to hardware you control, including fully offline environments. Built for teams with strict data-residency requirements.

  • Offline-capable images
  • Data never leaves the host
  • Hardware-flexible
[09]START

Process document queueswithout infrastructure.

Start on the API in minutes, or bring Docen into your own environment. Same models, same structured output, at whatever scale you run.