EU processing, on request

EU-only processing
for openparser.

openparser runs in AWS US regions today. We are preparing an EU deployment where your documents, results, and OCR models stay in EU regions. If you need this, tell us your volume and requirements and we will set you up first.

Talk to us about EU processing Read the API docs

Separate EU stackSelf-hosted optionSame API and SDKs

Switch with one setting

The EU deployment we are preparing is a separate stack with its own API host. The SDKs and CLI already accept a base URL, so your integration code stays the same.

environment

# Today
export OPENPARSER_BASE_URL=https://api.openparser.dev

# EU deployment (when your workspace is set up)
export OPENPARSER_BASE_URL=https://api.eu.openparser.dev

01
A separate EU stack
Its own API host, database, storage, and OCR GPUs in EU regions. EU requests are not routed through the US deployment.
02
Keys bound to a region
You choose EU when the workspace is created. Its API keys only work on the EU host.
03
An EU-only model list
GET /models on the EU host lists only OCR engines that run in the EU, with each one’s region and provider. Anything else returns a clear error, never a silent fallback.

Parse, Extract, Lineage

Parse

POST /parse

PDF or imageelements + markdown

open-weight hosted, from

$1/ 1,000 pages

Compare OCR prices

Extract

POST /extract

parse + JSON schematyped JSON

no per-document fee

Per tokenat your chosen model’s rate

Extraction API

Lineage

grounding: "field"

extracted fieldsource region + history

with every grounded extract

$0included

Explore lineage

EU processing FAQ

Where documents run today, what the EU deployment changes, and self-hosting.

Where does openparser process documents today?

The hosted API, workers, document storage, and open-weight OCR GPUs run in AWS US regions, with backups replicated to a second US region. Cloud OCR engines such as Google Document AI and AWS Textract run in US regions.

When will EU processing be available?

We set up the EU deployment for the teams who ask for it first. Book a call, tell us your page volume and requirements, and we will give you a date.

Which OCR models will run in the EU?

Open-weight PaddleOCR-VL on our own GPUs in an EU region, plus cloud engines that offer EU regions, such as Google Document AI, AWS Textract, and Azure Document Intelligence. The EU host lists only engines that run in the EU.

Can I run openparser inside my own infrastructure?

Yes, on request. We deploy openparser self-hosted for regulated teams, in your own cloud or data centre, with open-weight OCR running on your GPUs. Tell us your setup and we will scope it with you.

Is openparser GDPR compliant?

Compliance depends on how you use a service, not on the service alone. Before the EU deployment goes live we will publish the sub-processor list with regions, a DPA, and a written retention rule, so you can assess it for your GDPR or DORA obligations.

Tell us what you need in the EU

Company, country, pages per month, and whether you need an EU region or a self-hosted deployment. We will set you up first.

Talk to us about EU processing Try the US API now

EU-only processing
for openparser.

What EU processing includes