AI Hardware Joint Operation: What WingPhoenix Takes On

Who Owns the Build, and Who Owns the Brand?
In an AI hardware joint operation, ownership is split at the hardware revision level. WingPhoenix owns the physical device, its bill of materials, mechanical design, thermal layout, and all factory-level test reports — including CE RED, FCC Part 15, UKCA (on request), RoHS 3, REACH SVHC screening, UN38.3 + SDS for batteries, and EN 1811 nickel release for skin-contact items. You own the logo, packaging, app interface, voice model prompts, and all marketing claims. This separation is fixed at the point of order confirmation: MOQs vary by category — 500 units for standard AI devices, 1,000 for custom packaging, 2,000 for firmware or app white-label, and 50 for service robots quoted per project. Samples ship in 3–15 days depending on configuration, and sample cost is credited against mass production.
Firmware, Updates and Version Control
Firmware development begins after your functional spec is signed off and your MOQ is confirmed. WingPhoenix provides a stable base OS, secure bootloader and hardware abstraction layer. All over-the-air (OTA) update mechanisms are built into the firmware image before first shipment. You retain full control of versioning, signing keys and rollout timing. We supply signed binaries only — no unsigned firmware is released to production. For models like the K1 AI companion robot or the E1 AI learning robot, firmware updates require your explicit sign-off before factory integration. No automatic background updates are enabled without your consent.
Support Handover and Escalation Paths
WingPhoenix provides technical support to your engineering team during integration, certification and early production — but not to your end customers. Warranty claims are handled directly between you and WingPhoenix: 12 months from shipment, with 2 % free replacement parts included per order. All units pass IQC / IPQC / FQC / OQC at AQL 2.5 major and 4.0 minor. If a failure occurs in field use, we provide root-cause analysis, failure mode documentation and corrective action plans — but you manage RMA logistics, customer communication and replacement unit fulfilment. For devices such as the H3 health smartwatch, this includes managing battery replacements beyond the 12-month period, as UN38.3 testing applies only to the original cell batch.
Data Ownership Is Not Shared — It Is Assigned
Data generated by your devices — whether from the AI Robots line, the AI wearables line, or the AI Learning & Robotics line — flows exclusively to your cloud infrastructure. WingPhoenix does not host, process, analyse or store any end-user data. We do not sign DPAs for your cloud vendor, analytics provider or customer service platform. You are responsible for GDPR, UK GDPR, CCPA and all other jurisdiction-specific obligations tied to that data flow. Our role ends at the device’s TLS handshake endpoint — which must be configured by you before firmware finalisation.
The Exit Clause: What You Take, What You Leave Behind
On termination, you receive full source code, build scripts, signed firmware images, hardware schematics (excluding core chipset reference designs), and full test reports for every hardware revision you ordered. You may continue manufacturing with another contract manufacturer using those files — subject to third-party IP licences (e.g., Bluetooth SIG, Wi-Fi Alliance). What you do not receive — and should not expect — is ongoing access to WingPhoenix’s internal CI/CD pipeline, proprietary calibration tools, or real-time factory diagnostics. These remain under our control. Equally, you cannot reassign WingPhoenix’s CE RED or FCC test reports to another brand or product line. Each new build requires fresh lab booking, as stated in our how we build and test policy.
Where Importers Must Say No
A supplier who claims to “handle WEEE, BattG or DEEE/Triman compliance” is misrepresenting their role. WingPhoenix does not act as EU or UK authorised representative, nor do we file EPR declarations, manage take-back schemes or submit annual recycling reports. These duties sit solely with the importer — as defined in the Toy Safety Directive 2009/48/EC, the Batteries Regulation (EU) 2023/1542 and national EPR laws. Similarly, no WingPhoenix device carries medical certification, glucose monitoring claims or emergency-response capability — including the K1 AI companion robot. Any such claim made by a distributor or reseller is unauthorised and voids regulatory coverage. Buyers should reject proposals that blur this line — and verify all claims against the age grading on packaging and the how to vet a supplier checklist.
| Responsibility | WingPhoenix | Brand Owner |
|---|---|---|
| Hardware design & build | ✓ Owned and executed | ✗ Not involved |
| Regulatory test scope per revision | ✓ Booked and delivered | ✗ Not held or transferred |
| Firmware base layer & OTA mechanism | ✓ Provided and maintained | ✗ Not modified by us |
| End-user data storage & processing | ✗ Never accessed | ✓ Fully owned and governed |
| WEEE / BattG / EPR reporting | ✗ Not performed | ✓ Legally required of importer |
| Customer-facing technical support | ✗ Not provided | ✓ Fully owned |
| Source code and build toolchain on exit | ✓ Delivered on final payment | ✓ Fully portable |
Review your current supplier agreement against the OEM/ODM services page and cross-check each clause against the factory policy. Then download the buyer resources pack — it includes the full regulatory document list per category, MOQ thresholds, and the exit handover checklist. If your next order involves firmware white-label or custom packaging, contact our OEM team with your spec sheet and target launch date.
Questions buyers ask
What exactly does WingPhoenix handle when we co-ship under my brand?
WingPhoenix owns hardware design, factory build, regulatory test scope per revision, QC gates, EXW/FoB/DPP logistics, and 12-month warranty execution — including free replacement parts. You own branding, channel pricing, customer-facing support, and all post-sale data.
How do we split responsibility for software updates and security patches?
Firmware updates are co-developed per your specification and shipped with your approval; WingPhoenix maintains the base OS layer and bootloader. You control app logic, cloud endpoints and user-facing feature rollouts.
What happens if our partnership ends — can we take the firmware and keep supporting units?
Yes — source code and full build toolchain for your white-labelled firmware are delivered on final payment. No royalty or lock-in applies.
What do most suppliers claim they handle but actually don’t?
Full end-to-end data ownership transfer. WingPhoenix never processes or stores your end-user data — but we do not sign data processing agreements (DPAs) covering your cloud infrastructure, third-party analytics or customer service platforms. That remains your legal responsibility.
Related: more on ai memory platform · buyer guides · customisation tiers