Skip to content
KN-86 Deckline

universal60plate

  • Source: https://github.com/andrewcyuan/universal60plate
  • Category: research — archived plate-design reference
  • Role for KN-86: a single example of a freely-downloadable mechanical-keyboard plate as a DXF artifact. Not actioned — KN-86 uses Sweep plates from holykeebs per keyboard-decision.md.
  • License / caveats: see the repo for the explicit license. The README is sparse; the value is the DXF artifact itself.

What it is

Section titled “What it is”

A free open-source universal 60% keyboard plate, distributed as a DXF file. The plate fits the standard 60% keyboard form factor (the most common DIY keyboard size — 14 keys wide, 5 rows, with cutouts for ISO/ANSI variants and split spacebars). The README is minimal; the project’s value is the artifact: a ready-to-fab DXF that any laser-cut service can take and produce a working plate from.

Key takeaways for KN-86

Section titled “Key takeaways for KN-86”
  • It’s a concrete example of a downloadable, ready-made plate DXF. Worth knowing exists as a reference for what a finished plate artifact looks like in practice — useful background even though we’re not building one. The GOLEM plate-manufacturing guide describes the pipeline to produce such an artifact; universal60plate is what the output of that pipeline is.
  • The 60% form factor is the lineage of most DIY keyboards the KN-86 community is adjacent to. The Sweep is in a different family (40%-class split), but if a hypothetical KN-9x sister product ever wanted a 60% layout, this is the kind of reference to start from rather than designing from scratch.
  • MIT/permissive open-hardware as the right license posture. universal60plate’s presence on GitHub as a freely-downloadable plate is the open-hardware ethos KN-86 inherits (x0xb0x, Cyberdeck Cafe lineage). When KN-86 eventually publishes its own bezel/insert STL set, this is the kind of distribution model the project should follow — GitHub repo, permissive license, single-purpose, clearly labeled.

Why this is in research/ and brief

Section titled “Why this is in research/ and brief”

The entry is intentionally short because:

  1. We’re not building a 60% keyboard
  2. The README is sparse, so there’s no rich source material to summarize
  3. The reference value is “this exists as a finished artifact” — once that’s recorded, the entry has done its job

If a future KN-9x sister product or after-market KN-86 community contribution wants a starting plate file, this entry points there. Otherwise the entry sits in the corpus as a small “yes, this exists” reference.

Image

Section titled “Image”

No image downloaded.

Notes

Section titled “Notes”