PAGES
← all tools
◆ Hacking Hardware

HydraBus

v0.12 open-source

Free plan: not checked yet · Open source: yes

Open source C firmware for HydraBus v1 hardware hacking board, enabling protocol analysis and hardware interaction.

What you can do now

Checking Plays…

Summary

HydraBus is an open-source hardware hacking board with accompanying firmware, HydraFW, that talks to a target device's SPISPISerial Peripheral Interface, a synchronous communication bus standard used to connect microcontrollers to sensors, flash memory, and other peripherals at short range; cyber tools use it to read or write firmware on embedded devices., I2C, JTAGJTAGA hardware debugging standard (IEEE 1149.1) that exposes a chip's internal state through a small set of pins, letting cyber tools read memory, set breakpoints, and flash firmware without touching the running OS., CAN bus, and smartcard interfaces for probing and manipulation. The board itself is a physical purchase, but the firmware that drives it is free and open, built in native C, flashed onto the board and then driven from a VT100-style console over a serial connection rather than through any GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands.. This puts it in the hands of hardware hackers and embedded security researchers who need to talk directly to a chip's low-level buses rather than analyze software running on a general-purpose OS. It sits in the same space as multi-protocol hardware debugging tools, offering one board and firmware base instead of separate adapters per protocol. First launched in 2014, it remains active, with firmware releases adding features like SPI three-wire mode and timed smartcard reads alongside CI/CD via GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure..

Open source C firmware for HydraBus v1 hardware hacking board, enabling protocol analysis and hardware interaction.

How HydraBus helps

What is actually being sent over this chip's bus when the target boots or runs?

connects to the SPI, I2C, or CAN lines directly and reads or injects data live, so traffic between chips shows up as it happens rather than as a simulation

Can this smartcard be read before its response times out?

issues a timed read against the card so responses are captured within a set window instead of hanging or missing fast replies

Is this chip's JTAG interface actually accessible from the board?

drives the JTAG lines directly from the console, so probing for taps and boundary-scan access happens without a separate debug adapter

Can a device be talked to when only two SPI lines are broken out?

switches into three-wire mode so a target with a shared data line can still be probed without rewiring the bus

What does a device answer when sent specific raw commands on I2C or SPI?

sends hand-crafted byte sequences over the chosen protocol from the console and prints back exactly what the target returns

Is one board enough, or does each bus need its own adapter?

exposes SPI, I2C, JTAG, CAN, and smartcard interfaces from the same firmware, so switching protocols is a console command rather than swapping hardware

all 10 features, with the evidence for each →

Languages

Not documented

Device

HydraBus HydraBus
image © HydraBus · mirrored to the media CDN · original ↗

Spec · announced HydraBus v1.0 Rev1.5

processor
ARM Cortex-M4F STM32F405 up to 168 MHz, 1 MB flash
interfaces
2x USB-C (1 OTG, 1 device/host), SWD debug connector, 44 I/O breakout
storage
microSD slot, 4-bit SD/SDIO
radios
NFC via HydraNFC shield (optional add-on)

from the vendor's spec page ↗

from
not yet captured
no priced SKU yet
stock
not yet checked
vendor store not machine-readable
status
announced
HydraBus v1.0 Rev1.5
latest firmware
v0.12
HydraBus · Jan 30, 2026

Availability

announced
not yet captured
no source captured
pre-order
not yet captured
no source captured
ships
not yet captured
no source captured
discontinued
not yet captured
no source captured

A slip is called out here the day the vendor's own delivery estimate moves past the promised window. A "coming" milestone is the vendor's own wording, read off the page it links to — never a date we inferred.

Price

configuration generation launch today status source
HydraBus v1.0 Rev1.5 HydraBus v1.0 Rev1.5 — — announced price not yet checked
no price captures yet

Device history

  1. HydraBus v1.0 Rev1.5 news Jun 1, 2024 · source ↗ press

    HydraBus v1.0 Rev1.5 plus HydraNFC Shield v2 R1.5 kit back in stock after a chip shortage.

  2. HydraBus v1.0 Rev1.5 news Jan 8, 2024 · source ↗ press

    HydraBus v1 Rev1.5 with USB-C announced in stock worldwide on DigiKey.

Features

10 capabilities · 3 backed by code, an API document or a real run

Built from HydraBus's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What HydraBus offers you

  • Command-line interface7
All capabilities 10 capabilities
Multi-protocol hardware communication verified Provides open-source C firmware for the HydraBus v1 board that enables communication and analysis across multiple hardware protocols. 31 releases · 5 other sources · first seen Oct 2014

Also counts toward: Command-line interface

release 31 total

  • Adds make flash Makefile target for convenient firmware flashing v0.12 · Jan 2026 · source · release history
  • Initial support for SPI BIDIR (3-wire) mode in the console interface v0.12 · Jan 2026 · source · release history
  • Adds timed read / read with timeout feature for smartcards and other interfaces v0.12 · Jan 2026 · source · release history
  • Adds timed read capability for smartcard interactions v0.11 · Mar 2023 · source · release history
  • Adds -hd option for JTAG and 3-wire modes to enable high-density data dump output v0.11 · Mar 2023 · source · release history
  • Adds BBIO SDIO frequency switch to allow dynamic clock rate adjustment during SDIO card communication v0.11 · Mar 2023 · source · release history

