Member-only story
Can AI Model Vendors Track Your Self-Hosted Deployment?
How watermarks, SynthID, and fingerprinting work — and why licenses are enforced by audits, not signals.
I was model-shopping. The job was unglamorous: generate on-brand product-image variants at scale, eight or so per source image, cheaply enough that we could run it across the whole catalog instead of a curated handful. I had already swapped out one paid image API, and I was auditioning open models to replace another.
FLUX.1 [dev] was the one I wanted. Its outputs were just cleaner than the alternatives I was testing, the kind of margin you notice in the first ten samples and can’t un-see. Then I opened the FLUX.1 [dev] license file.
Non-commercial!
The thought that arrived next is the reason this article exists. It wasn’t “damn, I can’t use it.” It was: how would they even know? I’d be running the weights on a box inside our own infra. No phone-home. I could train a LoRA on our own product images and change the outputs entirely. Was there a watermark? A serial number baked into the tensors? Some beacon that pings Black Forest Labs the first time I generate a product shot for money?
So I chased it down properly. License texts, watermarking libraries, the model-fingerprinting…
