One wardrobe.
Every pose.
One grid.

Ask for one image and you get one opinion. Wardrobe Gone Wild styles your outfit many times across the fleet, a different pose and model each, laid out as one grid, so you choose the look instead of re-rolling. Send any result back as an edit reference.

Join r/wardrobeGW See how it works

r/ r/wardrobeGW · our demo batch · rendered on 11 rigs

the same four women, everyday clothes restyled to fitted athleisure

everyday

restyled

+2 more

4 women, restyled in one batch keep the best, re-roll the rest — in the studio

The throughput problem

Approving a look
takes many poses,
not one photo.

Consumer tools

1 image at a time

describe, wait, repeat

One result per run, behind a shared queue. Reviewing an outfit means dozens of manual round trips, and a day of iteration produces a handful of usable looks.

Cloud APIs

per image pricing

plus a parallel-request cap

Per-image pricing adds up at exploration volume, and rate limits cap how many render at once. Check the current rate with your provider.

Wardrobe Gone Wild

$0.006 / image

$29 for 5,000 images

One outfit description renders on every free rig at once. Creator is $29 a month for 5,000 images: $0.006 each if you use the allowance, $0.029 each at 1,000 images a month. Either way it is a flat monthly bill, not a meter.

The fleet

Real hardware. Real numbers.

r/ About the fleet

variations at once

Each rig holds the whole model across its 6 GPUs and renders one variation. Your batch spreads over every free rig, then queues the rest.

51s

for a draft image

Measured on one free rig. A batch of 11 drafts lands in about the same time, because they render together. At the Standard setting one image is about 3 min 18 s, and 50 of them about 17 minutes.

GPUs in the fleet

11 rigs, 6 GPUs each. Owned hardware, not rented capacity, which is why an image costs cents instead of dollars.

These are counts of machines we own and times we measured, not projections. Time per image scales with the size and the number of steps you choose.

How it works

Describe. Fan out. Pick.

Describe

Describe one outfit in the studio or through the API. Pick the size, the quality, how many poses you want, and any skills to apply, such as identity-preserving editing.

Fan out

The scheduler spreads the batch over every free rig. Each rig renders one pose on its own seed, and the rest queue behind them, so looks arrive steadily rather than all at the end.

Pick and iterate

Review the looks as a grid and keep what works. Send any result back as an edit reference, describe the change, and the fleet renders the next round.

Features

What's included.

SCALE

Poses at Scale

One outfit description goes to the fleet as up to 50 renders at once, a different pose and model each, and comes back as one grid. The looks share the same description, so you pick the strongest instead of re-running it all afternoon.

SKILLS

Styles and Skills

Style adapters change how the fleet renders a look, applied per batch with no training step. Identity-preserving editing has shipped; more skills are in development.

EDIT

Edit with Reference

Send any look back as a reference and describe the change. The fleet renders poses of the edit the same way it renders poses of an outfit.

API

API Access

Submit batches, poll status, and download results with pf_ API keys. The API is the same one the studio uses, so anything you can do by hand you can automate.

Styles

"a black cropped athletic set with white sneakers, city sidewalk" — one outfit, one seed, four styles.