Skip to content

The Naya Create

The Naya Create is a split, low-profile ergonomic keyboard made of two halves, each with a round dock that holds one input module (Touch, Track or Tune), plus a Speedlink USB dongle in the box. This page covers what the pieces are, how they connect, the models and identifiers, where the manual's specifications and the filed hardware differ, which versions are in the field, and how the product came to be. The one thing to know first: the left half is the central of the pair; it holds the whole keymap and talks to the right half over a Bluetooth split link, so almost every tool talks to the left half.

At a glance

  • Two halves, each a complete device with its own nRF52840 radio SoC, USB-C port, small cell, power switch and firmware image.
  • The halves are bonded to each other over Bluetooth LE; the left half is the central and holds the keymap, LED maps and module configurations for both.
  • Three modules shipped (Touch, Track, Tune); they have no radio and talk to the half through 8 dock contacts.
  • Output goes to one host at a time: USB or one of four Bluetooth host slots.
  • The Speedlink dongle ships in the box, but no shipped firmware gives it a working role.
  • Last vendor release: NayaFlow 1.25.1 (2026-07-21) with keyboard firmware 3.41.0 and module firmware 2.3.3.

Tags on this site say how each fact is known (MEASURED, STATIC, DOC, INFERRED, REPORTED, OPEN); see the home page for the legend. Firmware versions are written 3.41.0 and 2.3.3 here; the wire form is explained on Firmware versions.

Manual

Create, Touch, Tune and Track user manuals v1.1.0 (PDF); every version is listed on Manuals.

What the Create is

The Create is a split, low-profile ergonomic keyboard: two separate halves, each with a round module dock that holds one input module DOC78. Each half is made of three hinged sections: the main body, the outer "wing" (two key columns, the power switch and a light bar) and the "dock" (the module ring with three thumb keys) DOC78. There are 74 keys, 37 per half (24 on the body, 10 on the wing, 3 on the dock), plus a 7-LED light bar on each wing; NayaFlow 1.25.1 draws the same 74 keys and 14 side LEDs DOC STATIC7112. Details are on The keyboard half and Layout and positions.

The maker of record is Naya B.V. of Groningen, the Netherlands; the underside engraving reads "Designed by Naya in the Netherlands" and "Made in China" DOC2. Manufacturing was done by an ODM, Dongguan Boen Intelligent Technology Co., Ltd., named as manufacturer and factory on all three FCC test reports; the same company made both PCB antennas DOC13.

The firmware is a closed-source custom fork of ZMK by the vendor's own statements (2023), and the vendor published no protocol documentation DOC212345; see ZMK. The manual calls the backlight "Reprogrammable RGB", and marketing called the module-bay ring light "A-RGB Status Lights" DOC744. The product was marketed with Qi wireless charging for modules, multi-device Bluetooth, tenting and sculpted keycaps DOC744.

The pieces

Piece What it is Radio Microcontroller Power FCC ID USB PID Page
Left half The central: holds the keymap for both halves BLE (split link and host); its filing also certifies a 2 Mbps "2.4G SRD" mode Nordic nRF52840 USB, or a docked module; 50 mAh cell bridges module swaps 2BQ4V0825CRL 0x0064 Half
Right half The peripheral: reports its keys to the left BLE (split link); its filing also certifies a 2 Mbps "2.4G SRD" mode Nordic nRF52840 as the left 2BQ4V0825CRR 0x00C8 Half
Naya Touch Glass touchpad module none ST STM32F411 own pack, charged in the dock or on Qi none none Touch
Naya Track 40 mm trackball module with four buttons none ST STM32F411 as the Touch none none Track
Naya Tune Knurled dial with a touch surface and haptics none ST STM32F411 as the Touch none none Tune
Speedlink dongle USB-A receiver, NAYA-100-1 2.4 GHz: its filing certifies only a 2 Mbps "2.4G SRD" mode; the manual says Bluetooth 5.4 Nordic nRF52840 USB bus power 2BQ4V0825DG 0x012C Dongle

Each half is a complete device: its own USB-C port, its own Nordic nRF52840 radio SoC with native USB, its own small internal cell, its own power switch and its own firmware image; the left and right images differ in size in every release (for 3.41.0, 328 880 bytes left and 226 000 bytes right) DOC STATIC1215. The three modules that shipped are the Naya Touch (glass touchpad), the Naya Track (40 mm trackball with four buttons) and the Naya Tune (knurled dial with a touch surface and haptic feedback) DOC9101131.

