The photoshoot that starts itself.

A node canvas in Uwear where you wire a trigger to production steps: shoots, edits, video, an automatic quality check, and delivery. Publish a version, switch the automation on, and it runs on its own each time the trigger fires, spending credits only within the limits the published version fixes.

When you catch yourself submitting the same brief for every new product: the same art direction, model, crops, and checks, with only the garment changing. Wire those steps once in the canvas, publish, and switch it on; from then on each upload, tag, or new outfit runs them without a brief.

Three things you already do: upload clothing, add a tag to a product, or create an outfit. You can also start runs by hand from the builder, or from your own systems through the API with an idempotency key.

Credits, at the same rates as running the steps yourself. The builder totals the estimate before you publish: one run, and the worst case if every take is rejected and re-shot the full allowance. Each run reserves its estimate at start; if credits are short the run is rejected instead of half-running, and steps that fail on our side refund what they reserved.

When you add a Check quality step, the automatic reviewer scores every take, keeps the good ones, and re-shoots rejects up to the allowance you set; each re-shoot is billed like the original take. The check is a step you place where you want it, never a review we force.

Each automation has its own on and off switch, and a company-wide master switch stops every automation at once. Stopping requires a reason, which is recorded in the audit trail. Runs already in flight finish under their own retry rules rather than being cut off mid-step.