Free Platform Deployment: What Is Included, What Is Scoped Per Project
What “Free” Means in Practice
“Free platform deployment” refers only to the provisioning of WingPhoenix’s standard AI memory platform onto certified hardware revisions shipped from Shenzhen. It includes firmware signing with factory-issued keys, default cloud endpoint registration, TLS certificate injection, and boot-time verification enablement. This applies equally to AI Robots, AI Learning & Robotics, and AI Wearables lines — provided the model is listed in the current catalogue and matches the revision tested for CE RED, FCC, or UKCA. It does not extend to software-defined features added post-shipping, nor does it include customer-specific backend orchestration.
The Boundary Line: Where Integration Begins
Integration starts where the factory’s standardised provisioning ends. That includes custom data routing (e.g., forwarding sensor logs to a private MQTT broker), modifying the local inference engine’s output format, embedding proprietary NLU models, or adapting the OTA update mechanism to align with an enterprise MDM. These are scoped per project — quoted separately, with timelines aligned to your OEM/ODM services agreement. For example, adding OAuth 2.0 support to the K1 AI Companion Robot’s local API requires documented API contracts, security review, and regression testing — all outside free deployment.
Support and Maintenance Are Separate
Free deployment does not include ongoing platform support, SLA-backed uptime, or incident response. Technical assistance for baseline functionality — such as verifying certificate validity or confirming firmware version hashes — is available via WingPhoenix’s engineering portal. But troubleshooting custom integrations, debugging third-party API failures, or resolving misconfigured webhook endpoints falls under paid support tiers. Buyers should confirm support boundaries before committing to delivery milestones, especially when deploying across multiple geographies with divergent regulatory reporting requirements.
Migrations Are Never Free — And Here’s Why
Data migration is the most frequently misunderstood element. Free deployment assumes a green-field installation: no pre-existing user accounts, no historical interaction logs, no trained personalisation profiles carried over from another vendor. If your brand requires continuity of user history, session context, or learned preferences, that must be scoped as a discrete migration project — including schema validation, ETL tooling, consent handling, and GDPR/UK GDPR-aligned data erasure protocols. WingPhoenix does not hold, process or transfer customer data from prior vendors; any migration requires your explicit data processing agreement and documented lawful basis.
What This Process Cannot Do
This process cannot validate, adapt or certify your internal IT infrastructure for compliance with EU or UK digital product regulations. It does not generate a Post-Market Surveillance Plan, a UK Responsible Person declaration, or a WEEE registration dossier. Those remain the importer’s legal responsibility — as confirmed in our how to vet a supplier guidance. Nor does free deployment cover certification of custom firmware variants: every modified build must undergo full retesting at an accredited laboratory, with scope booked per hardware revision — including EN 62368-1 for power supplies or EN 71-3 for toy-grade leaching limits on E1 AI Learning Robot housings.
| Item | Covered in Free Deployment | Requires Project Scoping |
|---|---|---|
| Firmware signing & secure boot | Yes, for stock revision | No |
| Cloud endpoint configuration | Yes, default WingPhoenix domain | Custom domain, private cloud, or hybrid routing |
| OTA update framework | Yes, standard protocol | Custom delta logic, staged rollout rules, or offline update bundles |
| User account sync | No | SCIM, LDAP, or SAML integration |
| Data export schema | No | CSV/JSON structure alignment, PII masking, or GDPR-compliant anonymisation |
| Regulatory documentation | CE RED, FCC, RoHS, REACH supplied per revision | UKCA submission support, WEEE registration, or DEEE/Triman labelling |
| Legacy system deprecation | No | Cutover planning, parallel run validation, or fallback rollback design |
- Baseline deployment is tied to hardware revision — not order size, brand, or geography
- Every custom integration requires signed scope-of-work documentation before firmware build begins
- Sample units configured for integration testing carry the same firmware as mass production — no “demo-only” builds
- UN38.3 battery reports and SDS documents ship with every order — no exceptions for trial runs
- EN 1811 nickel release testing applies only to skin-contact surfaces on H3 Health Smartwatch and smart rings, not internal PCBs or connectors
- Google Play / GMS licensing is not included by default — see product catalogue for GMS-enabled models
Free platform deployment is a defined factory capability — not a marketing term. To proceed, download the latest factory policy document, identify your hardware revision in the product catalogue, and contact your WingPhoenix account manager to book integration scoping using the OEM/ODM services intake form. All integration projects begin with a signed statement of work and require firmware build approval at least 10 working days before production start.
Questions buyers ask
What does “free platform deployment” actually cover for our AI hardware order?
It covers baseline firmware flashing, cloud API endpoint configuration, and secure boot key injection for standard models. Everything beyond that — custom data schemas, third-party service hooks, or legacy system migration — is scoped per project.
How do finance and compliance teams verify which services are truly included versus billable?
They reference the published factory policy on <a href="https://wingphoenixai.com/factory/">how we build and test</a>, which defines free deployment as a fixed-scope activity tied to hardware revision, not use case or volume.
Our sample passed lab tests but failed in-house SSO authentication — who owns the fix?
That falls outside free deployment. Identity federation, certificate pinning, and enterprise directory integration are integration-scoped items, not covered under baseline platform provisioning.
What’s the one thing suppliers routinely overpromise on free deployment?
End-to-end data migration from an existing vendor’s cloud — no migration path, schema mapping, or historical data porting is included unless booked as a discrete project with defined acceptance criteria.
Related: more on ai memory platform · buyer guides · customisation tiers