Self-hosted background removal that stays on your network#
You need cutouts without uploading photos to a third-party cloud. Compliance, air-gapped networks, or cost at volume all point the same way: run inference on hardware you control.
When this applies#
- Images must not leave your VPC, laptop, or studio
- You want unlimited local processing at no per-image cost
- You already run Docker, Python jobs, or Apple Silicon Macs
- You may still call a managed API later for harder edges (hair, fur, products)
Which path to use#
| If you… | Use |
|---|---|
| Desktop batch on Apple Silicon, offline | withoutBG for Mac |
| Scripts, notebooks, batch folders | Python package (open_weights) |
| Team server, CI, or Linux GIMP plugin backend | Docker service or app image |
| Hair, fur, catalog edges, managed SLA | Pro Model cloud API (same endpoint shape) |
How withoutBG fits#
- Open Weights are Apache-2.0. Commercial use, modification, and redistribution are allowed.
- Local inference never calls the cloud. No API key for open_weights mode.
- Docker headless service exposes /v1.0/image-without-background on your host, matching the Pro API path so you can switch later without rewriting clients.
- Pro Model (when you need it): p95 ≈ 1.95 s server-side in Frankfurt, DE. RAM-only processing; uploads are not retained for training.
FAQ#
Is self-hosting really free?#
Yes for Open Weights. You pay for your own CPU/GPU and electricity. The model license is Apache-2.0. Pro cloud credits are optional when local quality is not enough.
Do my images leave the machine?#
Not in local Open Weights mode (Python, Docker, Mac). Pro Model uploads go to Frankfurt, DE over TLS, are processed in RAM, and are discarded after the response.
Can I keep the same client code for local and cloud?#
Yes for HTTP clients against the Docker Local API or Mac Local API: the path matches the cloud Pro API. The Python SDK switches with open_weights() vs api().
What about GDPR?#
Local processing keeps personal images on systems you control. For the cloud API, processing is in the EU (Frankfurt) with no training on customer uploads. See the privacy policy for details.
Next steps#
Pick an entrypoint. All product paths are linked from the use cases hub.