Manifesto
Ideas are meant to be felt.
Vibe coding for hardware. Tell PAL what you want to make — it writes real code for real devices. No soldering, no embedded C, no guesswork.
Software got a creative layer. Hardware never did.
Anyone can describe an app and watch it appear. Hardware stayed gated behind soldering irons, datasheets, embedded C, and board bring-up. The idea was never the hard part — the apparatus was. Palpable removes the apparatus so the idea can be felt.
Describe the behavior, not the wiring.
You should be able to say what you want a device to do — sense this, react that way, show or say the result — and have it work. PAL, our AI, writes the actual code, deploys it to a Raspberry Pi, and runs it. No breadboarding, no pin maps, no embedded toolchain.
Real code, on a real device, that you own.
This is not a simulation or a wiring diagram you take away and figure out yourself. Scripts are TypeScript and run locally on the device, so they keep working when the internet does not. Every project exposes REST and WebSocket APIs and a CLI. You are never locked out of your own logic.
Open hardware, not a walled garden.
Palpable runs on commodity Raspberry Pi hardware and any I2C/Qwiic module you can buy — 76 are certified and hardware-tested, and the rest still connect. No proprietary boards, no single-vendor catalog. Plug a sensor in and PAL detects it.
We do not pretend to be an ECAD tool.
Palpable does not design custom printed circuit boards. If you need a manufacturable PCB, you still want KiCad, Altium, or Flux. But most projects never needed a board — they needed a working device. That is the gap Palpable fills, honestly.