Most hardware just sits there. This one talks back — and remembers you.
AIPI Lite is an AI character — a voice, a memory, a personality you write yourself. Pick from 80+ voices out of the box; it learns you the longer you use it. Build it into a droid, a speaker, anything — and the hardware finally has a soul.
Inside the community: bigger discount drops, member builds, early access.
$3 off · TINKER auto-applied at checkout.
sticks918
An ESPHome template that brings AIPI Lite straight into Home Assistant, with voice control wired into the smart home.
noise754
A bridge that runs AIPI on a fully local stack. Whisper transcribes, a local LLM answers. No cloud, no API keys.
NightView · AI Prop Builds
An evolving set of AI prop experiments: a custom command console, a wall-mounted build, and a plan to add AI to 3D-printed masks.
NightView · Moto Studio Guide
A community walkthrough of connecting a servo, building an Action Group, and deploying motion with Moto Studio. Follow official wiring guidance for hardware safety.
OR-3O
A community-built protocol-droid head using AIPI Lite as its conversational core and a separate 4W speaker.
Orville Lee · AIPI Videos
Two creator demonstrations, including a custom character example, shared by @orvillelee.
AIPI Lite Desktop Stand with Acoustic Chamber
A 3D-printable desktop stand for AIPI Lite with an integrated acoustic chamber.
The back of the device is the part most companies hide.
Ours has six pads, labeled, in plain sight. Here's what they're for.
Lifeblood VBAT + GND
Direct access to the battery rail. Power external circuits from the same source the device uses. Or — go the other way — solder a bigger battery, a solar panel, or a different power architecture entirely. The device doesn't care where its electrons come from.
Voice-out TX + RX
A second mouth, for talking to other machines instead of to you. Connect AIPI's UART to a Pi, an Arduino, an STM32, another microcontroller. AIPI sends the AI commentary; the partner board turns the wheels, swings the arm, prints the receipt. Same protocol on both ends, public on the wiki.
Senses IO40 + IO41
The two cleanest GPIO on the chip — neither is a strapping pin, neither is reserved by the SoC. Each can become an I²C bus, an ADC channel, a touch input, a PWM output for servos, or an interrupt that wakes the droid when something in the world changes. This is where you give the droid its sight, its touch, its reflexes.
Pick a voice. Or clone your own.
Explore six featured character examples. Each is a starting point you can rewrite at xdc.aipi.com — change their lines, change their personality, change everything but the voice. Or replace the voice itself.
Garage Mentor
Speak & Build
Ham Radio Friend
Plucky Droid
Patient Mainframe
Wonder Host
Most dev boards have no soul.
Most AI droids have no body to modify.
Some dev boards wait silently in your drawer for you to give them purpose. Some AI pets at the toy aisle ship with personalities you can't edit and shells you can't open. AIPI Lite sits between — a finished AI droid you can disassemble, reprogram, extend, and rebuild without losing the part that makes it feel alive. Same brain, different body — a sculpture you're carving, a prop you're machining, a figure you're 3D-printing.
Not just an ESP32 dev kit — the AI stack is the hard part.
Not just a Raspberry Pi — Pi runs Linux. AIPI runs a character.
Not just Alexa — Alexa won't let you solder its UART.
Five steps. You start anywhere. You stop anywhere.
Most people stay on Rung 2 forever and that's fine. Some people reach Rung 5 in a weekend. The droid is the same droid — what changes is how deep you go.
Talk to it before you change anything.
Plug it in. The screen lights up. There's already a character living inside, ready to answer. You don't have to write a single line of code to know whether the device works for you.
Tech drawer ▾
Stock firmware. Default Xorigin agent. The Free plan includes AI agents, with more added over time, plus GPT-4.1, Xorigin, Gemini, Azure, and AmazonBedrock. Pro and above also add GPT-5.2 and GPT-5.5.
Teach it who it is.
Open xdc.aipi.com on any browser. Write the character: who they are, how they speak, what they care about. Paste in your knowledge — up to 5,000 characters on Free and Pro, 20,000 on Ultra. Now the droid is no longer Xorigin's. It's yours.
I'm not a hardware background, but I like to code and tinker on the side.
— Colin F., 45 AI characters and counting
Tech drawer ▾
Character-definition system. Knowledge base via web interface (text input only, no file upload). Changes propagate to device over WiFi within seconds.
Make it sound like someone real.
Clone a voice — yours, a loved one's (with permission), or any properly licensed track. Once approved, your character speaks with that voice. Most people stop here. The device is now a fully personal AI droid with the personality and voice you chose.
Tech drawer ▾
Voice cloning is included with Pro ($9.99/mo or $7.99/mo with auto-renew, 5 tracks), Ultra ($15.99/mo or $13.99/mo with auto-renew, 10 tracks), and Ultra Lifetime ($199 one-time, unlimited tracks). Auto-renew saves $2/mo and can be canceled anytime. Approval window up to 24 hours. Voice license verification required.
Give it a body.
Software side, no soldering yet. AIPI speaks MCP. Wire it into the services and home systems you already run — your character can read from them, trigger them, hold a conversation around them. Most builds start here.
Ready to solder? AIPI's TX and RX pads connect to a Pi, Arduino, or STM32 over UART. Send your droid a line over the documented protocol, and watch AIPI talk while your partner board drives the servos, the wheels, the head turn. We provide the soul. You sculpt the shell.
Robert Lipe's hardware reverse-engineering at robertlipe.com/449-2/ maps the same pads our protocol uses — public, documented, matches our internal docs.
Tech drawer ▾
MCP over SSE, user-addable. UART on TX/RX pads (ESP32-S3 SoC). Frame format and command set documented in the protocol spec.
Give it organs.
Six labeled solder pads on the back. VBAT and GND let you power simple external circuits from the device's own battery. TX/RX is your protocol channel to the partner board you wired up at Rung 4. IO40 and IO41 are direct sensing pins on the AI brain itself — ADC, touch, interrupt capable. Tie them to small inputs (a PIR, a button, an analog dial) and the protocol spec lists the events your character can subscribe to.
For everything heavier — multi-axis servos, motor matrices, displays, the moving parts of an art piece — drive it from your partner board on Rung 4. AIPI's two direct pins are reserved for sensing. Anything that turns or moves goes on the body.
I want to hook up some things to the pins... create a smart sensor... humidity, you might say something at me.
— Jason M., currently soldering AIPI into a droid
Tech drawer ▾
VBAT (3.3-4.2V Li-Po raw), GND, UART1 (TX/RX) per the documented protocol, IO40 and IO41 as direct GPIO with ADC and touch capability. Full pinout in §6.
$3 off · TINKER auto-applied at checkout.
Give your character a body that moves.
Create servo actions in the Visual Motion Editor, organize them in your Motion Library, and deploy them directly to AIPI Lite. Moto Studio is live on XDC; motion deployment requires Firmware v1.2.5 or later.
Full specs, pinout, and reference docs ▾
SoC & memory
| SoC | ESP32-S3 |
|---|---|
| Flash | 16MB |
| PSRAM | 8MB embedded |
| USB | Type-C, charging only — see §7 Q1 for firmware policy |
Audio
| Codec | ES8311 |
|---|---|
| Microphone | onboard MEMS |
| Speaker | onboard |
Power & battery
| Battery | Li-Po, 3.3–4.2V nominal |
|---|---|
| Charging | via USB-C, 5V/1A |
Pin assignments (back panel)
| VBAT | Battery rail · 3.3–4.2V raw, capable of sourcing/sinking |
|---|---|
| GND | Ground |
| TX | UART1 TX (protocol channel) |
| RX | UART1 RX (protocol channel) |
| IO40 | GPIO · ADC + touch · stock firmware uses this for volume |
| IO41 | GPIO · ADC + touch · fully-free direct sensing pin |
Reference docs
| Wiki | static.aipi.com/AIPI_InstructionBook/AIPI_InstructionBook.html |
|---|---|
| Reverse-engineering writeup | www.robertlipe.com/449-2/ |
Questions Makers actually ask.
Q1 ·Can I run my own firmware?
Not officially. AIPI Lite is a closed appliance — we don't open-source the embedded firmware, and we don't publish a flashing flow. What we do open is the six-pad UART protocol, so your AIPI can talk to a Pi or Arduino you already own and let you build whatever body you want around it. The brain stays ours; the body is yours.
Q2 ·Can I run it without an internet connection?
No. The LLM runs in the cloud, so AIPI needs WiFi to think. The protocol layer (Rung 4) is local — your AIPI can drive a partner board's offline hardware (servos, sensors, displays) over UART regardless of network state. But the conversation itself requires the cloud.
Q3 ·What's the catch with the subscription?
No catch. Free ($0) includes AI agents—with more added over time—plus a 5,000-character description, Knowledge Base, and GPT-4.1. Pro is $9.99/mo or $7.99/mo with auto-renew; Ultra is $15.99/mo or $13.99/mo with auto-renew. Auto-renew saves $2/mo and can be canceled anytime. Ultra Lifetime is $199 one-time.
Q4 ·Why are the back contacts exposed?
Because we want you to use them. Keep the contacts dry and free of debris, and never short them with wire or other metal objects. For powered builds, follow the wiring guidance and use only suitable accessories.
Q5 ·What can Moto Studio control directly?
AIPI Lite can provide up to four direct PWM control channels through CH1–CH4: IO40, IO41, RX/IO44, and TX/IO43. For multiple servos or motor projects, use an appropriate external power supply or motor driver and share ground with AIPI Lite; do not power DC motors or several servos directly from the device.
Q6 ·What's the BOM cost?
We don't publish it. The device retails at $35.99. The number worth arguing about is what you build with it, not what's inside it. Buy two and experiment.
Q7 ·How do I create and deploy motion?
Open XDC and go to Tool Workshop → Moto Studio. Build a Motion Group in the visual editor, save it to your Motion Library, then choose Deploy to Device. AIPI Lite needs Firmware v1.2.5 or later.
Q8 ·Can I reuse a motion on more than one device?
Yes. Motion Groups live in your Motion Library, so you can save a motion once and deploy it to different AIPI Lite devices instead of rebuilding it each time.
Q9 ·How can a motion be triggered?
Motions can be state-based or command-based. A state-based motion can run when AIPI enters a state such as listening. A command-based motion can be triggered by saying the Motion Group name. Voice recognition can vary, so do not treat command triggering as guaranteed in every environment.
Q10 ·What happens if a new interaction starts while a motion is playing?
The current motion stops and AIPI responds to the new event instead of waiting for the motion to finish.
Q11 ·Can Moto Studio control an external servo controller?
Not currently. The released workflow uses AIPI Lite’s four direct PWM outputs. External serial servo controllers, expansion boards, and more than four direct channels are not part of the current supported release.
$3 off · TINKER auto-applied at checkout.