About · Pessac, France
One tool, built for one contributor.
TB Dev is one person: Thomas Berthou. His father films underwater footage and sends it to four stock marketplaces. Rushlot is the tool he built to check each clip, describe it, and deliver it to his father’s own accounts, so a mistake in a listing never turns into an account that can no longer sell.
Scroll to read the story
The origin
Why it exists.
A re-upload is the most-attested cause of a stock account being suspended: a marketplace sees the same footage arrive twice and reads it as an attempt to game the catalogue, not as a fix. So the rule that matters most is the simplest one to state and the hardest one to keep by hand across four marketplaces and dozens of clips a week: review before upload, never after, and nothing sent twice.
The people
One maker. One contributor.
The tool and the footage it sends come from the same family.
Builds Rushlot
Wrote the tool that checks each clip, describes it and delivers it to his father’s own marketplace accounts.
Films the footage
Films underwater footage and sends it to Adobe Stock, Shutterstock, Pond5 and Getty Images.
September 2026
What went wrong, and what changed
In September 2026, before any of this was automated, four separate mistakes reached his father’s live listings. Each one is why a particular check exists in Rushlot today.
- Mistakes that reached live listings
- 4
- Clips in one lot published with French titles
- 12/34
- Characters of French in the longest title
- 189
- Characters of a title Pond5 keeps
- 80
- Defect 01
French titles reached two marketplaces
12 of the 34 clips in one lot were published with the contributor’s own French titles, up to 189 characters of French, on Pond5 and Getty Images. The agreement check that was meant to catch it compared English words on both sides, so a French title could only ever "agree" with itself and passed through untouched.
What changedMetadata generation now also renders the contributor’s own title into English and checks the published text against that rendering, not against itself. His words still decide what gets published; they are carried in the language the buyer searches in.
- Defect 02
An invented tag blanked a Pond5 listing
A description once opened with a tag the model invented, an angle bracket it had no reason to write. Shutterstock refused the row outright, Adobe carried the tag into moderation as the clip’s title, and Pond5’s own page broke on it and showed the item with no title and no description at all.
What changedA description carrying that kind of markup is dropped before a marketplace ever sees it, and a check now reads the exact text about to be published, not the draft that produced it.
- Defect 03
A title longer than a marketplace could hold
Pond5 keeps only the first 80 characters of a title. A title longer than that was going out untested against the smallest field that had to hold it.
What changedThe same pre-publish check now measures every generated title against the shortest limit any of the four marketplaces impose, and refuses to publish one that does not fit, rather than letting a marketplace silently truncate it.
- Defect 04
The same clip delivered twice
On 2026-09-17, one lot held the same shot twice under two different file names, an export and a re-export made by mistake. Every existing guard compared file paths, not names, so it went to Adobe, Getty and Shutterstock as a duplicate pair, the single most-attested cause of a stock account being suspended.
What changedEvery clip in a lot is now compared by name as well as by path before a byte moves, across the whole lot, not just the batch being sent that moment. Neither twin of a colliding pair goes out; the rest of the lot sends around them.
Where it sends
Four marketplaces. Your own accounts.
Open now · beta testers
Delivery sheet · one lot
How each marketplace receives it
- Adobe StockSFTP for qualified accounts, metadata embedded in the file.
- ShutterstockFTPS with your account credential, metadata through the portal’s CSV import.
- Pond5FTPS with a separate FTP password, metadata in the file and through Apply CSV.
- Getty ImagesThe ESP web uploader in your browser, metadata through ESP’s CSV.
Every time
- Copies per clipOne per marketplace
- Who submitsYou, on the marketplace
The promise
The rules Rushlot runs on.
Straight to your account.
Your files go from your own computer to your own marketplace account, over the transport that marketplace itself accepts. Nothing passes through a server of ours.
Review first, never after.
You review every clip before it uploads, never after. A re-upload is what gets an account suspended, so nothing is ever corrected by sending it again.
Submit stays yours.
Uploading is not submitting. Rushlot never presses a marketplace’s own Submit button; that decision stays yours.
Nothing invented.
Nothing is invented: no scientific name that failed a species registry, no place, no date, no category your own title and keywords do not support.
No challenge solved.
No CAPTCHA is ever solved, no browser is ever disguised as something else, no undocumented API is ever called. A marketplace that puts up a challenge stops the run and hands it back to you.
rushlot.com · Pessac, France
Send your next lot, reviewed first.
Rushlot opens in waves, Mac first. Leave your e-mail and we write when your turn comes.