This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Hardwave
Simulate hardware failures before they cost a respin
Know your motor will overheat, your battery will sag, or your drivetrain won't couple, before you spend weeks and a BOM finding out on the bench. Hardwave lets you compose your actual hardware system in Python and stress-test it in software first. As real bench data comes in, fold it back into the model so every iteration starts smarter than the last one.
If you're building hardware, you know this pattern: you size a motor, order the board, assemble everything, flip it on, and find out the drivetrain draws twice the current you budgeted for, or the thermal path you didn't think about is the thing that actually fails. Now you're waiting on another spin, and every week of that wait is runway.
Software engineers don't live with that loop. We have tests, hot reload, and tools that tell us something's wrong in minutes, not after a multi-week board turnaround. I kept wondering why more of that feedback couldn't move earlier, before the BOM, not after it.
That's why I built Hardwave.
Hardwave is an open-source Python framework for composing and simulating full electromechanical systems, not just a circuit or a single subsystem, but the electrical, mechanical, and thermal pieces together as one graph. Getting started is as easy as...
pip install hardwave
Under the hood, each component (a motor, a driver, a controller, a thermal path) exposes typed ports and its own solver, and you connect them into a simulation graph. That means you can model your actual product, your actuator, your custom mechanism, your power stage, not just generic reference circuits.
As an example: model a battery, an H-bridge, a DC motor, and a PID controller, then simulate how the system responds under load, current draw, voltage sag, control response, before a single part ships to your bench.
Hardwave is early. The standard library today is generic building blocks (motors, drivers, sensors, thermal elements), and the part I'm most excited about long-term is closing the loop with real hardware: once you've got a prototype on the bench, the same graph should let you fold in your measurements and get a model that's sharper for the next iteration, instead of bench data dying in a notebook.
If you're a technical founder or engineer bringing up your own hardware, especially anything with actuation, motors, or a multi-domain system where "it worked in isolation but not together" is a familiar sentence, I'd genuinely love to hear what broke on your last spin and whether this would've helped.
No comment highlights available yet. Please check back later!
About Hardwave on Product Hunt
“Simulate hardware failures before they cost a respin”
Hardwave was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #72 on the daily leaderboard. Know your motor will overheat, your battery will sag, or your drivetrain won't couple, before you spend weeks and a BOM finding out on the bench. Hardwave lets you compose your actual hardware system in Python and stress-test it in software first. As real bench data comes in, fold it back into the model so every iteration starts smarter than the last one.
Hardwave was featured in Hardware (11.4k followers), Developer Tools (515.9k followers), Artificial Intelligence (473.7k followers), GitHub (41.3k followers) and Vercel Day (26 followers) on Product Hunt. Together, these topics include over 212.9k products, making this a competitive space to launch in.
Who hunted Hardwave?
Hardwave was hunted by david mungai. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Hardwave stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
david mungai
Hi everyone! I'm David, the founder of Hardwave.
If you're building hardware, you know this pattern: you size a motor, order the board, assemble everything, flip it on, and find out the drivetrain draws twice the current you budgeted for, or the thermal path you didn't think about is the thing that actually fails. Now you're waiting on another spin, and every week of that wait is runway.
Software engineers don't live with that loop. We have tests, hot reload, and tools that tell us something's wrong in minutes, not after a multi-week board turnaround. I kept wondering why more of that feedback couldn't move earlier, before the BOM, not after it.
That's why I built Hardwave.
Hardwave is an open-source Python framework for composing and simulating full electromechanical systems, not just a circuit or a single subsystem, but the electrical, mechanical, and thermal pieces together as one graph. Getting started is as easy as...
Under the hood, each component (a motor, a driver, a controller, a thermal path) exposes typed ports and its own solver, and you connect them into a simulation graph. That means you can model your actual product, your actuator, your custom mechanism, your power stage, not just generic reference circuits.
As an example: model a battery, an H-bridge, a DC motor, and a PID controller, then simulate how the system responds under load, current draw, voltage sag, control response, before a single part ships to your bench.
Hardwave is early. The standard library today is generic building blocks (motors, drivers, sensors, thermal elements), and the part I'm most excited about long-term is closing the loop with real hardware: once you've got a prototype on the bench, the same graph should let you fold in your measurements and get a model that's sharper for the next iteration, instead of bench data dying in a notebook.
If you're a technical founder or engineer bringing up your own hardware, especially anything with actuation, motors, or a multi-domain system where "it worked in isolation but not together" is a familiar sentence, I'd genuinely love to hear what broke on your last spin and whether this would've helped.
Hardwave is MIT licensed and fully open source.
Website: https://hardwave.dev
GitHub: https://github.com/HardwaveDev/hardwave
I'll be here all day to answer any questions you may have, cheers!