RF-DETR is a production-grade computer vision library by Roboflow for real-time object detection, instance segmentation, and keypoint estimation. It implements a DETR-family architecture (LW-DETR, Deformable DETR) with a DINOv2 backbone, providing a complete training-to-deployment pipeline. The library is published as the `rfdetr` PyPI package and serves as the open-source core of Roboflow's detection platform, with larger models available under a separate license. The system is structured as a Python library with a CLI entry point (`rfdetr`). The main model class `RFDETR` (and variants like `RFDETRNano`) provides `predict()`, `train()`, `export()`, and `evaluate()` methods. Training is built on PyTorch Lightning with custom `LightningModule` and `LightningDataModule`, plus callbacks for EMA, COCO evaluation, GPU memory monitoring, and drop-path scheduling. The export subsystem uses a registry pattern with format-specific exporters (ONNX, TensorRT, TFLite, CoreML, OpenVINO, ExecuTorch, LiteRT) that share preprocessing and decoding utilities. Dataset loaders support COCO, YOLO, WebDataset, and Roboflow formats with configurable augmentation backends (torchvision, Albumentations, Kornia). The primary data flow: input images → preprocessing (resize, normalize) → DINOv2 backbone → multi-scale feature projector → deformable attention transformer encoder-decoder → task-specific heads (detection, segmentation, keypoints) → post-processing (top-k selection, NMS-free decoding). Training uses COCO-style datasets with Hungarian matching for label assignment. External dependencies include PyTorch, PyTorch Lightning, HuggingFace Transformers, and optional backends for export. The library integrates with Roboflow's platform for dataset management and deployment. The codebase is actively maintained with extensive test coverage (pytest, CI workflows for CPU/GPU/XLA), backward compatibility testing for legacy checkpoints, and a formal changelog. It demonstrates high craftsmanship in areas like safe checkpoint loading, atomic file operations, custom fused optimizers (Triton), and export robustness. The large optional dependency surface and reliance on some private PyTorch APIs introduce maintenance risk, but overall it is a well-engineered library suitable for production use.