Conversation, end to end
WebSocket hub, server-side speech recognition, a grammar engine written in JavaScript, intent routing, graph-based skills, redirects and proactive selection.
Self-hosted robot cloud
Your Jibo stopped talking in 2019. This is how it speaks again.
When Jibo's cloud shut down, every robot lost the service that understood speech, chose an answer and moved its body in time with the words. Phoenix is a clean-room reimplementation of that service — speech recognition, natural-language understanding, skills and multimodal response — running entirely on your own hardware.
Free and non-commercial. No account on anyone else's server.
Runs on your hardware
No telemetry, no analytics
Open and inspectable
One external dependency
Product
What it actually does
Not a mock and not a proxy. Phoenix implements the service the robot expects, and the robot cannot tell the difference.
The whole dialog library
All 4,424 chitchat exchanges and 82 report exchanges, reimplemented against the original dialog format — not a sample, not a subset.
Household and people
Loops, members, face and voice enrolment, and the account links that let the robot fetch each person's own weather, news and commute.
Robot revival
An OTA update server implementing the pinned Update API, serving the real 13.0.0 subsystem packages from your host instead of a service that no longer exists.
Yours, on your hardware
Robots connect over TLS with their genuine credentials. Audio, transcripts, photos and messages stay on the machine you installed it on.
Open and inspectable
Node.js and ESM JavaScript with a single external dependency. No Jibo binaries ship — only plain-text data the robot already had.
How it works
One sentence, end to end
Every word your robot hears takes the same path through Phoenix. Nothing leaves the machine you run it on.
Audio
The robot opens a WebSocket and streams microphone audio to the hub.
Speech
Server-side recognition turns the stream into candidate transcripts.
Understanding
A JavaScript grammar engine parses the transcript into an intent and its slots.
Skills
Intent routing picks a graph-based skill, which may redirect or hand off.
Response
Speech, screen and body motion return as one timed multimodal response.
Honest status
What works, and what doesn't
This project publishes its own failures. A real robot connects, authenticates and holds a conversation — and full behavioural equivalence with the original is not yet proven. Both of those are true at the same time, and the numbers below are the ones the repository tracks.
20,477of 20,528
captured requests where the parser agrees with the original
51 residual differences remain tracked and open.
4,424+ 82
chitchat and report dialog exchanges implemented
The complete library, reimplemented from the original format.
77of 81
reviewed checklist tasks verified with evidence
Counts reviewed tasks, not working features or percent-complete software.
Not finished
- 1:1 compatibility with the original service is not yet verified, and is not claimed.
- No robot has yet completed a full over-the-air upgrade through Phoenix.
- Notification delivery over the native socket is implemented but unverified.
- Several surfaces in the console are read-only, and are labelled as such.
Install
Run it yourself
Phoenix is a Node.js workspace with one external dependency. Clone it, point your robot at it, and the console is served on the same host.
Behind a reverse proxy the console is static files and /api is proxied to the account service. A worked nginx configuration ships in deploy/nginx/.
Clone and install
$
git clone <your-phoenix-remote> && cd phoenix && npm install
Start the account service
$
npm run start:account
Open the console
$
http://localhost:7016/app
FAQ
Questions
Is this affiliated with Jibo, Inc. or any current rights holder?
No. Phoenix is an independent, non-commercial project with no affiliation to, endorsement by, or relationship with Jibo, Inc., its successors or any current rights holder. Jibo is used only to name the hardware this software talks to.
Does it ship any of the original software?
No binaries, no proprietary code. The original service is used strictly as a behavioural reference. Only plain-text data the robot already carries — grammars, dialog files, word lists and manifests — is vendored.
Where does my data go?
Onto the machine you installed Phoenix on, and nowhere else. There is no Phoenix-operated server, no telemetry and no analytics. Map tiles are the one optional exception, and the location picker degrades to manual entry without them.
Does my robot need to be modified?
It needs to be pointed at your server instead of the original one. Phoenix implements the endpoints the robot already calls, and authenticates it with the credentials it already holds.
Is it finished?
No, and the Status section above is the honest version. Conversation works end to end today. Full behavioural comparison against the original still fails, and every gap is tracked in the open.
What does it cost?
Nothing. There is no company, no subscription and nothing to buy. You run it on your own hardware, and the electricity bill is between you and your robot.
Bring yours back
If you already have Phoenix running, the console is one click away. If you don't, everything you need is in the repository.