Compare
Palpable vs Atech
Both pair AI with hardware so you can build by describing. The split is openness: Atech generates firmware for its own proprietary modules; Palpable runs on any I2C/Qwiic sensor you can buy.
When Atech is the better choice
If you want a single curated kit where the hardware and AI are designed together out of the box — and you are happy staying inside one vendor’s module ecosystem — Atech’s bundled approach keeps things simple.
If a fixed proprietary kit covers everything you will ever build, that simplicity is a real plus. But if you want to grab any off-the-shelf Qwiic sensor, plug it in, and have PAL detect it and run your idea on open hardware, Palpable keeps the catalog — and your code — open.
Questions
Is Palpable locked to specific hardware like Atech?
No. Palpable works with any I2C/Qwiic module — 76 are certified and tested, and uncertified ones can still connect. You are not tied to a single vendor’s parts.
Do I own what gets built?
Yes. Scripts are TypeScript and every project exposes REST and WebSocket APIs plus a CLI, so your logic and data are portable.
Do I still get a guided, kit-like experience?
Yes. PAL handles detection, code, and deployment, and certified module packs give you a curated starting point without the lock-in.