Platform

From reading text to understanding a page.

Generic OCR extracts characters into a disordered string. Our architecture extracts structured data while understanding hierarchy, tables, keys, values and the contextual nuances of Indian languages.

Output

What comes out the other side.

A structured document with its geometry intact — regions, reading order, coordinates and a confidence score on every claim. Not a wall of text.

receipt_hi_0412.jpg 3 regions · 1.4s
HEADING · 0.97
श्री बालाजी किराना भंडार
बागबहरा, महासमुंद, छत्तीसगढ़ · GSTIN 22AABCU9603R1ZX
TABLE · 0.88
चाय पत्ती — 500 ग्राम245.00
सरसों तेल — 1 लीटर178.50
आटा — 5 किलो210.00
कुल योग633.50
HANDWRITING · 0.61
प्राप्तकर्ता के हस्ताक्षर — 04/09/2026

Extracted fields

6 fields · 1 needs review · 1 flagged

merchant_name
श्री बालाजी किराना भंडार 0.97
gstin
22AABCU9603R1ZX 0.95
line_items
3 rows parsed 0.88
total_amount
₹ 633.50 0.99
date
2026-09-04 0.93
signature_block
प्राप्तकर्ता के हस्ताक्षर 0.61
The engine

Four stages, in order.

Each stage makes the next one more accurate — which is also to say that skipping one degrades everything after it. The sequence is the design.

Stage 01

Edge detection & preprocessing

On-device, native C++ / OpenCV

Contour detection locates the page. Affine homography transformation corrects perspective and skew. CLAHE — Contrast Limited Adaptive Histogram Equalization — normalises contrast locally rather than globally, which is what recovers a faded carbon copy photographed under a single tube light without blowing out the parts that were already legible. This stage runs before anything is read, and it is the largest single accuracy lever in the pipeline.

Stage 02

Layout segmentation & bounding

Spatial attention maps

The visual hierarchy of the page is identified — tables, header blocks, stamp seals, signature fields, key–value pairs and line-item grids — and a reading order is established across them. This runs before recognition, because knowing a block is a table column changes how its contents should be read. Flatten the page first and the structure that made it meaningful is already gone.

Stage 03

Indic multimodal transformer

Fine-tuned vision-language model

The recognition core. A vision-language transformer fine-tuned on Devanagari matras, half-characters, complex joint ligatures and mixed-code Hinglish — the constructions where engines built for Latin script produce character truncation and disordered output. Text is recovered together with its position, not as a flat stream stripped of geometry.

Stage 04

Semantic structuring & RAG

Normalised schemas + embeddings

Extracted blocks are normalised into typed JSON schemas — tax invoice, land record, KYC form — and vector embeddings are generated alongside them, so the same pass that digitises a document also makes it available to semantic search, automated accounting and downstream LLM analysis without a second extraction.

Document image → CLAHE clean → transformer attention → structured JSON + embeddings
Empirical precision

Benchmark results on real Indian documents.

Published accuracy in this category is usually measured on clean benchmark sets. Real documents are not clean, so ours are not measured that way.

99.4% Printed Hindi accuracy
Complex Devanagari ligatures on printed forms
Internal eval
86.8% Handwritten Indic accuracy
Field notes, doctor scripts, revenue signatures
Internal eval
100% Table layout fidelity
Multi-column headers and row-span preservation
Internal eval
<0.4s End-to-end latency
Standard 300 DPI page, single request
Internal eval
The eval set. 10,000+ authentic Indian documents — tax invoices, handwritten land records and degraded carbon copies, collected in the conditions the product actually meets. This is our own benchmark, not a public one. We publish it alongside the figures because an accuracy number without its document set is not a claim anyone can check.
Script

Why Devanagari is not Latin with different shapes.

Foreign scanning tools and cloud OCR APIs are trained almost exclusively on Latin typography and clean European invoices. The failures that follow are structural, not a matter of training-data volume.

क् + ष = क्ष

Conjuncts

Consonants combine into single ligatures with their own shapes. A segmenter that assumes one glyph is one character will cut these apart and read something else entirely.

कि की कु कृ कै

Matras

Vowel marks attach above, below, before and after the consonant they modify — sometimes drawn to the left of a character they are pronounced after. Position carries meaning.

शिरोरेखा

The shirorekha

The headline joining letters across a word defeats the whitespace segmentation Latin engines depend on. It has to be detected and reasoned about, not stripped away.

Devanagari is our first script, and mixed-code Hinglish is handled as a first-class case rather than an error state. The architecture is not specific to Devanagari — the same approach extends to the other major Indian scripts, and that is the intended path.

Deployment

Hybrid edge and cloud.

A document service from a hyperscaler is, by design, a reason to stay on that cloud. Portability is not in their interest. It is in ours.

01 / ON-DEVICE

Local inference

Capture, edge detection and CLAHE restoration run on the handset, with an offline scanning queue for the places where the network isn't. Nothing leaves the device until it has to.

02 / CLOUD

Batch at concurrency

High-concurrency GPU inference for enterprise batch jobs, with caching by content hash so an identical page is never processed twice.

03 / PRIVATE

Your VPC, or on-prem

The same container inside your own network boundary, or fully air-gapped — for land records, identity documents and anything that cannot lawfully leave the building.

Data posture

Zero raw-image retention.

These are Aadhaar forms, passbooks, land titles and medical records. The privacy design is part of the architecture, not a policy page written afterwards.

What we never store

No Aadhaar numbers, biometric scans, bank credentials or raw camera captures retained on our servers. Scanned images are processed in memory and purged. Aligned to India's Digital Personal Data Protection Act, 2023, with full user deletion controls.

What you control

Local offline scanning queue, one-tap history purge, direct device storage export, and no customer document used for training without an explicit agreement.

Bring us your worst document.

The faded carbon copy. The handwritten खसरा. The one your current tool quietly returns as empty. That is the one we want to see.

Pluton

Pluton Technologies (OPC) Private Limited.
Building India's document intelligence layer.

Registered office
Ward No. 2, Shantinagar, Bagbahra,
Mahasamund, Chhattisgarh 493449
India
support@plutontechnology.com +91 90542 37669
© 2026 Pluton Technologies (OPC) Private Limited. All rights reserved. DPDP Act 2023 aligned · Zero raw-image retention