huggingface.co web signal

ATH-MaaS's OvisOCR2 tops OmniDocBench at 0.9B params

TL;DR

  • ATH-MaaS released OvisOCR2, a 0.9B end-to-end multimodal document parser, under the Apache 2.0 license on Hugging Face.
  • The model scored 96.58 on OmniDocBench v1.6, the first end-to-end model to top a leaderboard previously dominated by pipeline methods.
  • OvisOCR2 is post-trained on Qwen3.5-0.8B via SFT, RL, and OPD stages, and outputs Markdown with HTML tables and LaTeX formulas.

A 0.9 billion parameter open weights model just topped an end-to-end document parsing leaderboard that pipeline systems had owned, and it was released under Apache 2.0 by a group most people outside of document AI have never heard of. That is the ATH-MaaS drop, OvisOCR2 on Hugging Face, posted with a technical report and matching weights.

The claim on the model card is that OvisOCR2 scores 96.58 on OmniDocBench v1.6 as the first end-to-end model to lead a benchmark previously dominated by pipeline methods, the stacks that chain layout detection, text recognition, and post-processing together. It also posts a 75.06 average on PureDocBench. The model is a post-training of Qwen3.5-0.8B, using a multi-stage recipe the authors describe as SFT, RL, and OPD on a mix of real and synthetic documents. Output is Markdown, with HTML for tables and LaTeX for formulas, plus bounding box coordinates for visual regions. Inference is wired for vLLM and SGLang.

Why that combination matters if you run a document AI pipeline: the commercial OCR API line item is priced per page, and the incumbent argument for paying that price has been quality on messy real-world PDFs. A 0.9B open-weights model that leads the public benchmark and fits comfortably on a single GPU changes the make-versus-buy math, at least at the level of a pilot.

The honest caveat is the one the model card itself flags: outputs can be incorrect or incomplete on the diversity and complexity of real-world documents, and manual verification is recommended for critical applications. Benchmark leadership is not the same as reliability on your worst scanned invoice or your densest legal exhibit. What the model card does not spell out is which languages the model handles cleanly, what is in the training corpus in enough detail to reason about licensing, or how throughput compares to the closed APIs at production load.

The forward-looking part is who this quietly benefits: teams doing domain-specific document work, legal contracts, medical forms, scientific PDFs, who can now fine-tune on their own corpus without asking a vendor for permission, and researchers who get a reproducible baseline for further OCR work. Pilot it on your ugliest pages before you touch the procurement contract.