Documentation
Module guides, integration notes, delivery details, and hardware setup paths will live here.
In preparationBrowse SDK modules →
Developer hub
Build against the SDK, with engineers in the loop.
Start with the public evidence. See what is published, what is in preparation, and how to reach an engineer.
Resource index
Know what exists before you integrate.
Public states are part of the interface. Unpublished material stays labeled until it is ready.
Samples
Working capture, record, stream, and analysis pipelines will be indexed by module in the nexvdo-docs and nexvdo-samples repositories. Final public URLs are not published.
Pending — GitHub org transfer in progress
API reference
Signatures, types, error behavior, and lifecycle notes will publish with the documentation set.
In preparation
Benchmark index
Measured throughput and latency records will be indexed here once each figure is approved with its date, scope, and test setup.
Pending approvalRead the support model →
See the pipeline shape first.
The public API reference is in preparation. This sketch shows the four-module flow without presenting unpublished signatures as final.
pipeline.cpp
// Illustrative sketch — final signatures publish with evaluation access
auto device = nexvdo::open_first_device();
auto session = device.record("clip.mp4");
device.stream_preview(display_frame);
auto metadata = session.analyze(model_handle);Sample repositories — pending publication while the GitHub organization transfer completes.
Included free with YUAN hardware, delivered through a supported evaluation path — engineer answer within 48 hours.
The full API surface is published with evaluation access.
GitHub-first support keeps engineering answers searchable.
Neteon handles first-line support and routes escalations to YUAN engineering.
Learning path that exists today
YUAN's Developer Hub is live. Start with Pandora, then move into the SDK.
The published path has 10 chapters. Hardware setup comes first. QCAP and QDEEP close the path with 24 NexVDO SDK tutorials.
QCAP covers capture, record, and stream. QDEEP covers analysis. This is the live evidence layer while the portal reference set is prepared.
10chapters
24SDK tutorials
QCAP
10 tutorials across capture, record, and stream.
QDEEP
14 tutorials for the analysis path.
Compatibility matrices
No inferred cells.
The table is ready for evidence. Every unpublished cell keeps its state visible.
Benchmark index — pending until approvedNo public version numbers are publishedCompatibility download — pending publication
| Coverage area | Compatibility | Evidence | Artifact |
|---|---|---|---|
| Hardware targets | Matrix — pending publication | Test record — pending publication | Download — pending publication |
| Operating systems | Matrix — pending publication | Test record — pending publication | Download — pending publication |
| Module coverage | Matrix — pending publication | Test record — pending publication | Download — pending publication |
| Validated configurations | Matrix — pending publication | Test record — pending publication | Download — pending publication |
Buying a product?
You are building your own device — NexVDO SDK plus YUAN hardware inside your product.
Start at the SDK →Commissioning a system?
You need an integrated stack delivered and supported — hardware, software, and integration through Neteon.
Request scoping →Support model
Engineers stayin the loop.
Start with the public surface that matches the question. Every unpublished surface keeps its state visible.
Read the support modelGitHub Discussions & Issues
Ask in the open. The first response comes within 48 hours. Engineering answers remain searchable for the next team.
Read the workfloworg transfer in progress
Instant AI support
A documentation-grounded assistant is planned for direct answers from the published reference set.
Read quick answerslaunches with docs
Documentation
SDK guides, API references, sample paths, and compatibility tables will live in one index.
View the indexin preparation
Quick answers
Where are the public SDK docs?
The NexVDO documentation and API reference are in preparation. YUAN's published Developer Hub is the live learning path available today.
How is the SDK delivered?
It is included free with YUAN hardware and delivered through a supported evaluation path. An engineer answers evaluation requests within 48 hours.
Where can I see working examples?
YUAN publishes 24 NexVDO SDK tutorials across QCAP and QDEEP. The nexvdo-docs and nexvdo-samples repositories remain pending while the GitHub organization transfer completes.
How does support work?
GitHub issues are the intended first line. Neteon handles the first response within 48 hours and escalates product questions to YUAN engineering.
Use it with your stack
DeepStreaminference pipelines
TensorRToptimized inference
NVENChardware encode
GPUDirectzero-copy video
Jetsonedge compute
PyTorchmodel training
TensorFlowmodel training
ONNXmodel interchange
OpenCVvision processing
GStreamermedia pipelines
FFmpegtranscode tooling
ROS 2robotics middleware
C++native API
Pythonscripting API
Named integrations reflect the stacks NexVDO deployments run beside. Detailed integration notes — pending publication.
Bring the pipeline you need to ship.
Request an evaluation. An engineer answers within 48 hours and maps the SDK, hardware, and support path to your build.
Request an evaluation