However, we observe that the speed and accuracy of YOLOs are negatively affected by the NMS. Recently, end-to-end Transformer-based detectors (DETRs) have provided an alternative to eliminating NMS. Nevertheless, the high computational cost limits their practicality and hinders them from fully exploiting the advantage of excluding NMS. In this paper, we propose the Real-Time DEtection TRansformer (RT-DETR), the first real-time end-to-end object detector to our best knowledge that addresses the above dilemma. We build RT-DETR in two steps, drawing on the advanced DETR: first we focus on maintaining accuracy while improving speed, followed by maintaining speed while improving accuracy.…
moku-v4 is an open-weight model for object detection from Kaya, released under GNU Affero General Public License 3.0. It has 20M parameters. At 16-bit it needs about 0 GB of GPU memory, which fits on 1x MI300X from $1.85 an hour, at the lowest prices in the SAVRN Index.
Go board detector used by Kaya to turn a photo of a goban into a position (SGF). Trained with moku. Kaya computes a homography from the 4 corners and snaps every stone onto the grid.
Runs On
What it takes to serve moku-v4 (20M parameters): the memory its weights need at each precision, and the cheapest way to rent enough data-center GPUs to hold them.
| Precision | Weights | Memory needed | Cheapest setup | Per hour | Also fits |
|---|---|---|---|---|---|
| 16-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 8-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 4-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
Memory is the weights at that precision plus 20% for the runtime and a short context; a long context needs more. Prices are the lowest on-demand hourly rates in the SAVRN Index, read Oct 18, 2026.
moku-v4 on every accelerator the SAVRN Index prices, at every precision
Model Card
By Kaya, published under agpl-3.0, revision 529e8ea9aaac.
Go board detector used by Kaya to turn a photo of a goban into a position (SGF). Trained with moku. Kaya computes a homography from the 4 corners and snaps every stone onto the grid. - model.safetensors, config.json, preprocessorconfig.json: transformers checkpoint. - model.onnx: what Kaya runs (ONNX Runtime Web). Input pixelvalues (batch, 3, 640, 640), RGB scaled to [0, 1] with no mean/std normalization; outputs logits (batch, 300, 3) (apply a sigmoid) and predboxes (batch, 300, 4), normalized (cx, cy, w, h). With the corner head, a third output cornerpoints (batch, 8, 3) holds the 8 best board-corner peaks (x, y, score), x and y normalized to [0, 1] (class-agnostic). The stone-threshold…
Read Kaya's full model card
Go board detector used by Kaya to turn a photo of a goban into a position (SGF). Trained with moku.
It detects three classes: black_stone (0), white_stone (1) and board_corner (2).
Kaya computes a homography from the 4 corners and snaps every stone onto the grid.
Files
model.safetensors,config.json,preprocessor_config.json: transformers checkpoint.model.onnx: what Kaya runs (ONNX Runtime Web). Inputpixel_values(batch, 3, 640, 640), RGB scaled to [0, 1] with no mean/std normalization; outputslogits(batch, 300, 3)(apply a sigmoid) andpred_boxes(batch, 300, 4), normalized(cx, cy, w, h). With the corner head, a third outputcorner_points(batch, 8, 3)holds the 8 best board-corner peaks(x, y, score), x and y normalized to [0, 1] (class-agnostic). The stone-threshold calibration is baked intologits(offset +0.35 on every class logit), so Kaya's fixed 0.035 threshold needs no per-model setting.
Evaluation
| split | mAP@50 | stone cdAP | corner R@4 | perfect boards | errors / board |
|---|---|---|---|---|---|
| validation | 0.544 | 0.773 | 0.642 | 42% [31%, 54%] | 20.8 [12.8, 29.5] |
| test | 0.585 | 0.794 | 0.664 | 44% [35%, 53%] | 18.6 [10.6, 28.6] |
Board metrics run Kaya's own post-processing (stone threshold 0.035, corners from head) and compare the
resulting position with the one read from the annotations: perfect is the share of boards
without a single wrong intersection and no corner more than half a cell off. Intervals are 90%
bootstrap CIs over photos.
Configuration
- Architecture
- RTDetrForObjectDetection
- Model type
- rt_detr
Identity and Version
- Repository
- kaya-go/moku-v4
- Publisher
- Kaya
- Task
- Object detection
- Modality
- Image
- Library
- transformers
- Parameters
- 20M parameters
- Languages
- go
- Revision
- 529e8ea9aaac9a3ac2c423d6dcf68e35d7a480b6
- First published
- 2026-09-23
- Last updated
- 2026-09-24
Files and Weights
6 files, 163.1 MB in total. The weights are 2 files totalling 163.1 MB in onnx, safetensors.
Every file
| File | Type | Size | SHA-256 |
|---|---|---|---|
| model.onnx | Weights | 82.6 MB | de40db0f8a38 |
| model.safetensors | Weights | 80.5 MB | 634da050b84a |
| config.json | Configuration | 2.5 KB | — |
| preprocessor_config.json | Configuration | 424 B | — |
| README.md | Documentation | 1.8 KB | — |
| .gitattributes | Repository | 1.5 KB | — |
License and Download
- License
- agpl-3.0
- Access
- Open weights, no gate
- Download size
- 163.1 MB
Released by Kaya through its official repository on Hugging Face. Read the license.
Built From
- Derived from kaya-go/moku-v2
- Quantized from kaya-go/moku-v2
- Trained on (disclosed) kaya-go/moku-v4
Memory Requirements
| Precision | Weights in memory |
|---|---|
| As published | 163.1 MB |
| 16-bit | 0.0 GB |
| 8-bit | 0.0 GB |
| 4-bit | 0.0 GB |
Weights only, from the published parameter count; the key-value cache and runtime add to this.
Questions About moku-v4
How much GPU memory does moku-v4 need?
About 0 GB at 16-bit and 0 GB at 4-bit: the weights (20M parameters) plus a working margin. A long context needs more.
What is the cheapest GPU to run moku-v4 on?
At 16-bit, 1x MI300X from $1.85 an hour; at 4-bit, 1x MI300X from $1.85 an hour, at the lowest on-demand prices the SAVRN Index lists.
Can I use moku-v4 commercially?
Yes, with conditions. moku-v4 is released under GNU Affero General Public License 3.0. The AGPL 3.0 is a strong copyleft license. Commercial use is allowed, but a modified version made available to users over a network must be released with its source code under the same license.
Similar Models
However, we observe that the speed and accuracy of YOLOs are negatively affected by the NMS. Recently, end-to-end Transformer-based detectors (DETRs) have provided an alternative to eliminating NMS. Nevertheless, the high computational cost limits their practicality and hinders them from fully exploiting the advantage of excluding NMS. In this paper, we propose the Real-Time DEtection TRansformer (RT-DETR), the first real-time end-to-end object detector to our best knowledge that addresses the above dilemma. We build RT-DETR in two steps, drawing on the advanced DETR: first we focus on maintaining accuracy while improving speed, followed by maintaining speed while improving accuracy.…
The RT-DETRv2 model was proposed in RT-DETRv2: Improved Baseline with Bag-of-Freebies for Real-Time Detection Transformer by Wenyu Lv, Yian Zhao, Qinyao Chang, Kui Huang, Guanzhong Wang, Yi Liu. RT-DETRv2 refines RT-DETR by introducing selective multi-scale feature extraction, a discrete sampling operator for broader deployment compatibility, and improved training strategies like dynamic data augmentation and scale-adaptive hyperparameters. These changes enhance flexibility and practicality while maintaining real-time performance. This model was contributed by @jadechoghari with the help of @cyrilvallez and @qubvel-hf This is RT-DETRv2 consistently outperforms its predecessor across all…
The D-FINE model was proposed in D-FINE: Redefine Regression Task in DETRs as Fine-grained Distribution Refinement by Yansong Peng, Hebei Li, Peixi Wu, Yueyi Zhang, Xiaoyan Sun, Feng Wu This model was contributed by VladOS95-cyber with the help of @qubvel-hf This is the HF transformers implementation for D-FINE coco -> model trained on COCO obj365 -> model trained on Object365 obj2coco -> model trained on Object365 and then finetuned on COCO D-FINE, a powerful real-time object detector that achieves outstanding localization precision by redefining the bounding box regression task in DETR models. D-FINE comprises two key components: Fine-grained Distribution Refinement (FDR) and Global…
LW-DETR, a Light-Weight DEtection TRansformer model, is designed to be a real-time object detection alternative that outperforms conventional convolutional (YOLO-style) and earlier transformer-based (DETR) methods in terms of speed and accuracy trade-off. It was introduced in the paper LW-DETR: A Transformer Replacement to YOLO for Real-Time Detection by Chen et al. and first released in this repository. Disclaimer: This model was originally contributed by stevenbucaille in transformers. LW-DETR is an end-to-end object detection model that uses a Vision Transformer (ViT) backbone as its encoder, a simple convolutional projector, and a shallow DETR decoder. The core philosophy is to leverage…
Table Transformer (DETR) model trained on PubTables1M. It was introduced in the paper PubTables-1M: Towards Comprehensive Table Extraction From Unstructured Documents by Smock et al. and first released in this repository. Disclaimer: The team releasing Table Transformer did not write a model card for this model so this model card has been written by the Hugging Face team. The Table Transformer is equivalent to DETR, a Transformer-based object detection model. Note that the authors decided to use the "normalize before" setting of DETR, which means that layernorm is applied before self- and cross-attention. You can use the raw model for detecting tables in documents. See the documentation for…