StackMap
Subscribe
Explore / production-ocr-course
neural-maze

production-ocr-course

Runnable course: a production OCR pipeline on Kubernetes — Rust ingestion, Qwen 3.5 (4B) served by vLLM at 1.86 pages/s, Redis queues, KEDA autoscaling. Deploy it on AKS/GKE, not a notebook.

183 50 Rust Apache-2.0updated 3 days ago
Curator's take

The rare OCR tutorial that ends in infrastructure instead of an API call: event-driven ingestion in Rust, an SLM (Qwen 3.5 4B) on vLLM with continuous batching, and metric-driven KEDA autoscaling — the whole thing deployable on your own cluster, with an honest architecture assessment included. Read it to learn how document-understanding systems are actually operated. NOT a library you import: it's a course with a reference implementation (183 stars, young), the model choices will age, and if you just need OCR output today the mapped engines (Chandra, MinerU, olmOCR) get you there without a Kubernetes cluster.

Mapped by ShipWithAI editors · links verified
README.md

📄 Production-Grade SLM-Powered OCR Course 📄

Build a self-scaling, event-driven OCR pipeline on Kubernetes (AKS / GKE) with Qwen 3.5 + the GLM-OCR SDK


Architecture

Table of Contents

Course Overview

Most OCR tutorials stop at "call an API and get some text back." This isn't that.

Instead, we're building a production-grade, self-scaling Visual Document Understanding pipeline, deployed for real on Kubernetes (AKS or GKE), that goes far beyond flat text extraction: it reasons about charts, tables, and layout the way a human reader would — powered by a Small Language Model (Qwen 3.5) instead of a bloated frontier model.

By the end of this course, you'll have your own event-driven OCR system capable of:

  • 🧠 Understanding documents, not just transcribing them — charts, tables, handwriting, and contextual reasoning via Qwen 3.5 (4B)
  • ⚡ Serving generative OCR at 1.86 pages/second with vLLM's continuous batching, PagedAttention, and Multi-Token Prediction (MTP)
  • 🦀 Ingesting files through a high-concurrency Rust (Axum) gateway, decoupled from GPU inference via Redis
  • 🔄 Running a zero-copy, /dev/shm-based document handoff between the layout encoder and the inference engine
  • ☸️ Auto-scaling T4 (layout) and A100 (inference) node pools independently with KEDA, from zero to bursting load
  • 🔒 Locking the whole pipeline behind an Internal Load Balancer + Enterprise API Gateway (Azure APIM / GCP API Gateway), with zero public exposure
  • 🤖 Wrapping the pipeline as an MCP server for native use by AI agents, including Claude Code

Excited? Let's get started!


The Neural Maze Logo

📬 Stay Updated

Join The Neural Maze and learn to build AI Systems that actually work, from principles to production. Every Wednesday, directly to your inbox. Don't miss out!

Subscribe Now


Who is this course for?

This course is for ML/AI Engineers and Platform Engineers who already know how to call an OCR API and want to know **what it takes to run one in

Continue your stack

What teams reach for next — and why each earns a place beside production-ocr-course. Ranked by curator confidence.