Modules have no radio: each is an STM32F411 microcontroller with a Qi wireless-charging receiver and a battery, and it talks to the half through the dock contacts. None has an FCC ID of its own; they are photographed inside the two halves' filings, and the grantee has exactly three IDs DOC14.

The Speedlink dongle (model NAYA-100-1) ships in the box; it is its own nRF52840 radio with its own FCC ID (2BQ4V0825DG) and ISED number (34320-0825DG) DOC735. The radio the filings certify differs from the manual's wording: both halves' FCC filings carry a separate "2.4G SRD" 2 Mbps test report besides BLE, and the dongle's SAR report names only "2.4G SRD", while the manual says "Speedlink Connection: Using Bluetooth v5.4" DOC137. Whether shipping firmware ever uses the SRD mode, on the halves or the dongle, is OPEN (details). No working role for it has been demonstrated with shipped firmware: it enumerates on USB but does not answer the halves' protocol (measured on the owner's dongle, 2026-09-11) MEASURED, no NayaFlow release carries a firmware image for it and no release note through 1.25.1 enables it STATIC DOC1213. The vendor's NayaFlow 0.1.0 note reserved a host slot "for future BLE dongle support" DOC13. A third party relays vendor statements that the dongle was "not yet active" and "coming soon"; those words are in no primary source we hold REPORTED20. See Speedlink dongle.

How the pieces connect

The two halves are bonded to each other over Bluetooth Low Energy (the "split link"): each half's pair table holds the other half's address, and the left half's Bluetooth status reports a live link to the right half at a 7.5 ms connection interval, latency 0 and a 4 s supervision timeout MEASURED (owner's board, 3.41.0, 2026-09-01 and 2026-09-08, cross-checked both ways).

Vendor text describes the same link: the BLE v2 firmware (3.35.4) promised "higher bandwidth between halves", 3.39.4 onward (its beta note says 3.39.3) "reduced BLE traffic between halves", the v1.1.0 manual says to power the left half first "to ensure proper pairing between the keyboard halves", and a 2025 factory issue was "transmitting between the two halves"; the 2023 campaign page already said the halves talk to each other over RF and that in wired USB mode only the left half sends data to the computer DOC131483221.

