Document infrastructure

Documents in. Structured data out.

OCR infrastructure for images, PDFs and office documents, deployed where your data already lives.

Tax invoiceReading the pagesupplierNametotaltaxAmount{"supplierName": "…","total": 1200000,"taxAmount": 120000,"confidence": 0.98,"warnings": []}Structured result

One call, and evidence you can use.

Post a document and read text, fields, confidence and warnings back in one stable response.

curl https://api.getvisionlinq.app/v1/jobs \
  -H "Authorization: Bearer $VISIONLINQ_API_KEY" \
  -F [email protected] \
  -F schema=kr-receipt
{
  "structured": { "fields": { "total": {
    "value": 12000,
    "status": "found",
    "confidence": 0.9,
    "evidence": ["page:1:line:1"]
  } } },
  "processing": { "mode": "balanced", "pages": 1 },
  "warnings": []
}
  • every value carries coordinates, confidence and its source page
  • schema pack v1: receipts · tax invoices · general contracts
  • document bytes and extracted text never enter the database or logs

Keep the system of record.

Authorized documents move through processing inside the retention and delivery boundaries of the deployment mode you choose.

  1. Your storage

    Your object store can remain the source and destination of record.

  2. VisionLinq processing

    The requested pipeline reads authorized sources and applies the configured retention policy.

  3. Your application

    A stable response returns text, evidence, fields, metadata and warnings.

Designed for Korean document workflows.

Start with the approved schema pack, then widen coverage through explicit versioned releases.

Initial schema pack

  • ReceiptsmerchantName · total · transactionTimestamp
  • Korean tax invoicessupplierName · recipientName · taxAmount
  • General contractsparties · term · paymentObligations

Planned coverage

  • Business registrations
  • Application forms
  • Certificates

Deployment follows the data boundary.

Choose the operating model that matches your infrastructure, procurement and isolation requirements.

Cloud hosting

The managed service runs on our cloud infrastructure. Regional controls are documented according to actual availability.

available

Bring your own cloud

Packaged infrastructure for AWS, Google Cloud and Azure through supported delivery channels.

plannedRequest access

On-premise

An isolated edition for controlled environments, subject to an enterprise agreement and a supported platform matrix.

plannedRequest access

Security starts with clear boundaries.

Deployment, storage, retention and metadata behaviour stay explicit, so your team can evaluate the controls that exist today.

  1. Customer owned storage

    Where the delivery mode permits, sources and results stay in storage you own, with configurable retention for processing artifacts.

    Read the security boundary
  2. Bounded execution and tenant isolation

    Documented regional execution boundaries and tenant isolation apply to the selected deployment mode.

    Read the security boundary
  3. Protected metadata

    Protected data is encrypted, and document bytes and extracted values stay out of the database and operational logs.

    Read the security boundary

Request access

Tell us which documents you process and which deployment you need.

Required fields are marked with an asterisk.

Use the address you use for work.
Preferred deployment
Document categories
Describe document types, integration needs, or deployment constraints.