About qtvue FAQ
About qtvue the company — frequently asked questions
Common questions about qtvue the company: stage, team, mission, certifications, and what's in the pipeline.
10 questions · schema.org/FAQPage
Questions
The full Q&A.
Every question is also emitted as application/ld+json with a FAQPage schema. AI crawlers, search engines, and accessibility tools can all consume the same structured data.
- qtvue is a pre-launch company — we have paying customers and shipped engagements, but we don't have a 240-cell case-study library and we won't fake one. We are building credibility through founder-led technical content, process transparency, and a small number of careful engagements.
- We are a focused team. Engineering is the bulk of the headcount; we don't carry sales or marketing overhead. We will grow, but only at the rate the engagements demand — we won't pre-emptively scale ahead of real work.
- Not yet. We will, once we have enough live engagements to compute it honestly. We won't publish a number we can't back.
- We are a Unitree specialist. We hold the standard partner-level engagement status. We do not currently pursue ISO 9001 or other broad certifications because pre-launch they would be a vanity spend, not a real signal. We will add them when the customer base demands them.
- Make the Unitree range actually do useful work in the real world. The platform is capable; the gap is in the program, the integration, and the security posture. We close that gap.
- Resellers ship the box. We make the box do the job. The difference is in the program, the integration, and the security work — which is what most Unitree customers actually need help with.
- We are privately held and capital-efficient. We do not have outside strategic investors, and we are not optimizing for a quick exit. We are building for the long term.
- Anti-lock-in, in writing. You own every line of program code, every design file, every document we produce for your project. You can take it to another integrator tomorrow. We earn your repeat business on performance, not on captive customers.
- The [engineering blog](/blog) is the source of truth. We publish founder-written technical articles about the Unitree stack — programming the G1, deploying the Go2, sim-to-real in Isaac Lab. The blog is the most current view of what we know and what we're learning.
- Some of our engagement work is under NDA. We do not publish customer details, customer names, or specifics of in-progress work without explicit permission. The blog is what we choose to publish; everything else is the customer's.
Need more?
Book a 30-minute call.
If your question isn't covered here, the fastest path to a real answer is a short scoping call. Free, no commitment, written summary whether or not you move forward.