docs

  • Open source C firmware for HydraBus v1 hardware hacking board, enabling multi-protocol communication and hardware analysis.
  • Open source C firmware for HydraBus v1 hardware hacking board, enabling protocol analysis and hardware interaction.

command line

NFC Tag Emulation verified Emulates NFC tags such as Mifare 1K and ISO14443A for testing or interaction purposes. 4 releases · 1 other source · first seen Nov 2015

Also counts toward: Command-line interface

release

  • Adds emul-mf-ul command with optional filename for Mifare Ultra Light tag emulation 13.10.2016 · Sep 2016 · source · release history
  • Adds emul-mf-ul command with optional filename support for Mifare Ultra Light tag emulation 0.8 · Sep 2016 · source · release history
  • Adds emul-mf-ul command for Mifare Ultralight Emulation. 0.7 · Apr 2016 · source · release history
  • Adds emul-mifare and emul-3a commands for NFC tag emulation (Mifare 1K & ISO14443A) 0.6 · Nov 2015 · source · release history

command line

Logic Analysis shipped Captures logic signals on up to 16 channels at up to 1MHz, compatible with standard analysis tools. 4 releases · first seen Nov 2015

release

  • Increased maximum hexdump capacity to 2^32 bytes for larger memory captures. 0.9 · Sep 2018 · source · release history
  • Added SUMP mode autodetection for Sigrok and OLS compatibility without prior setup. 0.9 · Sep 2018 · source · release history
  • Added trigger mode on all supported modes to capture specific signal events. 0.9 · Sep 2018 · source · release history
  • Adds sump mode (Logic Analyzer up to 1MHz 16chan) compatible with ols-0.9.7.2 and sigrok 0.6 · Nov 2015 · source · release history
SPI Protocol Support verified Supports serial peripheral interface (SPI) communication with configuration options for address, dump file, sector count, and bus selection. 3 other sources · first seen Jan 2026

Also counts toward: Command-line interface

command line

UART Sniffing shipped Captures and displays UART traffic via a bridge command in uart mode. 3 releases · first seen Nov 2015

Also counts toward: Command-line interface

release

  • Added \xx escape sequence support in freeform strings for raw data injection. 0.9 · Sep 2018 · source · release history
  • Adds hd console command for hex/ascii dumps of SPI, I2C, UART, and wire data 0.8 · Sep 2016 · source · release history
  • Adds UART sniffer capability via the bridge command in uart mode 0.6 · Nov 2015 · source · release history
Bootloader Support shipped Supports USB DFU boot mode activated via hardware button during reset. 3 releases · first seen Feb 2015

Also counts toward: Command-line interface

release

  • Adds debug test-rx CLI subcommand and tx_bench.py script for benchmark testing 0.8 · Sep 2016 · source · release history
  • Adds SD script support with initscript file at root of sdcard for automatic startup execution 13.10.2016 · Sep 2016 · source · release history
  • Added USB DFU boot mode activated by pressing UBTN at PowerOn/RESET 0.5 · Feb 2015 · source · release history
Signal Generation shipped Provides configurable output signals including DAC voltage/noise/waveforms and PWM control with real-time feedback. 2 releases · first seen Feb 2015

release

  • Added configurable DAC command for channels 1 and 2 in raw, volt, triangle, or noise modes with feedback 0.5 · Feb 2015 · source · release history
  • Added configurable PWM command supporting frequency (1Hz-42MHz) and duty cycle (0-100%) with real-time feedback 0.5 · Feb 2015 · source · release history
Frequency and Duty Cycle Measurement shipped Measures signal frequency (128Hz to 84MHz) and duty cycle in Console mode. 1 release · first seen Sep 2016

Also counts toward: Command-line interface

release

  • Adds measure-freq command to measure frequency & Duty Cycle from 128Hz to 84MHz 0.8 · Sep 2016 · source · release history
SD Card Scripting shipped Executes automated commands from an init script on the SD card during startup. 1 release · first seen Sep 2016

release

  • Adds initscript file support at root of SD card to execute commands on startup 0.8 · Sep 2016 · source · release history
Session Logging shipped Records terminal sessions to the HydraBus SD card for later review. 1 release · first seen Feb 2015

Also counts toward: Command-line interface

release

  • Added Log command to record Terminal sessions to HydraBus SD card via logging on/off/sd subcommands 0.5 · Feb 2015 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for HydraBus, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail HydraBus puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

12 entries

  1. January 20261
  2. March 20231
  3. September 20201
  4. September 20181
  5. September 20162
  6. April 20161
  7. November 20151
  8. February 20151
  9. December 20141
  10. October 20142
    Show

    12 entries

    Project health

    Issue, contributor and maintainer activity in hydrabus/hydrafw, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 −1 vs prior 12 months
    2. Maintainers 0 +0 joined · −1 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 3.8 hours
    6. Open backlog 2 of 63 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 2
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.