Osam (/oʊˈsɑm/) is a tool to run open-source promptable vision models locally (inspired by Ollama).
Osam provides:
- Promptable Vision Models - Segment Anything Model (SAM), EfficientSAM, YOLO-World;
- Local APIs - CLI & Python & HTTP interface;
- Customization - Host custom vision models.
Installation
Pip
pip install osam[cpu] # or osam[gpu] for NVIDIA GPUs
osam[gpu] installs onnxruntime-gpu together with the CUDA and cuDNN
libraries, so no system CUDA install is needed. Install only one onnxruntime
build: onnxruntime and onnxruntime-gpu overwrite each other's files.
For osam serve:
pip install osam[cpu,serve]
Quickstart
To run with EfficientSAM:
osam run efficientsam --image <image_file>
To run with YOLO-World:
osam run yoloworld --image <image_file>
Model library
Here are models that can be downloaded:
| Model | Parameters | Size | Download |
|---|---|---|---|
| SAM 100M | 94M | 100MB | osam run sam:100m |
| SAM 300M | 313M | 310MB | osam run sam:300m |
| SAM 600M | 642M | 630MB | osam run sam |
| SAM2 Tiny | 39M | 150MB | osam run sam2:tiny |
| SAM2 Small | 46M | 170MB | osam run sam2:small |
| SAM2 BasePlus | 82M | 300MB | osam run sam2 |
| SAM2 Large | 227M | 870MB | osam run sam2:large |
| SAM3 | 893M | 3.4GB | osam run sam3 |
| EfficientSAM 10M | 10M | 40MB | osam run efficientsam:10m |
| EfficientSAM 30M | 26M | 100MB | osam run efficientsam |
| YOLO-World XL | 168M | 640MB | osam run yoloworld |
PS. sam, efficientsam is equivalent to sam:latest, efficientsam:latest.
Prompts
| Model | Point | Box | Negative box | Text |
|---|---|---|---|---|
| SAM | ✓ | ✓ | ||
| SAM2 | ✓ | ✓ | ||
| SAM3 | ✓ | ✓ | ✓ | ✓ |
| EfficientSAM | ✓ | ✓ | ||
| YOLO-World | ✓ |
Speed
Milliseconds to encode the image + run one prompt (point; text for SAM3 and YOLO-World, which has no separate encoding), median of 5 runs after a warm-up, excluding model loading:
| Model | CPU i9-12900K |
CUDA RTX 3080 Ti |
CPU Apple M5 |
CoreML Apple M5 |
|---|---|---|---|---|
| SAM 100M | 1255 + 32 | 692 + 20 | 2267 + 47 | 257678 + 84 |
| SAM 300M | 2633 + 33 | 2125 + 23 | 6778 + 53 | > 15 min |
| SAM 600M | 4165 + 34 | 4197 + 27 | 11023 + 52 | > 15 min |
| SAM2 Tiny | 569 + 40 | 65 + 16 | 1627 + 59 | 277 + 66 |
| SAM2 Small | 651 + 44 | 74 + 17 | 2119 + 58 | 320 + 61 |
| SAM2 BasePlus | 1237 + 50 | 104 + 17 | 2923 + 51 | 570 + 65 |
| SAM2 Large | 2414 + 43 | 151 + 17 | 7596 + 48 | 1281 + 60 |
| SAM3 | 6512 + 1174 | 348 + 75 | 15233 + 1426 | 2425 + 373 |
| EfficientSAM 10M | 399 + 45 | 55 + 16 | 781 + 34 | fails to load |
| EfficientSAM 30M | 948 + 46 | 74 + 15 | 1767 + 35 | fails to load |
| YOLO-World XL | 774 | 42 | 1829 | fails to load |
Measured on examples/_images/dogs.jpg (2560x1600) with onnxruntime 1.23.2
(onnxruntime-gpu 1.31.1 for CUDA).
Run python examples/benchmark.py --device cpu --device cuda to measure on
your machine.
See docs/benchmark.md for SAM3 per prompt, load times
and CPU/CoreML parity.
Custom download endpoint
Models are downloaded from their canonical URLs by default. To download from a
mirror instead (for example, in networks where the canonical hosts are blocked),
set OSAM_BLOB_ENDPOINT to a comma-separated list of endpoints tried in order:
# Try the mirror first, then fall back to the canonical host.
export OSAM_BLOB_ENDPOINT="https://mirror.example.com,direct"
Each blob is fetched from <endpoint>/<sha256-hex>; the reserved value direct
uses the model's canonical URL. Downloads are verified by SHA-256 regardless of
the endpoint, so a mirror cannot serve corrupted data. When unset, only direct
is used. Omit direct from the list (for example
OSAM_BLOB_ENDPOINT="https://mirror.example.com") to disable the canonical
fallback and serve every blob from the mirror only.
Execution providers
Pick a device per model with --device on the CLI or device= in Python:
osam run sam3 --image examples/_images/dogs.jpg --text dog --device coreml
model = osam.apis.get_model_type_by_name("sam3")(device="cuda")
cpu, cuda and coreml are supported. An unavailable device raises an
error instead of falling back to CPU. With coreml, SAM3 runs its point
decoder on CPU and the rest on CoreML.
Without a device, inference runs on CUDAExecutionProvider when the installed onnxruntime has it,
otherwise on CPUExecutionProvider. To use another accelerator (CoreML on
macOS, DirectML on Windows, TensorRT, ROCm), set OSAM_ONNX_PROVIDERS to a
comma-separated list tried in the given order:
export OSAM_ONNX_PROVIDERS="CoreMLExecutionProvider,CPUExecutionProvider"
CoreML ships in the osam[cpu] build on macOS. For DirectML and other
builds, install osam without extras plus the matching onnxruntime package
(for example onnxruntime-directml). If a session cannot be created with the
given list, osam logs the error and falls back to CPUExecutionProvider.
Usage
CLI
# Run a model with an image
osam run efficientsam --image examples/_images/dogs.jpg > output.png
# Get a JSON output
osam run efficientsam --image examples/_images/dogs.jpg --json
# {"model": "efficientsam", "mask": "..."}
# Give a prompt
# 1. point prompt (x,y[,label]: foreground=1 by default, background=0)
osam run efficientsam --image examples/_images/dogs.jpg \
--point 1439,504 --point 1439,1289 > efficientsam_point.png
# 2. box prompt with sam2 (x1,y1,x2,y2)
osam run sam2 --image examples/_images/dogs.jpg \
--box 1233,376,1649,691 > sam2_box.png
# 3. text prompt
osam run sam3 --image examples/_images/dogs.jpg --text dog > sam3_text.png
# 4. box prompt with sam3
osam run sam3 --image examples/_images/dogs.jpg \
--box 1233,376,1649,691 > sam3_box.png
# 5. text prompt with sam3, excluding a region
osam run sam3 --image examples/_images/dogs.jpg \
--text dog --negative-box 1200,400,1700,1400 > sam3_negative_box.png
# Or give the whole prompt as JSON (point labels: background=0, foreground=1,
# box=2,3, negative box=4,5)
osam run sam2 --image examples/_images/dogs.jpg \
--prompt '{"points": [[1233, 376], [1649, 691]], "point_labels": [2, 3]}'
# from a file (@prompt.json) or stdin (-), with a threshold on top
osam run sam3 --image examples/_images/dogs.jpg --prompt @prompt.json \
--score-threshold 0.5
Output images: 'efficientsam_point.png', 'sam2_box.png', 'sam3_text.png', 'sam3_box.png'
Python
import numpy as np
from PIL import Image
import osam
image = np.asarray(Image.open("examples/_images/dogs.jpg"))
request = osam.types.GenerateRequest(
model="efficientsam",
image=image,
prompt=osam.types.Prompt(points=[[1439, 504], [1439, 1289]], point_labels=[1, 1]),
)
response = osam.apis.generate(request=request)
annotation = response.annotations[0]
mask = np.zeros(image.shape[:2], dtype=np.bool_)
bbox = annotation.bounding_box
mask[bbox.ymin:bbox.ymax + 1, bbox.xmin:bbox.xmax + 1] = annotation.mask
Image.fromarray(mask).save("mask.png")
Input and output images ('dogs.jpg', 'mask.png').
HTTP
# pip install osam[cpu,serve] # required for `osam serve`
# Get up the server
osam serve
# POST request
base64 < examples/_images/dogs.jpg \
| jq -Rs '{model: "efficientsam", image: gsub("\n"; "")}' \
| curl 127.0.0.1:11368/api/generate -X POST --json @- \
| jq -r '.annotations[0].mask' | base64 --decode > mask.png
Metadata
Release files for osam 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| osam-0.9.0.tar.gz | 27.5 MB | With provenance | Details for osam-0.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| osam-0.9.0-py3-none-any.whl | Python 3 | none | any | Details for osam-0.9.0-py3-none-any.whl |
Total release size: 29.0 MB
Release files / osam-0.9.0.tar.gz
| Download URL | osam-0.9.0.tar.gz |
|---|---|
| Size | 27.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04031d334d30835c00c1f8ed5180920e1a57a4772ce7f8f41e3a2b92bd1c904a
|
|
BLAKE2b-256 checksum How to use checksums |
176856ed38ec75763cb8423a43cf4ecf772b69d72389af279ea591fe09256de6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / osam-0.9.0-py3-none-any.whl
| Download URL | osam-0.9.0-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84964e07a07df396ae953dba72c375adf1b10f283dc9d617a9fb609d1f854921
|
|
BLAKE2b-256 checksum How to use checksums |
b844c83da34190d7db92f4831dc686c0c113fcc7828d3acb672a74785d3b094c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for osam 0.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for osam-0.9.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.