DIY hardware + embedded software
Hardware you can hack. Software you can remix.
DIY electronics, custom boards, and embedded software for projects that live beyond the breadboard.
For makers, hackers, embedded developers, educators, students and small labs.
Build it. Understand it. Keep it running.
Browse
Start with the board. Choose what it does.
Six areas to grow into. Categories are here first; the boards that fill them are being built now.
Hackable boards and drop-in modules built to be reprogrammed, not replaced.
In development Kits & ProjectsEverything needed to build one complete thing, with the documentation to match.
In development Sensors & InterfacesWays to measure the world and talk to the rest of your bench.
In development Power & Field SystemsRunning on batteries, solar or a long cable, a long way from a desk.
In development Tools & TestSmall practical instruments for building, probing and fixing.
In development AccessoriesCables, carriers, enclosures and the parts that hold a project together.
In developmentHow it fits together
One board. Several jobs. Over several years.
Software is not an afterthought here. The same hardware can become a different useful tool when you load a different firmware profile - and it keeps getting better after you own it.
-
Choose hardware
Pick the board or module that has the pins, power and physical shape your project needs.
-
Load a firmware profile
Flash a profile to give it a behaviour: log data, drive something, sense something, test something.
-
Customise it
Change the configuration, edit the examples, or write your own. The documentation tells you where the seams are.
-
Keep improving it
New profiles and fixes arrive as updates. The board you bought first can do things it could not do on day one.
Useful hardware should not become obsolete just because the first idea changed. That is the whole reason the software side exists.
New and featured
On the bench
First boards are on the bench
Nothing is listed yet, and we would rather show you nothing than show you something that is not real. Development notes go up as work happens.
Software
A firmware profile changes what the board is
A profile is a firmware build plus its configuration and its documentation. Swap the profile and the same hardware stops being one instrument and starts being another.
Every profile will say plainly which hardware it runs on, how mature it is, what it cannot do yet, and how to get back if a flash goes wrong. Where there is no release yet, it will say so instead of offering a download that does not exist.
Learn by building
Guides that assume you want to understand it
Buying the board is the easy part. The guides are where a project actually gets finished - and where you learn enough to change it later.
Ecotech
Build it. Understand it. Keep it running.
Ecotech here means design intent, not a badge. These are the things we are trying to get right - not claims about outcomes we have not measured.
Long useful life
Hardware that stays capable because the software keeps moving.
Repairable where practical
Accessible parts, sensible connectors, and notes on what can be replaced.
Modular by default
Small pieces that combine, so one change does not mean a new build.
Documented honestly
Pinouts, limits and known problems written down, including the awkward ones.
Reuse over replace
A retired project should become parts for the next one, not landfill.
Open development
Source, examples and issues will live on GitHub
There is no GitHub organisation to link to yet. When there is, this is where it will point - and this section will name real repositories rather than promises.
The plan is straightforward: firmware source and example applications, an issue tracker you can actually file a bug in, tagged releases with notes, and enough contribution guidance that a pull request is worth your time.
Stay in the loop
Hear about the first releases
No signup form is running yet, because we will not put up a form that quietly goes nowhere. Until one is live, the updates page is the honest version - and email works.