Pick your blocks.
Choose the functions you need. Get matching electronics, a battery and an enclosure, as a kit or ready assembled.
A new hardware concept, taking shape
Give your ideas
a physical side.
Cameras, buttons and sensors that connect to the software you build with AI. Pick your blocks. Tell them what to do.
Compatible hardware. Your software. Endless starting points.
A little hardware. A lot of possibility.
Illustrative modules
CameraSee something.
MotionSense something.
“Let me know when
my bike moves.”
The concept
The physical part,
already figured in.
Building an app with AI is becoming easier. Adding a physical device should be, too. HardwareBlocks brings compatible electronics, simple setup and a software connection into one kit — so you can focus on your idea.
Make the connection.
Pair through the planned HardwareBlocks app. Use Wi-Fi or Bluetooth to connect your device to your software.
Build it your way.
Use ChatGPT or Claude to write your application, define its behaviour and design its interface. API and MCP access are part of the platform concept.
What could you build?
Same building blocks.
Very different ideas.
Four starting points. Each shows a physical input, a connection and an application you could make your own.
Build concept
A little window into your fridge.
Check the latest picture before you shop. Capture the contents after the door closes and build your own food overview.
Build concept
Know when your space is free.
Turn a parking-space sensor into a simple availability display. Define the distance that means a car is parked.
Build concept
A heads-up when your bike moves.
Arm a small device on your bike and get a movement alert through a connected phone or gateway. Set your own sensitivity.
Build concept
SkiTik. Give every turn a story.
Take motion sensing onto the slopes. A boot-mounted device supplies data for an app that explores your turns and movement.
These are proposed builds, not products available to order. Illustrations show the idea, not final hardware.
Try the idea
One input.
Your kind of output.
Select a build and trigger an example event. This is the connection we want to make simple: something happens in the real world, and your software responds.
Interactive simulation. No device or AI service is connected.
Fridge cameraSimulation
Your app
Ready for a snapshot
Close the door to update the fridge overview.
Your starting prompt
“Show the latest fridge photo and the time it was captured.”
Enclosure
Sensor
Battery+
Your preferred starting point
A kit to tinker with.
Or ready to connect.
The same idea, with two ways to get started. Choose compatible parts to assemble yourself, or a device assembled for you.
Get to know your hardware as you connect the module, battery and enclosure.
Proposed formats. Final components and assembly are still being developed.
A few useful answers
Built around your idea.
Is HardwareBlocks available yet?
HardwareBlocks is a concept in development. The kits, pairing app and API/MCP platform described here are planned. There are no orders, prices or delivery dates on this site.
Do I need to know how to code?
The idea is to use ChatGPT or Claude to help write and adapt your application. You still decide how it should work and test the result. HardwareBlocks aims to take care of the electronics and device connection.
Will every device work anywhere?
Connection depends on the build. Wi-Fi needs network coverage. Bluetooth needs a nearby phone or gateway, and remote alerts need that connection to reach the internet. Battery life, range and environmental suitability depend on the final hardware.
What do API and MCP add?
An API gives your application access to device data and supported actions. MCP is intended to expose supported functions to compatible AI tools. The exact interfaces and permissions still need to be developed.