With both halves on USB, the right half exposes no keyboard HID interface of its own; its key presses reach the host through the left half MEASURED (owner's board, 3.41.0, 2026-09-01). The left port also answers some requests addressed to the right half (dst 0x51): the firmware-version read reaches the right half, but the Bluetooth identity reads (be/1008, be/1002, be/1005) sent to 0x51 on the left port answer for the left half, and requests for the left through the right port get no answer MEASURED (owner's board, 3.41.0, 2026-09-22). This routing runs over the split link: every measurement fits a radio link, and no wired traffic between the halves has been observed; each half has its own USB-C port and the Y-cable joins them only at its splitter MEASURED DOC INFERRED7. It worked even with the halves on different firmware: the left port read the right half's version (3.35.4) while the right half's own port returned empty payloads MEASURED (owner's board, left 3.41.0, right 3.35.4, 2026-09-20). Whether any shipped setup has a wired data path between the halves is open OPEN (details). See Split link and Transport.

Which sender byte a reply relayed from the right half carries is not recorded OPEN (details). Direct replies carry the answering half's own address in the sender position; NayaCore's port probe names aa 50 00 00 fe ... "ProtocolCDC Left detected" and aa 51 00 00 fe ... Right STATIC12.

Toward a host the keyboard is one Bluetooth device, the left half: NayaFlow's BLE v2 warning asks users to re-pair "NayaCreate Left" only, host device names are "NayaCreate BLE n" per slot, and on the owner's board the right half answers the Bluetooth status read with nothing and a Windows host paired one identity MEASURED STATIC DOC (3.41.0, 2026-09-08 and 2026-09-11)1213. A third-party BLE central likewise used one connection for the whole keyboard (also reported by createflow-dongle) and found one battery level only REPORTED20. Whether the right half ever advertises to, or bonds with, a host by itself is open OPEN (details).

USB and Bluetooth to the host

Output goes to one host at a time; the user picks the output (USB or a Bluetooth slot) from the System layer DOC87. Bluetooth offers four user host slots; the firmware status reports five profiles (0-4) and the stock keys select profiles 1-4 DOC MEASURED (owner's board, 3.41.0, 2026-09-10). The vendor's first notes reserved a fifth slot for a future dongle; the 2023 campaign promised Bluetooth "to up to five devices", and its FAQ "multiple Bluetooth devices plus one RF device via the included dongle" DOC1321.

In USB mode each half enumerates a CDC serial interface; on 3.41.0 the left half adds a HID interface, while on 3.28.7 each half exposes two CDC interfaces of which only one answers MEASURED (owner's board, 3.41.0, 2026-09-01; a second board, 3.28.7, 2026-09-19). The configuration channel over USB stays usable when output is switched to Bluetooth MEASURED (3.41.0, 2026-09-10). See USB and Bluetooth.

Configuration and firmware updates are USB only on 3.41.0. The vendor tool has no Bluetooth path at all: NayaCore links only Qt Core, SerialPort, Sql and ZeroMQ, and every device worker in it is a serial one STATIC12 (also reported by createflow-dongle). Over Bluetooth, a third party found HID, one battery level, device information and an idle vendor service that answers no configuration frame, with no DFU, SMP or UART service REPORTED20. The HID report map createflow-dongle reads over Bluetooth (its firmware carries a verbatim copy) is byte-identical to the left half's USB HID report descriptor in our own capture (keyboard with LED output, consumer control, mouse) REPORTED20 MEASURED (USB side: owner's board, 3.41.0, 2026-09-11).

The keyboard would not start Bluetooth pairing while powered over USB MEASURED (owner's board, 3.41.0, 2026-09-11); a third-party guide likewise says to keep it unplugged while pairing20.

A freshly opened port often loses its first frame: in 23 of 30 nayactl connections the first fe/1001 got no reply and the retry did, with both halves awake on USB MEASURED (3.41.0, 2026-09-01). Tools retry their first request (nayactl's connect handshake makes three attempts) STATIC17. Whether a sleeping half answers at all has not been captured (open question); see Transport.

Every power-on passes through the MCUboot bootloader: each half first appears at its bootloader USB PID for about 1 to 1.7 s, then at its application PID; when one half comes up and re-links, the central reboots through the bootloader too MEASURED (a second board, 3.28.7, 2026-09-19; owner's board, 3.41.0, 2026-09-22). See Bootloader.

The module dock

A module docks on either half; the same module reports a different dock address depending on the side, for example a Tune is 0x40 on the left and 0x41 on the right MEASURED (owner's board, 3.41.0, 2026-09-03; a second board, 3.28.7, 2026-09-19; also seen on the nayactl maintainer's board, 3.30.118). The dock is magnetic: each half's module bay holds 6 magnets, one on either side of the contact block and 4 more spaced around the circular bay MEASURED (owner's board, paper-clip test, 2026-09-23); the manual speaks of "magnets in the dock and on the bottom of the module" DOC78. The dock carries 8 contacts on both sides (spring pins on the half, flat pads on the module) and no USB data lines; the net names are UART, boot select, battery, 5 V feed, enable and ground DOC INFERRED1. Details on Module dock.

Power in one paragraph

The half's internal cell only bridges module hot-swaps; normal operation is powered from USB or from a charged docked module, so wireless use depends on the modules' batteries DOC7846. Modules charge in the dock when the keyboard has power, and on any Qi charger whether docked or not DOC79. Details on Power and batteries.

Roles of the two halves

The left half is the central of the pair: it holds the keymap for both halves, the LED maps for both halves, the module configurations for both docks and the module firmware store. The right half holds no keymap and reports no module-configuration slots; one layer-list write to the left restores lighting on both halves MEASURED (owner's board, 3.41.0, 2026-09-01 to 2026-09-20). The right half answers the status families on its own port (system, Bluetooth, module and dock reads), but NayaCore never sends it a keymap-family frame, so the left half is the only way in for layout changes MEASURED STATIC (3.41.0, 2026-09-11)12. A keymap-family read sent to the right half goes unanswered: 30/1009 got no reply (3.41.0, 2026-09-01) MEASURED, and NayaCore's per-command table marks every 30 command "Unsupported" on the right STATIC (Firmware differences); 30/1001 itself has not been sent there. See Keymap.

Models and identifiers

Item Value Evidence
Model, both halves NAYA-800-1(NAYA-CREATE); the registered HVINs add a side suffix, NAYA-800-1(NAYA-CREATE) L and ... R, as printed on the two labels and listed by ISED; the halves are also told apart by FCC ID suffix (CRL left, CRR right) DOC labels, BLE reports p10125
Model, dongle NAYA-100-1(Dongle) DOC DG RF report p10, UM1 p237
Equipment name on the filings "Ergonomic detachable wireless mechanical keyboard"; brand line "NAYA TECH, Naya Create" DOC CRL and CRR reports p1, p101
USB vendor ID 0x37D1 for every Naya device MEASURED STATIC owner's boards (3.41.0) and dongle, 2026-09-11; nayactl constants17
USB application PIDs 0x0064 left, 0x00C8 right, 0x012C dongle MEASURED STATIC as above
USB product strings "Naya Create Left", "Naya Create Right", "Dongle" MEASURED owner's boards and dongle, 2026-09-11
USB serial string per unit; it is also the hardware ID that fe/1004 returns and the key NayaCore uses for the device; values are not reproduced here MEASURED STATIC owner's board; NayaCore "HWID mismatch" string12

More on Regulatory records and USB.

Specifications: the manual versus the filings

Specification Manual v1.0.6 says Filings or measurement show Evidence
Size 212 x 118 x 18 mm most likely per half: the 1:1 label artwork of one half's underside is about 210 x 121 mm DOC INFERRED72
Weight 1.4 kg per half or per pair not stated OPEN (details) DOC7
Body, dock, wing "Aerospace Grade Aluminum" agrees; keycaps are polycarbonate DOC7
Switches Kailh CPG-1232, 0.45 x 0.42 mm pin variant agrees DOC7
Backlighting RGB 88 addressable LEDs on keys and light bars DOC MEASURED; see Layout
Bluetooth 5.4 the SIG listing's core-spec field reads 5.1 DOC76
USB 2.0 or newer (v1.1.0: USB 3.0) not tested DOC78
Internal battery "45mA", Li-ion a 50 mAh cell per half (3.7 V, 0.185 Wh) DOC12
Input voltage "4.2V" each half's input is rated 5 V DC 1.5 A on its label; 4.2 V reads as the cell's full-charge voltage DOC INFERRED2

The 2023 campaign spec sheet described the pre-production design as 205 x 120 mm, 17 mm total height (11.2 mm typing height) and 225 g per half DOC21. Module batteries in the filed samples are Tune 1000 mAh, Touch 700 mAh and Track 600 mAh (two 300 mAh cells in parallel); the vendor's website and the 2023 campaign spec sheet said 1500 / 800 / 800 mAh (1500 mAh for the Float), and the v1.1.0 module manuals 1500 / 1500 / 700 mAh; retail capacities are not confirmed DOC OPEN 11191021 (details). The full reading of the manual is on Manuals.

What is in the box

The v1.0.6 box list: a travel case, the keyboard, the Speedlink dongle, a 1 m USB Type-C Y-cable, one keycap/switch puller, three spare switches and two module spacers DOC7. The vendor's later help-center manual (v1.1.1, no public archive) describes item D as "Y-Cable/Two USB-C cables" DOC. Modules ship in their own boxes: "1x Naya Touch"; "1x Naya Track" plus "1x 40mm Trackball"; "1x Naya Tune" DOC91011. Supported host systems per the manual: Windows 10 and newer, macOS Ventura and newer, tested on Ubuntu 24.04 LTS DOC7.

Versions in the field

What Versions Evidence
Keyboard firmware seen on hardware 3.28.7 (a second board), 3.30.1 (the nayactl maintainer's board), 3.35.4 and 3.41.0 (the owner's boards) MEASURED owner's boards; nayactl pull request 519
Module firmware seen 2.1.2, 2.2.2 (nayactl maintainer) and 2.3.3 MEASURED19
Last vendor release NayaFlow 1.25.1 (2026-07-21), carrying keyboard 3.41.0 and module 2.3.3; engine NayaCore 6.11.0 DOC13
Beta-only keyboard firmware 3.39.4, 3.40.0 and 3.40.4 shipped only on the public beta channel (beta 1.22.0's note says 3.39.3, but its app constant and NayaCore's version string say 3.39.4); 3.30.1 is in no public release on either channel; some boards may still run one of these DOC STATIC INFERRED1416
Bluetooth layer version be/100f replies 00 02 on 3.41.0 on both halves (status, then 02, which fits the vendor's "BLE v2"); not implemented on 3.28.7 (no frame at all) MEASURED owner's board, 3.41.0, 2026-09-11; a second board, 3.28.7, 2026-09-19
Dongle the only version-like value is its USB bcdDevice 0x0307; the halves' bootloader identities report the same value, so it most likely reflects the USB stack's default (Zephyr 3.7) rather than a dongle firmware version MEASURED INFERRED owner's dongle and boards, 2026-09-11

Every release is listed on Firmware versions and History.

Build history

  • Prototypes (2023-2024). In January 2023 the keyboard had no battery of its own (all batteries in the modules; the May 2023 campaign still said so) and tenting was quoted "up to 60°"; the shipped manuals say 27° DOC4748217. The Reddit quotes on this site are archived text, not live-verified.
  • Switches. The 2023 campaign specified Gateron KS-28 low-profile switches; Gateron's promised hot-swap socket never came and the KS-28 had quality problems, so Naya moved to Kailh's PG1232 ("Choc Mini", already tried in prototype 5) in March 2024. The dock keys, first Kailh CPG1316 scissor switches, moved to the same PG1232 in September 2024 (about 3 mm taller). Batch 0 came with linear switches, Batch 1 with tactile, and linear became the default from 2025-06 DOC212226293135.
  • Manufacturer. In spring 2024 Naya dropped the contract manufacturer that had built all prototypes, prototyped with two new ones and chose one in July 2024; the vendor later put the time lost at about a year DOC26272838.
  • Module microcontroller. The modules moved from a Holtek part to ST's STM32F411 in May 2024 (the Tune ran on an STM MCU in the July 2024 prototype) DOC2728.
  • Antenna window. The all-metal body blocked the radio, so a plastic section was added over the antennas by the USB-C port (the black end cap), and the planned slim USB-C receiver dongle became a USB-A one DOC2829.
  • Batches. EVT1 finished and EVT2 samples arrived in autumn 2024. Batch 0 was 100 test units shipped in January 2025 (Create with Touch and Tune; Track later) with mostly-wired tester firmware and no remapping or module support. Batch 1 (about 150, April 2025) fixed "a few electrical issues", tightened socket tolerance and thickened the power switches. Batch 2 (2 x 250, June 2025), Batch 3 (2 x about 500, August 2025) and Batch 4 (about 1300, August to September 2025) followed; production validation (PVT) was complete by 2025-07-28 and all Kickstarter pledges had shipped by 2025-09-11; Batches 0-2 were built during production validation DOC3031323334353638.
  • Filed samples. The FCC samples (received by the lab 2025-06-20, mainboards dated 2025-02-20/21) postdate Batch 0, so early retail boards may carry an older board revision than the one filed INFERRED (details).
  • Vendor batch notes. "Batch 1 / DVT#2" units could not charge modules over USB until the firmware in NayaFlow 0.1.0; a "custom build of NayaCore" was used for testing and validating "the last batch of hardware"; NayaFlow 1.15.1 changed readiness detection so "newly delivered" units flash correctly DOC1314.
  • A wired chain that did not ship. In January 2024 the vendor described a wired full-duplex chain at "10 mb/s" from the right module through the right half, the left half and the left module to the computer DOC24. The 2023 campaign page said the opposite for USB mode (the halves stay on RF, only the left sends data over USB), and every measurement on shipped halves fits a radio link between them; whether any shipped unit has such a wired path, and what rate the dock link runs at, is not known OPEN (details).
  • LED count. The 2023 campaign spec sheet promised "90 individually addressable RGB LEDs" (listed as 68 body, 6 dock edge and 10 wing indicator LEDs, which add up to 84) and two side-glow zones per half for status; the shipped keyboard has 88 key and light-bar LEDs (74 keys plus a 7-LED bar per half) DOC INFERRED21.

The wider family

  • Device types in NayaCore: CreateLeft, CreateRight, Dongle, ModDock, TypeLeft, TypeRight, TypeOne; module types TOUCH, TRACK, TUNE, FLOAT STATIC12.
  • Five module apps. Every module firmware bundle, inside NayaCore in every stable release from 1.11.0 to 1.25.1, contains five encrypted apps: Touch, Track, Tune, Float and Query (*_UserApp.sfb with _HASH sidecars); only Touch, Track and Tune shipped STATIC DOC12. See Module firmware.
  • Float. A six-axis ("3D") input puck with a dial ring: marketing showed X/Y/Z, pitch, roll and yaw and a dial, the v1.1.0 manual lists the same inputs, and a vendor update of 2025-12-23 described 6DOF plus a base dial and put shipping at "Q3" 2026; a Naya patent family (WO2025188184A1) covers it; no Float was seen by us DOC STATIC3739843. By the other modules' address pattern it would dock at 0x80 (left) / 0x81 (right); nobody has one to confirm INFERRED.
  • Query. It has a firmware app (41 088 bytes in the 1.25.x bundle) but no entry in NayaCore's module-type list and no marketing trace STATIC. What it is stays unknown (details).
  • Naya Connect. Naya announced a second product family: a 75 % keyboard (Naya Type) with a Dock and magnetic attachments, crowdfunded in January and February 2026 with delivery estimated from February 2027; press reports say its Touch, Track, Tune and Float modules also work on the Create. There is no FCC filing for it: grantee 2BQ4V has nothing after 2025-09-03 as of 2026-09-23 DOC4142404.
  • Other shop items. The vendor's 2026 shop images also showed a "Type" keyboard, a 24-key "Multipad" and a standalone "Dock" with 8 pogo pins and 4 keys; whether any shipped is unknown DOC44 OPEN (details).
  • Bluetooth SIG listing. A listing exists for the keyboard (listing 311198, design Q372162, qualified 2025-09-19, model NAYA-800-1(NAYA-CREATE)); it describes "USB, 2.4G, BLE three working modes". No separate dongle or Naya Connect listing was found DOC6. Details on Regulatory records.
  • The module layer model. A 2024 vendor answer already described it: every layer has 9 sublayers, 1 for the keyboard and 4 for each dock (one per module type), which matches the 8 module-bay positions in the keymap DOC MEASURED25; see Layout and positions.

Safety

The dock contacts carry battery voltage (see Module dock): do not bridge or short them, as the manual says DOC7. The general safety notes are on the home page.

Open questions

  • OPEN Whether the right half ever advertises to or bonds with a host by itself (details).
  • OPEN Which sender byte a relayed reply carries (details).
  • OPEN Whether the Speedlink dongle does anything with shipped firmware (details).
  • OPEN Whether 1.4 kg is per half or per pair (details).
  • OPEN Retail module battery capacities (details).
  • OPEN What Query is; whether Float, Type, Multipad or the standalone Dock shipped (details).
  • OPEN Whether early retail boards (Batch 0/1) carry older board revisions than the filed ones (details).
  • OPEN What the SIG listing's "2.4G" mode refers to (the "2.4G SRD" mode certified in the halves' and the dongle's FCC filings is one candidate, INFERRED) (details).
  • OPEN Whether any shipped setup has a wired data path between the halves (details).

Sources

  1. FCC ID 2BQ4V0825CRL (left half): exhibits on the FCC record (FCC EAS search, grantee code 2BQ4V; mirror fccid.io/2BQ4V0825CRL). Short codes such as "CRL IP1 p10" (exhibit Internal Photos 1, lab attachment page 10) are explained on Regulatory records. ↩↩↩↩↩↩↩↩↩↩

  2. FCC ID 2BQ4V0825CRR (right half), including its label artwork ("Create-R Engraving Reference Sheet"); mirror fccid.io/2BQ4V0825CRR. ↩↩↩↩↩↩

  3. FCC ID 2BQ4V0825DG (Speedlink dongle); mirror fccid.io/2BQ4V0825DG. ↩↩↩↩

  4. FCC OET Equipment Authorization System, grantee search for grantee code 2BQ4V, read 2026-09-23. ↩↩

  5. ISED Canada Radio Equipment List, company number 34320 (search), read 2026-09-23. ↩↩

  6. Bluetooth SIG qualification listing 311198 (listing search), read 2026-09-23. ↩↩

  7. Naya Create User Manual Version 1.0.6, filed as five exhibits under FCC ID 2BQ4V0825CRR (fccid.io); "UM1 p3" means part 1, PDF page 3. See Manuals. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩

  8. Naya Create User Manual Version 1.1.0 (27 pages, PDF dated 2025-11-10), the vendor's Naya_Create_UserManual.pdf on its shop CDN (read 2026-09-23; no archived copy yet). See Manuals. ↩↩↩↩↩↩↩↩

  9. Naya Touch User Manual Version 1.1.0 (vendor PDF, 9 pages). See Manuals. ↩↩↩↩

  10. Naya Track User Manual Version 1.1.0 (vendor PDF, 8 pages). See Manuals. ↩↩↩

  11. Naya Tune User Manual Version 1.1.0 (vendor PDF, 8 pages). See Manuals. ↩↩↩

  12. NayaFlow 1.25.1 (Windows): NayaCore 6.11.0 strings, symbols, imports and embedded resources, and the renderer bundle (static reading). ↩↩↩↩↩↩↩↩↩

  13. Vendor release notes, NayaTech/NayaFlow-releases (0.1.0 to 1.25.1). ↩↩↩↩↩↩↩

  14. Vendor beta release notes, NayaTech/NayaFlow-beta-releases. ↩↩↩

  15. create-legacy-firmware, FIRMWARE-HISTORY.md (image catalog of the 25 stable releases). ↩

  16. create-legacy-firmware, firmware-history-beta/MANIFEST.json (beta images carved, commit 7b511ca). ↩

  17. nayactl, github.com/Qonfused/nayactl (README and constants.py). ↩↩

  18. nayactl, pull request #2 (module type detection; maintainer's board on 3.30.1). ↩

  19. nayactl, pull request #5 (maintainer's board on 3.30.1 with modules on 2.2.2). ↩↩

  20. createflow-dongle, github.com/mediaandmerch/createflow-dongle: docs/findings.md, firmware/src/battery.c and README (third party, keyboard 3.41.0; read at e95b679, 2026-09-23). ↩↩↩↩↩

  21. Kickstarter campaign page with its Specs Sheet and FAQ, naya-create/naya-create (2023). ↩↩↩↩↩↩↩↩

  22. Kickstarter update 4, 2023-08-10. ↩

  23. Kickstarter update 9, 2023-12-07 ("based on a customized ZMK base"). ↩

  24. Kickstarter update 10, 2024-01-06. ↩

  25. Kickstarter update 11, 2024-02-15. ↩

  26. Kickstarter update 12, 2024-03-01. ↩↩

  27. Kickstarter update 13, 2024-05-08. ↩↩

  28. Kickstarter update 14, 2024-07-24. ↩↩↩

  29. Kickstarter update 15, 2024-09-03. ↩↩

  30. Kickstarter update 16, 2024-10-06. ↩

  31. Kickstarter update 17, 2024-11-04. ↩↩↩

  32. Kickstarter update 18, 2025-01-02. ↩↩

  33. Kickstarter update 19, 2025-02-11. ↩

  34. Kickstarter update 20, 2025-03-19. ↩

  35. Kickstarter update 21, 2025-06-16. ↩↩

  36. Kickstarter update 22, 2025-07-28. ↩

  37. Kickstarter update 24, 2025-08-08. ↩

  38. Kickstarter update 25, 2025-09-11. ↩↩

  39. Kickstarter update 26, 2025-12-23. ↩

  40. Kickstarter Naya Connect FAQ, archived 2026-03-14. ↩

  41. New Atlas, Naya Connect modular keyboard, 2026-01-25. ↩

  42. CNX Software, 2026-01-30 (Naya Connect). ↩

  43. WO2025188184A1, "Manual user input device", Naya B.V., published 2025-09-12 (Google Patents). ↩

  44. The vendor's former website, archived by the Wayback Machine (naya.tech captures); cited only, images not reproduced. ↩↩↩

  45. Reddit, vendor comment jklwnhz (2023-05-18); archived text, not live-verified. ↩

  46. Reddit, vendor comment jn3wrmk (2023-06-06); archived text, not live-verified. ↩

  47. Reddit, vendor comment j34wi1g (2023-01-06); archived text, not live-verified. ↩

  48. Reddit, vendor post 1047jlm and comment j35hisb (2023-01-05/06); archived text, not live-verified. ↩