Last update Sept 21, 2026

Work in Progress

Test Environment: Windows and macOS, with BLE as the primary connection method

Colonelpanic’s RMK + RynkBench vs. the MoErgo ZMK Experience

Made easy, as Colonelpanic provides 2 ready-to-flash UF2 firmware files for both the Glove80 and Go60. Alternatively, you can build your own.

Real-time configuration is a HUGE advantage of RMK. No firmware builds or flashing for every change, just make the change and see it instantly. It’s a game changer compared to MoErgo Layout Editor. I have not been able todo Real-time updates over BLE. (Windows)

ZMK Studio is very limited in many respects, and development is extremely slow! Having to compile firmware files yourself (the traditional way) for MoErgo is a no-go for most users.

Colonelpanic’s RynkBench is still relatively early in its development, and the current user experience can sometimes feel frustrating or cumbersome. For many users, this may be a significant factor when deciding whether to use Colonelpanic’s RMK build in its current state.

It can be done, but Vial doesn’t offer feature parity with RynkBench, particularly for advanced features such as custom or conditional RGB and battery-based configuration. These limitations come from the Vial protocol itself. That said, Vial support is still a huge advantage for QMK users. Not working out of the box.

Similar, where Layout Editor is better in adjusting the UI to OS.

Can be done technically but requires work

With the option to use Vial, this could potentially be a good choice for beginners looking for a simple and straightforward experience. Similar to what Keychron has done for ZMK with Launcher. Does not seem to be supported out of the box and still requires work on the rmk side.

Currently limited in Rynchbench. Only a few key languages are supported, whereas the MoErgo Layout Editor supports a much broader range of locales.

Similarly, RMK has some features that feel easier than ZMK, such as “Morse” that combines hold-tap and tap-dance

Config is based on a TOML file / Layout Editor uses JSON

Better in Colonelpanic’s RynkBench. Far Less complex than in ZMK. Bilateral HRM and Autoshift can be implemented as simple profiles, making them significantly easier to configure and tune. No finger layers, no double hold-taps and macros.

Assistants: Swap a layout to Colemak-DH or other alpha

Colonelpanic's RynkBench Assistant search/replace feature (no aptmak blue)

Colonelpanic's RynkBench Assistant search/replace feature

In Advanced, Usage, Health

Super advanced use cases, like inxi and doc machette

I guess limited from an UX perspective and requires build your own

Seamless keymap migration between the Go60 and G80.

Available in Rynchbench - IN DEVELOPMENT, did not work for me, also not able to export and import Go60 toml files

ZMK has known BLE compatibility issues with certain chipsets, such as Intel and RealTek. This requires use_2m_phy=false and is similar to ZMK.

Slightly slower to reconnect when the PC wakes from standby compared to the default MoErgo ZMK factory firmware. NOTE from colonelpanic: reconnection speed, RMK uses a slightly slower interval but this can be changed in toml if manual build (200 ms)

Auto connect to BLE when you unplug USB: Automatically reconnecting to BLE after unplugging USB is an annoyance. With the MoErgo factory firmware, the connection is transferred to BLE almost instantly to the last BLE profile. I normally use the keyboard wirelessly and only connect USB for charging or management, so I would prefer the keyboard to stay disconnected rather than automatically switch back to BLE.
Note from colonelpanic: I don't really like "auto connect".

Looks similar, see the BLE tap in this sheet.

https://docs.moergo.com/glove80-user-guide/operating-glove80-wirelessly/#advanced-usage-temporarily-disconnecting-an-active-ble-connection

Looks like supported out of the box? Many have asked for this at MoErgo.

Tap Magic key is not supported so you need to hold. Other behavior is replicated.

Colonelpanic’s RynkBench supports JSON import and includes a preset MoErgo Magic Layer for a similar experience. However, RynkBench and RMK behaviors are quite differently from ZMK.

User experience for MoErgo users (transition to RMK)

See BLE reconnect and Magic tap

My experience is pretty good, even with RGB turned on.
ZMK: More mature and extensively proven for low-power wireless keyboards.
RMK: Potentially very competitive, with strong low-power optimizations and promising results.

More capabilites than PR36. example key blink and animations

See RGB tap. RGB bringhtness and colors (hex) are very different and not aligned with my ZMK MoErgo colors in TailorKey

Exact same Magic layer is possible, I demonstrated that with Glove80

Touchpad Smooth scrolling (ZMK has some capability)

Todo - colonelpanic tested and seems to works

Section E: Firmware Build & Developer Workflow

Requires two different U2F files but real time updats does not require a flash and is a huge PRO

Debugging is easier in some areas—for example, tuning HRM timers is straightforward thanks to real-time updates. However, debugging other issues, such as RGB problems or unexpected behavior, might be more difficult.

CLI update etc is better and can be scripted

Different! AFAIK The realtime aspect requires to reserve blocks of memory to add/change things. This might give challenges for larger keymaps with 32 layers.

Much smaller and not much activity on RMK Discord

Less and related to community

Amazing compared to ZMK! ZMK is really SLOW!!

It's great, but is this a custom RMK Fork?