For anyone building an AI toy, Tuya or Espressif is often the first hard question. We (Shenzhen Nablai Intelligent Technology Co., Ltd., brand name Nablai) back both lines, and there is a clear matching logic behind that.
Two lines, not duplicated effort
Customers often ask us why we build TY on the Tuya platform and LX on the Espressif platform at the same time - do the two lines not compete with each other? Working from the Tuya T5E, the Espressif ESP32S3 and the PY32, we have built three product lines - TY, LX and NT - of which TY and LX map onto the two major ecosystems. That is not duplicated effort; it is a different key for a different commercial goal.
What TY and LX actually are
Let us first be clear about what TY and LX are. The TY Series is built on the Tuya T5E, a mature full-stack IoT platform that works out of the box: device connectivity, AI conversation, 60+ languages and overseas pre-compliance all come packaged, with brand sovereignty exercised inside the Tuya ecosystem. The LX Series is built on the Espressif ESP32S3 and is our own dual-track design: Espressif ESP-IDF runs on the device, the Nablai private cloud runs in the cloud, and it ships with the Nablai App, WeChat Mini Program and the AMS vendor management platform, with accounts, content and data owned entirely by the brand owner.
Architecture: both are dual stack; the difference is sovereignty
One thing has to be said plainly about architecture: TY002 and LX002 are both a local SDK + cloud API dual stack. The difference is ecosystem ownership and brand sovereignty, and it is absolutely not a straight comparison of TY as pure cloud against LX as pure local. The local SDK handles wake-up, basic interaction when the connection drops and on-device command parsing; the cloud API carries semantic understanding and OTA. NanoToy (PY32) is the true pure UART command module - no AI, no cloud, no SDK. Only once the dual stack is clear can you see why the two lines can coexist: they share a single engineering model, and differ only in who owns the cloud and the ecosystem.
Why two platforms
Why two? Because customer goals fall naturally into two groups. One group wants product in overseas markets as fast as possible, and what they need is speed and dependability - Tuya's years of overseas service, global data centers and certification system, with three weeks of prototyping and three months to mass production, make TY the fast lane into global markets. The other group wants to build its own brand, and what it needs is sovereignty - users, data and content held in its own hands, with room to run follow-on operations and sell subscriptions. LX's independent account system and AMS console exist for exactly that. We do not sell a single truth; we sell the right match.
How to choose: look at the commercial goal
The selection logic is simple: pick TY if speed into overseas markets comes first, pick LX if brand sovereignty comes first. Plenty of customers lead with TY to validate overseas demand, then use LX to build up their own system - the two lines are not an either/or, they are a sequence. And if you want to test the water cheaply first, NT (PY32, pure UART) is there as a fallback. There are only three decision dimensions: target market, appetite for brand sovereignty, and time to market.
The question that most often misleads
The easiest trap in a two-platform strategy is asking which line is more advanced. The two lines rest on different platforms and serve different positions; neither outranks the other. The question that actually matters is what my commercial goal is. Conflate wanting speed with wanting sovereignty and either your overseas launch gets dragged down by compliance, or your own system never gets built. When we take on a customer, the first thing we do is help them take the goal apart.
Build it all in-house? Most factories should not start from zero
Some people also ask whether they can build the whole thing themselves. Technically yes, but the price is an asset-heavy operation: an AI team, cloud architecture, compliance qualifications, multilingual corpora - every one of them an ongoing commitment. The value of TY and LX is that they package these capabilities, which are not in a toy company's DNA, into a module, so the factory can concentrate on design and manufacturing and "you design and manufacture, we make it smart" becomes a real arrangement rather than a line in a pitch deck. Building in-house is not impossible; it is just not where most toy factories should start from zero.
A typical two-platform combination
A typical combination: the customer first uses TY to build an export plush bear and gets it listed overseas within three months; once that is running, they migrate their own IP and lesson content onto LX and set up their own user system and subscription content. The same bear borrows an ecosystem to move fast in the first half, then comes back in-house in the second - the underlying logic of a two-platform strategy is letting the customer switch to the right form at the lowest cost at each stage.
Two roadmaps running in parallel across the industry
At the industry level, the argument between the two AI toy roadmaps is still going on. According to Guangdong province's Action Plan for Accelerating AI Adoption in the Toy Industry (2025-2027) and a number of market research reports, the global AI toy market is growing quickly, with global expansion and brand-building running as two parallel main threads. By backing both TY (ecosystem-led expansion) and LX (brand sovereignty), what we are really doing is leaving both speed and dependability in the customer's hands.
FAQ
Q: How do I choose between TY and LX? A: Pick TY if speed into overseas markets comes first (Tuya T5E, fast pre-compliance); pick LX if brand sovereignty comes first (Espressif ESP32S3, independent accounts plus data you own). Plenty of customers lead with TY and then consolidate on LX.
Q: How do the two lines differ architecturally? A: TY002 and LX002 are both a local SDK + cloud API dual stack; the difference is ecosystem ownership and brand sovereignty, not cloud vs. local. NanoToy (PY32) is the true pure UART command module.
Q: What if I want to test the water at low cost? A: The NT Series (PY32, pure UART) has no AI and no cloud, and suits small-batch validation of expression screens and read-along accessories.
Q: Can we build the entire AI system in-house? A: It is technically feasible but asset-heavy. TY and LX package the AI, the cloud and compliance into a module, so most toy factories do not need to start from zero.
The most common trap in selection is treating technical sophistication as the only criterion. Whether a platform is advanced only means something once it is matched against a commercial goal. Work out first whether you need speed or sovereignty, and the right solution surfaces on its own.
About Nablai
Nablai is an AI company, and AI smart toys are the application area we focus on today. Our product is the AI smart toy module, and our goal is to give toy companies a product-level solution for bringing AI into their toys.
We have built three product families:
- TY Series: built on Tuya T5E, 60+ languages, the fast lane into global markets
- LX Series: built on Espressif ESP32S3, full brand ownership, deep customization
- NT Series: built on PY32, a low-cost way to test the smart toy market
- Website: https://www.nablai.com.cn
- Phone: 15917703502
- Slogan: Driven by gradients, optimized by intelligence. Powered by Nabla, Optimized by AI.
Shenzhen Nablai Intelligent Technology Co., Ltd. — AI module specialists for smart toys
📧 contact@nablai.com.cn 🌐 www.nablai.com.cn