Primate Vision vs. NVIDIA VSS (2026): A Managed API vs. a Build-It-Yourself Blueprint
NVIDIA VSS is the strongest self-hosted real-time video-analytics stack you can deploy — genuinely real-time, RTSP-first, GA since June 2026, with published benchmarks and the most forward-looking agent-operations story in the category. I have real respect for it.
It is also, by NVIDIA’s own documentation, not a product. It’s a reference architecture you must build and operate: you supply the GPUs, the authentication, the TLS, the Elasticsearch, the message brokers, and the ops team. A project, not a product.
Primate Vision is the managed inverse: one API call, a deterministic verdict (yes / no / indeterminate) with calibrated confidence, timestamped evidence, an annotated evidence video, and a published 45ms p50 latency — with nothing to deploy. Which one you want comes down to two questions: do you own GPUs and an infra team, and can your data leave the building?
This is part of our full 2026 video-AI landscape comparison.
What VSS actually is
In NVIDIA’s own words, VSS is “a GPU-accelerated reference architecture for building video analytics agents with real-time verified alerts, visual Q&A, and automated reporting” — VLMs (Cosmos Reason, Qwen3-VL), LLMs (Nemotron), RAG, and NIM microservices, shipped as Docker Compose profiles and Helm charts you deploy on your own NVIDIA GPUs. (VSS docs)
The docs are refreshingly explicit about what that means: “Deploy VSS in a trusted, isolated network. Do not expose the VSS services directly to untrusted networks. This release assumes authentication, TLS termination, rate limiting, and external access controls are provided by the infrastructure.”
You are the infrastructure.
Primate Vision is a hosted API. You point it at a live stream (managed WebRTC) or a file (upload or URL ingest, up to 2 GiB), ask a question in plain English, and get a deterministic verdict — yes / no / indeterminate — with a 0–1 calibrated confidence score, timestamped evidence segments, and an annotated overlay evidence video. Time-to-first-answer on Primate Vision: minutes, with a curl call — a free sandbox key is one POST away. Time-to-first-answer on VSS: days to weeks of deployment work. That’s not a criticism of NVIDIA; it’s the definition of a reference architecture.
The head-to-head
| Dimension | Primate Vision | NVIDIA VSS |
|---|---|---|
| Delivery model | ✅ managed API, nothing to deploy | ❌ self-hosted blueprint: Compose/Helm, NIMs, Elasticsearch, brokers, GPU tuning |
| Live stream input | ✅ managed WebRTC | ✅ RTSP first-class; up to 100-stream configs, 16×1080p concurrent tested |
| Real-time, GA | ✅ 45ms p50 / 316ms p95 published | ✅ GA 3.2 (June 2026), hardware-dependent benchmarks published per microservice |
| Verdict contract | ✅ deterministic yes/no/indeterminate + calibrated 0–1 confidence, one clean JSON | ⚠️ VLM-generated yes/no verdicts — stochastic, uncalibrated; results fragment across Elasticsearch, Kafka topics, and agent chat |
| Documented verdict failure modes | — | ⚠️ their own release notes: captions containing “yes”/“true” create spurious incident records; negative-intent search matches positive results (release notes) |
| Bounding boxes / 3D tracking | ❌ overlay evidence video only, no bbox JSON | ✅ DeepStream detection/tracking JSON + synchronized multi-camera 3D tracking |
| Embeddings / search | ❌ none | ✅ Cosmos-Embed1 semantic search (note: default index lifecycle deletes search embeddings after 48h min age) |
| Edge / air-gap | ❌ cloud only | ✅ core story — DGX Spark to AGX Thor, zero data egress |
| Multi-camera scale | ❌ one active stream per account today | ✅ tested at 16 concurrent 1080p, 100-stream configs |
| Auth / TLS / SLA | ✅ managed; published availability targets | ❌ your burden; no SaaS SLA (nothing is hosted) |
| Webhooks | ✅ Standard Webhooks signing, retries, redelivery, Prefer: wait |
⚠️ Kafka/Redis/MQTT broker integration — not developer-facing webhooks |
Verdicts you can put in an audit trail
VSS’s alert-verification layer answers yes/no — but the answer is generated by a VLM, with no calibration and with failure modes NVIDIA itself documents: caption text containing “yes” or “true” spawning spurious incidents, prompt clobbering when concurrent agent sessions share a backend, NIM crash-recovery requiring a stack redeploy. None of that disqualifies a reference architecture. It’s honest engineering documentation, and I respect NVIDIA for publishing it. But it is the difference between a research-grade stack and a verdict you’d attach to a compliance record.
Primate Vision’s verdict is deterministic: a closed vocabulary computed by similarity scoring against the video — not sampled from a language model — with a calibrated confidence score, a pinnable model version (darwin-1.3), a deterministic test mode for CI, and one clean response shape: verdict, confidence, timestamped clips, evidence video URL. One contract, not three storage systems.
Pricing: opposite cost structures
VSS has no usage meter at all. The software is downloadable; the costs are (1) your GPUs and (2) an NVIDIA AI Enterprise subscription at $4,500 per GPU per year list ($1,125 for Inception startups) for supported production, or $1/GPU-hour consumption in the cloud plus instance costs. (NVAIE pricing)
The honest normalization (estimate — every number depends on GPU choice, utilization, and model layout): a minimal cloud deployment on 2× H100 runs roughly $14–22/hour for the box. Spread across the tested 16 concurrent streams at full utilization, that’s ~$0.9–1.4 per camera-hour; self-managed at fleet scale, perhaps $0.3–0.6. At single-stream utilization, it’s the full $14–22/hour. The structural truth is simple: high fixed cost, near-zero marginal cost. The exact inverse of a usage meter.
Primate Vision has two lanes:
- Metered — $0.01 per second of source video ($0.60/min), flat, fps-independent. Queued time free; failed jobs free. A 30-second clip → verdict + evidence = $0.30, with zero fixed cost, zero GPUs, zero NVAIE contracts.
- Enterprise — contact us for 24/7 continuous monitoring and camera fleets: dedicated capacity or on-site deployment at a small fraction of the metered rate, under highly discounted enterprise plans — which is the correct comparison against a VSS fleet deployment, not the metered rate.
Normalized at the metered rate we’re $36/camera-hour† — far above VSS at fleet utilization. We print that number ourselves because hiding it would be dishonest. The two cost curves cross exactly where you’d expect: occasional questions and bursty workloads favor a meter; owned 24/7 fleets favor owned GPUs — or our enterprise lane, which exists for precisely that workload and can include on-site deployment.
† Metered rate normalized for comparison. Primate does not sell 24/7 continuous monitoring at the metered rate — continuous and fleet workloads use enterprise plans; contact us.
One VSS budget line worth knowing: all 2.x/3.0/3.1 container images are deprecated and get removed from NGC on September 30, 2026 — self-hosters are on a forced re-deploy treadmill.
Choose NVIDIA VSS instead when…
For some buyers these are decisive, and they should be:
- Your data cannot leave the building. Sovereign, defense, critical-infrastructure, or privacy-bound deployments where any cloud API — including ours — is disqualified. VSS runs air-gapped, edge profiles down to DGX Spark and AGX Thor.
- You run a 24/7 multi-camera estate with budgeted GPU capex and a platform team. Dozens-to-hundreds of streams, near-zero marginal cost per added camera — structurally cheaper than any usage meter at that scale.
- You need classic CV fused with VLM reasoning: DeepStream tracking, tripwires, ROI rules, synchronized multi-camera 3D tracking — capabilities no cloud vision API (ours included) exposes.
- You’re an ISV building a video-analytics product and want an NVIDIA-blessed reference architecture instead of assembling DeepStream + vLLM + RAG yourself. Their agent-ops story (Agent Skills, VA-MCP servers, validated agent harnesses) is genuinely the most forward-looking in the category.
Choose Primate Vision when…
- You want an answer this afternoon, not a deployment this quarter. One curl call vs. Compose stacks, Elasticsearch, brokers, and GPU memory tuning.
- You don’t have (or want) GPUs and an infra team. No $4,500/GPU/year licensing, no capex, no ops burden, no upgrade treadmill.
- The verdict has to be trustworthy and auditable. Deterministic closed-vocabulary answers with calibrated confidence and watchable evidence — versus stochastic VLM verdicts with documented spurious-incident bugs.
- You need managed security and a clean contract: auth, TLS, and rate limiting are our problem, and every answer arrives in one JSON shape with webhooks or
Prefer: wait. - Your workload is bursty or on-demand. Pay $0.30 for a 30-second question; pay nothing when idle.
Try it
Try it for free — real processing, no card required to start.
Your AI agent can do it for you — right from Claude. Primate Vision ships an MCP server, llms.txt, markdown docs twins, and a sandbox key available in a single POST — your agent can get a key, upload a clip, and read back a verdict without a human touching a dashboard.
For 24/7 monitoring and camera fleets: see our enterprise plans.
Method note: every VSS claim traces to NVIDIA’s docs, release notes, performance pages, and NVAIE licensing guide accessed 2026-07-31. All $/camera-hour figures for VSS are labeled estimates with assumptions stated; NVIDIA publishes no such number.