Batch-process real estate photos at studio scale

Whole-listing staging is the single-listing flow: drop one shoot, get one ZIP with consistent style across the rooms. Batch processing is the pipeline flow — many listings, many operations (staging + declutter + day-to-dusk + sky + repaint), running in parallel through the same queue, with API + webhooks for engineering teams. If you're a solo agent staging one listing, use whole-listing staging. If you're a studio, brokerage, or content ops team running mixed operations across many properties a week, batch processing is the right surface.

Yes. Operations are per-photo metadata, not per-batch. A single submission can carry virtual staging on the empties, decluttering on the lived-in rooms, day-to-dusk on the twilight exteriors, sky replacement on the gray-sky shots, and wall repaint on the loud-color rooms — all running concurrently. The output ZIP is organized by listing and operation. Most competitors don't support this and force three separate batch uploads for three operations.

99+ photos on every paid tier with no hard upper cap. Studios regularly submit 300–500 photo batches across 10–20 listings. Throughput is bounded by queue concurrency, not by your plan tier — the 500th photo doesn't take longer than the 1st on a per-photo basis. For reference, REimagine Home caps batch at 50 photos on a $99/mo Agency plan; Apply Design, VSAI, Spacely, and HomeDesigns have no batch workflow on their public pricing pages.

REST endpoints to submit a batch, attach photos with per-photo operation metadata, and receive signed (HMAC-SHA256) webhook callbacks per listing as renders finish. Submissions take an Idempotency-Key header — retry the same key after a timeout and you get the same job back, never a duplicate charge. Available on the Brokerage tier — not gated behind Enterprise like Collov ($127/mo) or VSAI ($79/mo). Email brokerages@edensign.io to provision keys.

Yes. Drop a folder tree — `12 Maple St/`, `47 Oak Ave/`, `89 Pine Ln/` — and the output ZIP returns the exact same folder structure, with each listing's renders in its own subfolder. Per-listing manifests list the operation chain applied, render IDs, and any flagged retries. No file renaming, no MLS reorganization step.

Per-photo failure isolation: a failed render is retried twice with exponential backoff, and if it still fails it's flagged in the per-folder manifest while the rest of the batch continues. The other 499 photos don't stall. You can re-submit just the failed slice with the same idempotency key without re-paying for the successful 499. Webhook callbacks fire per-listing, so your downstream pipeline reacts as each listing finishes rather than waiting for the whole batch.

Yes — point Edensign at a Drive or Dropbox folder, and we watch it for new listings, pick them up as your photographers drop them in, run the configured operation chain, and write the resulting ZIP back to a sibling folder. No Zapier or middleware required. Studios use this to fully automate the gap between 'photographer finishes shoot' and 'listing renders are in the brokerage's MLS folder.'

Same $0.59/photo on Brokerage paid annually, whether you submit 1 photo or 500. We deliberately don't price batch differently — it keeps your unit economics predictable, especially for studios that bill clients per-photo. There's no Agency-tier upcharge to unlock batch (REimagine charges $99/mo for it) and no volume floor. Larger commitments are available for >5,000 photos/month — email brokerages@edensign.io.

Yes. The batch submission accepts a `priority` hint per listing — useful when a brokerage-tier customer has one rush listing and three standard ones in flight. You can also cap concurrency per workspace if your pipeline downstream can't drink from the firehose. Defaults work for studios out of the box; only touch them if you have a specific bottleneck in your delivery side.