Compare

Palpable vs Schematik

Both turn plain language into working hardware. The difference is what you get at the end — generated code you still have to run, or a live device you can talk to.

Palpable
Schematik
What you describe it to
PAL, in plain English or by voice
A chat-driven IDE
What comes out
A running device — code deployed and executing on a Pi
Source code, a wiring diagram, and a parts list
Hardware
Any I2C/Qwiic module — plug it in, PAL detects it
ESP32 / Arduino / Pico-class boards
After it ships
Over-the-air updates with automatic rollback; PAL can see and fix live state
You flash and debug the board yourself
Runs offline
Yes — scripts run locally on the device
Depends on your own firmware
Availability
Join the waitlist
Closed beta

When Schematik is the better choice

If you specifically want to own and hand-edit firmware for an ESP32 or Pico — and you are comfortable flashing and debugging boards yourself — a code-generating IDE like Schematik fits that workflow well.

If you just want generated source to drop into your own embedded toolchain, that path is enough. But if you want to describe a behavior and have a real device run it — with sensors auto-detected, OTA updates, and PAL watching the hardware — that is what Palpable is built for.

Questions

Is Palpable an IDE like Schematik?

No. Schematik generates code and diagrams you take away. Palpable runs the device for you: PAL writes the code, deploys it to a Raspberry Pi, and keeps it updated over the air.

Do I need to know electronics to use Palpable?

No. You connect Qwiic modules and describe what you want. PAL detects the hardware and writes and runs the code. No soldering or embedded C required.

Can I still get to the code?

Yes. Scripts are TypeScript and every project exposes REST and WebSocket APIs plus a CLI, so you are never locked out.

Make something you can hold.