nvidia/simready-assets
Updated • 1.24M • 1.33k
Chukwuma Nwaugha
nwaughachukwuma
AI & ML interests
high-performance Inference for visual AI (vlm-run gateway). context engineering (mm-ctx)
Recent Activity
liked a dataset about 11 hours ago
nvidia/simready-assets liked a model about 11 hours ago
deepseek-ai/DeepSeek-V4.1-Flash-1017 liked a model about 21 hours ago
nvidia/NVIDIA-Nemotron-3.5-Transcribe-30B-A4BOrganizations
liked a
dataset about 11 hours ago
liked a
model about 11 hours ago
liked a
model about 21 hours ago
liked a
dataset 7 days ago
liked a
model 7 days ago
Qwen/Qwen3.5-0.8B
👍🚀 48
12
#8368 opened 8 months ago
by 
Atlas-0
nvidia/parakeet-tdt-0.6b-v3
🚀❤️ 42
3
#4167 opened about 1 year ago
by 
nhminetz
dots-studio/dots.mocr
👍 1
2
#11532 opened 3 months ago
by 
spillai
google/diffusiongemma-26B-A4B-it
🤗🔥 72
2
#10415 opened 5 months ago
by 
someguywithacomputer
google/embeddinggemma-2
👍 8
5
#12924 opened 23 days ago
by 
sebinesh5657
facebook/sam3
🤝👍 111
14
#6223 opened 12 months ago
by 
abhishekkrishnanaik
facebook/sam3.1
👍 15
5
#9331 opened 7 months ago
by 
Vishruth-N
liked a
dataset 18 days ago
replied to their post 20 days ago
This list comprises models strictly from vlmrun Gateway - https://vlm.run/gateway
posted an update 29 days ago
Post
118
Here's how the best OCR/chat models on vlmrun gateway - https://vlm.run/gateway - performed on a very hard (x2) to read handwritten French weather-log document.
Scores are 0–100, averaged over 3 runs and two LLM judges - Claude Opus 5.5 and GPT-5.6 Sol. Latency is average time per request.
Scores are 0–100, averaged over 3 runs and two LLM judges - Claude Opus 5.5 and GPT-5.6 Sol. Latency is average time per request.
- 2 replies
liked a
model about 1 month ago
posted an update about 1 month ago
Post
71
Cheap, fast, and efficient OCR + RAG pipeline with VLM Run Gateway and TypeSafe AI Jev.
liked a
dataset about 2 months ago
posted an update about 2 months ago
Post
3,245
It’s easy to get distracted by benchmarks, throughput (tok/s), and all the hype around frontier model releases.
This is Shiny Model Syndrome, which makes engineers and teams forget the basic physics of production software, i.e., using the right tool for the job and optimizing for ease of integration.
- Teams spend huge amounts of money on frontier models for document parsing, OCR, detection, segmentation, and other task-specific visual AI workflows.
- Inference marketplaces don’t find it profitable to list task-specific models like glm-ocr, paddleocr, or dots.mocr, even though they’re all superior to frontier VLMs for document parsing and OCR.
- Engineers stitch together multiple endpoints for different use cases across the long tail of visual AI. Those who choose to self-host instead deal with painful infrastructure and GPU ops.
At VLM Run, we wanted one place to run OCR models, VLMs, and ViTs that we could confidently use for our own internal agents and evals. The gateway was born out of that need, and we’ve since opened it to the public.
The gateway exposes a single OpenAI-compatible endpoint for the long tail of visual AI across OCR, document parsing, VQA, detection, segmentation, embeddings, and transcription. Simply point the base_url of your OpenAI SDK at gateway.vlm.run/v1/openai, or ask your agent to connect via MCP (gateway.vlm.run/mcp).
You can swap the model name to compare glm-ocr, dots.mocr, paddleocr-vl-1.6, qwen3.8-27b, gemma4-26b-a4b, and more. We handle serving, runtime, and pipelining behind the scenes to give you high-quality visual intelligence.
- https://vlm.run/gateway
- https://huggingface.co/blog/vlm-run/introducing-gateway
- https://www.vlm.run/blog/introducing-gateway
This is Shiny Model Syndrome, which makes engineers and teams forget the basic physics of production software, i.e., using the right tool for the job and optimizing for ease of integration.
- Teams spend huge amounts of money on frontier models for document parsing, OCR, detection, segmentation, and other task-specific visual AI workflows.
- Inference marketplaces don’t find it profitable to list task-specific models like glm-ocr, paddleocr, or dots.mocr, even though they’re all superior to frontier VLMs for document parsing and OCR.
- Engineers stitch together multiple endpoints for different use cases across the long tail of visual AI. Those who choose to self-host instead deal with painful infrastructure and GPU ops.
At VLM Run, we wanted one place to run OCR models, VLMs, and ViTs that we could confidently use for our own internal agents and evals. The gateway was born out of that need, and we’ve since opened it to the public.
The gateway exposes a single OpenAI-compatible endpoint for the long tail of visual AI across OCR, document parsing, VQA, detection, segmentation, embeddings, and transcription. Simply point the base_url of your OpenAI SDK at gateway.vlm.run/v1/openai, or ask your agent to connect via MCP (gateway.vlm.run/mcp).
You can swap the model name to compare glm-ocr, dots.mocr, paddleocr-vl-1.6, qwen3.8-27b, gemma4-26b-a4b, and more. We handle serving, runtime, and pipelining behind the scenes to give you high-quality visual intelligence.
- https://vlm.run/gateway
- https://huggingface.co/blog/vlm-run/introducing-gateway
- https://www.vlm.run/blog/introducing-gateway