GitHub Issues
The first line for bugs and integration questions. Get a first response from an engineer within 48 hours.
Org transfer in progressVisit the developer hub →
Support
Engineers answer. Here is where.
GitHub issues are the first line — first response from an engineer within 48 hours. Neteon runs first-line support in U.S. hours. Escalations go to YUAN engineering in Taipei.
Office hours — schedule pending publication
Pick the channel
Four channels, one rule: an engineer reads it. Channel states below are the honest current states.
GitHub Discussions
Ask design and pipeline questions in the open. Get answers that stay searchable for the next team.
Org transfer in progressVisit the developer hub →
Documentation
Get module guides, integration notes, and compatibility tables from the team that writes the SDK.
In preparationVisit the developer hub →
Evaluation requests
Get a substantive answer to your use case from an engineer within 48 hours. Evaluation hardware ships from U.S. stock.
Escalation path
Who answers — and in what order
Neteon operates the first line from the U.S. — answering in U.S. hours on committed SLAs, backed by 20+ years as a North American industrial-infrastructure distributor.
When a question needs the SDK team itself, it escalates to YUAN engineering in Taipei. The path is short and it ends at the people who wrote the code.
You file a GitHub issue
First response from an engineer within 48 hours.
Neteon — first line
U.S. hours, committed SLAs. 20+ years distributing industrial infrastructure in North America.
YUAN Taipei — engineering escalation
The team that builds the SDK and the hardware.
Response targets
Committed targets are stated plainly. Everything else renders as its honest current state.
| Channel | First response | Who answers | Status |
|---|---|---|---|
| GitHub Issues | 48 h | Engineers — Neteon first line | Org transfer in progress |
| GitHub Discussions | No committed target | Engineers | Org transfer in progress |
| Evaluation requests | 48 h | Neteon first line, YUAN Taipei on escalation | Open — via the evaluation form |
| Documentation | — | Written by the SDK team | In preparation |
| Office hours | — | Engineers | Schedule — pending publication |
The support surfaces
GitHub Discussions & Issues
Ask in the open. Issues and discussions are answered by engineers and stay searchable for the next team.
Visit the developer huborg transfer in progress
Instant AI support
An assistant trained on the NexVDO documentation set, for answers at typing speed.
Get instant answerslaunches with docs
Office hours
Recurring engineer office hours are part of the support model. The schedule is not published yet.
Ask through an evaluationschedule pending
Quick answers
How is the SDK licensed?
NexVDO is included free with YUAN hardware — there is no license line in the adoption decision. It ships through a supported evaluation path rather than a public download.
How do I get access?
Request an evaluation. An engineer sends a substantive answer within 48 hours, and evaluation hardware ships from U.S. stock.
Which platforms does it target?
One SDK surface across NVIDIA Jetson and Intel x86 targets. Per-platform compatibility tables are pending publication.
Who answers support requests?
Neteon fronts first-line support in U.S. hours on committed SLAs, with escalation into YUAN's Taipei engineering team.
Need a human?
Evaluation requests get a substantive answer from an engineer within 48 hours. Business and hardware questions route to Neteon — YUAN's U.S. front door.
Evaluate on real hardware
Request an evaluation and get a substantive answer — from an engineer — within 48 hours. Evaluation hardware ships from U.S. stock.
Request an evaluation