Skip to main content
CASE STUDY

Four custom image workflows. Shipped in under a week.

How Dyver replaced one inconsistent model with four production APIs, and started shipping to clients at scale.

No AI team needed
Dyver×Runflow
DY

Dyver

AI product image processing for e-commerce and retail

Product

High-volume AI image editing for product and fashion photography

Customers

E-commerce brands and retailers needing studio-quality catalog imagery at scale

Before Runflow

One general-purpose model, manual QA on every output

Delivered by Runflow

Four custom image workflows with dedicated API endpoints

Timeline

First four workflows in production in under a week

Team

No in-house AI or GPU infrastructure team required

THE PROBLEM

One model can't hold catalog quality at scale.

Dyver was running every edit through one general-purpose model. On a good day it worked. At scale, output drifted: half-removed tags, artifacts on fabrics, garment edges that melted when backgrounds changed.

Because the model couldn't be trusted to stay consistent, every image was checked by a human before going to the client. Manual QA became the ceiling on volume.

Competitors were moving fast. Dyver needed consistent workflows, fast. Hiring an in-house AI team would take months they didn't have.

1
General model
Manual
QA per image
Inconsistent
Output quality
Capped
Client volume
THE SOLUTION

Four custom workflows. Four API endpoints.
Shipped in a week.

Instead of asking one model to do everything, Runflow built a dedicated workflow for each job: shopping tag removal, model removal, additional product removal, and background removal.

Each workflow is purpose-built: models plus post-processing tuned for one task. Dyver calls it with a single API request. No model selection, no pipeline engineering, no GPU management.

All four shipped in under a week. New edit types follow the same path. Client requests become endpoints, not roadmap items.

Purpose-built per task

Each workflow is engineered for a specific edit. Consistent output at catalog scale, not one-model-fits-all.

Days, not quarters

New workflows go from spec to production API in days. Dyver ships to clients at the pace of their requests.

WORKFLOWS IN PRODUCTION

The four workflows Runflow built for Dyver.

Drag any card to reveal the before and after. Each grid shows real production output.

Shopping Tag Removal

Live3 samples

Remove brand and price tags from product photography while preserving fabric detail and texture.

Shopping Tag Removal sample 1 after
Shopping Tag Removal sample 1 before
◂ ▸
BeforeAfter
Shopping Tag Removal sample 2 after
Shopping Tag Removal sample 2 before
◂ ▸
BeforeAfter
Shopping Tag Removal sample 3 after
Shopping Tag Removal sample 3 before
◂ ▸
BeforeAfter

Model Removal

Live3 samples

Extract garments and accessories from model photography to produce flat-lay style product shots.

Model Removal sample 1 after
Model Removal sample 1 before
◂ ▸
BeforeAfter
Model Removal sample 2 after
Model Removal sample 2 before
◂ ▸
BeforeAfter
Model Removal sample 3 after
Model Removal sample 3 before
◂ ▸
BeforeAfter

Additional Product Removal

Live3 samples

Isolate the hero product by removing secondary items, accessories, and styling props from the scene.

Additional Product Removal sample 1 after
Additional Product Removal sample 1 before
◂ ▸
BeforeAfter
Additional Product Removal sample 2 after
Additional Product Removal sample 2 before
◂ ▸
BeforeAfter
Additional Product Removal sample 3 after
Additional Product Removal sample 3 before
◂ ▸
BeforeAfter

Background Removal

Live

Clean isolation of products from complex backgrounds, producing studio-quality white or transparent cuts.

Production workflow. Sample gallery available on request.

SENTINEL INTEGRATION

Two callbacks per image.
Reviewers only see one.

Dyver sends Runflow an image. Runflow runs the edit and ships the result back in under three seconds. A second callback follows with Sentinel's score, a pass/fail, and any artifacts it caught. Reviewers stop scanning every output. They only see what Sentinel flagged.

Request lifecycle
job img_9a8b
t = 0.0sDyver → Runflow
Image received
API call hits the workflow endpoint. Edit starts immediately.
POST /v1/flows/model-removal/run
+ 2.3sRunflow → Dyver
Edited image shipped back
Synchronous response. Dyver delivers it to the end client right away.
200 OK · image/webp · 1.4 MB
+ 4.7sSentinel → Dyver
Quality callback fires
Off the critical path. The reviewer only sees this if Sentinel flagged the image.
{ "job_id": "img_9a8b", "score": 87.4, "passed": true, "notes": [] }
Dyver review queue
last 50 jobs
sku-47210-edited.webp
auto-approved · shipped
94.2
sku-58331-edited.webp
auto-approved · shipped
92.8
sku-68412-edited.webp
auto-approved · shipped
91.1
sku-38201-edited.webp
background bleed on edges
58.2
sku-44720-edited.webp
auto-approved · shipped
90.4
sku-50611-edited.webp
auto-approved · shipped
89.3
96% auto-approved
4% need a reviewer
Callbacks per image
2 · edit, then score
Added latency
0 ms
Reviewer workload
Only flagged outputs
THE OUTCOME

Delivering to clients at scale.

Dyver went from firefighting one unreliable model to running four production workflows with consistent output. New edit types ship as live endpoints in days, not quarters.

Before Runflow
  • One general model for every edit
  • Manual QA on every output
  • Client volume capped by review capacity
  • New edit types blocked on hiring an AI team
With Runflow
  • Four purpose-built workflows in production
  • Consistent output across the catalog
  • Quality signals surface outliers automatically
  • New workflows shipped in days through a single API

Want your own custom workflow?

Describe the edit you need. Runflow builds the workflow, ships the endpoint, and you scale on top.

SOC 2 Type II Compliant
No AI team needed