Seven years of WeAct Studio

2 min readUpdated Studio

Seven years in, our schematics, outlines and 3D models are public. This is how the product line grew.

WeAct Studio boards and a debug probe on a workbench

In December 2019 we created our first repository. It did not contain one of our boards — it was a fork of somebody else's STM32 HID bootloader. The MiniSTM32F4x1 only showed up a month later.

Seven years on, that first product line is still shipping and the repositories have been rebuilt a few times. This post is not about the philosophy. It is about what we publish.

What is actually published

The repository layout is the same almost everywhere:

FolderContents
HardwareSchematic PDF, board outline, STEP 3D model, Altium library
DocChip datasheets, display and sensor documentation
SDK / ExamplesVendor SDK ports and example projects
Soft / ToolsFirmware, flashing tools, host software

How the product line grew

There was never a roadmap. What shipped each year depended on who got stuck on what.

YearWhat shipped
2020MiniSTM32F4x1, BluePill+, MiniSTM32H7xx
2021LogicAnalyzerV1, RP2040 core board
2022WCH RISC-V (BluePill+ CH32), e-paper module, WCH BLE, ESP32-C3
2023MiniDebugger, STM32G431, CH32V003, WCH-LinkW
2024USB2CANFD V1, RP2350
2025PDPowerMini, RP2350B
2026PowerMonitor, USB2CANFD V2, LogicAnalyzerV2

A pattern shows up in that table. Core boards were settled by 2020; everything added since sits outside the board — instruments, interface modules, displays. Core boards have a low ceiling and plenty of competitors. Instruments and modules have to get analog behaviour, timing and firmware to agree, which is slow to build and hard to replace afterwards.

Who is actually using it

The crudest available signal is GitHub stars. Imprecise, but at least it exists:

  • MiniSTM32F4x1 — over 900
  • MiniSTM32H7xx — 500
  • E-paper module — over 430
  • BluePill+ — just over 200

None of that is an achievement. It does say one thing: people come back for these boards because the documentation and the design can be checked.


If you are using one of our boards and something is wrong, open an issue. Being told you are wrong is the least costly way to improve.