Not runnable todayDetectionVerified 2026-11-05
Ultralytics YOLO11 detect
Ultralytics/YOLO11 (yolo11n.pt)
Ultralytics YOLO11 detect is a image object detection model (AGPL-3.0). Not runnable on Mixpeek today.
Something blocks it today, such as the license, remote code or a GPU-only runtime. The reason is below.
No demo for Ultralytics YOLO11 detect yet
A video, image, slideshow or playground goes here once we record one on our own data.
What it is good and bad at
- Best at
- Fast detect for the fixed COCO label set; n size runs in real time on CPU.
- Worst at
- Closed label set (needs fine-tuning for new classes); license blocks closed commercial use; small or crowded objects at 640 input.
- Task
- Detection
- Input
- Image
- Output
- Boxes, Labels, Scores
- Use cases
- Object detection
Templates that use it
No template uses this model yet. Browse templates.
Input and output
Input
- image
- resolution
- 640x640 letterboxed
- color
- RGB
- prompts
- none (fixed classes)
Output
- boxes
- xyxy pixels
- labels
- COCO 80 classes
- scores
- 0..1
How Mixpeek wires it
- Extractors
- None today
- Feature URIs
- None today
- Vector indexes
- None
- Retriever stages
- None
- Combines with
- detector boxes -> crops -> SigLIP vectors per object (one document per object, or a multi-vector per frame)
- labels -> payload field -> attribute filter in a retriever
- scene splits -> keyframes -> detector -> object documents with frame timestamps
How it runs
- Status
- Not runnable today Blocked by AGPL-3.0 and pickle .pt weights. Would run as a custom extractor plugin that exports the checkpoint to ONNX once (ultralytics export format=onnx) and serves it with onnxruntime on CPU, emitting boxes, labels and crops.
- Serve apps
- None
- Runtime
- ultralytics YOLO (or onnxruntime after export)
- Weights
- Pickle, no remote code
- Parameters
- 2.6 M
- Size on disk
- 5.6 MB
- Preprocessing
- Letterbox to 640x640 (stride-aligned padding), RGB, scale to 0..1.
- Postprocessing
- Confidence threshold then NMS
- Serving
- both
- Hardware
- Runs on CPU (slower without a GPU)
Scale to zero
- Minimum replicas
- 0
- Maximum replicas
- 1
- Idle timeout
- 600 s
- Memory
- 1 GB
- CPUs
- 1
- GPUs
- 0
- Cold start, node warm
- Not recorded
- Cold start, new node
- Not recorded
Measured cost
Unmeasured
No committed measurement; plan row 3 measures it in the standalone image.
Our evaluations
Unmeasured
We have not evaluated this model on our own data yet. Publisher results are in the sources below.
Questions
- What is Ultralytics YOLO11 detect best at?
- Fast detect for the fixed COCO label set; n size runs in real time on CPU.
- What are the limits of Ultralytics YOLO11 detect?
- Closed label set (needs fine-tuning for new classes); license blocks closed commercial use; small or crowded objects at 640 input.
- Can Ultralytics YOLO11 detect be used commercially?
- No. AGPL-3.0: offering it over a network obliges publishing the whole application's source under AGPL; closed commercial use needs an Ultralytics Enterprise license.
- How does Ultralytics YOLO11 detect run on Mixpeek?
- Blocked by AGPL-3.0 and pickle .pt weights. Would run as a custom extractor plugin that exports the checkpoint to ONNX once (ultralytics export format=onnx) and serves it with onnxruntime on CPU, emitting boxes, labels and crops.