Rembrand product insertion API

Turning product insertion into an API shifts Rembrand from running ad deals itself to selling picks and shovels to the companies that already control premium video inventory. That matters because a studio, streamer, or publisher can keep its brand relationships, send finished footage into Rembrand’s system, and get back edited assets with realistic objects, signs, or packaging added into the scene, then pay software or licensing fees instead of sharing campaign revenue title by title.

• The workflow is much more concrete than a generic ad tech API. Rembrand breaks video down, finds usable surfaces and moments, models lighting, depth, motion, and occlusion, then returns lightweight files that slot back into the editing project for final render. That makes it usable inside existing post production pipelines.
  1 sacra 3 adobevideopartner
• This model changes who owns the advertiser. In Rembrand’s creator marketplace, Rembrand curates creators for brands and shares CPM revenue with creators. In the API model, the publisher or studio keeps the direct sales relationship and uses Rembrand as infrastructure, with revenue coming from licensing fees.
  1 sacra 2 rembrand
• The closest precedent is Mirriad, which built virtual product placement for TV, streaming, music, and other premium video. The category is moving toward platform distribution and programmatic pipes, with Rembrand also appearing in Adobe’s video partner ecosystem and in The Trade Desk’s Kokai environment through partners covering in scene media workflows.
  4 mirriad 5 prnewswire 6 mogl

If this model works, virtual placement stops being a bespoke service and starts looking like production software tied to ad sales systems. That opens a bigger market than creator campaigns alone, because every large rights holder with a video library can treat in scene inventory as software enabled ad space and scale placements across many titles at once.