Trailer takes the catalogue export you already have and gives it back with three new columns on the end — a title, a description and a tag line rewritten for the platform you actually sell on, listing by listing.
Nothing opens in this browser — this one takes a job and does the work on our own graphics cards in Oregon. The free allowance below is how you try it: 25 rows, no card and no payment, on the key you are issued.
Work in, work out. A CSV goes up, the same CSV comes back with your own columns untouched beside the new ones. Every rewrite runs on our own GPUs in Oregon.
The problem
Half the titles are the filename. A third of the descriptions are one line. The tags are whatever the uploader remembered that afternoon. Rewriting two thousand of them by hand is a fortnight of work nobody in a small operation has, so it never happens — and a listing nobody can find earns nothing for as long as it sits there.
added, never replaced. Your original title, description and tags come back in the same cells they went in. Nothing you wrote is overwritten, so a bad rewrite costs you a column, not a catalogue.
Every rewrite runs on Tower 1's own graphics cards in Oregon. Not a hosted model, not an advertising company's API, and nothing about your catalogue is sent to anyone who might train on it.
A row that fails, or that the word gate holds back, is not charged. That is a rule in the code rather than a goodwill policy you have to ask for.
How it works
Whatever your store already gives you — a CSV with a title column, a description column and ideally a tag column. No credentials, no plugin, nothing installed. Trailer never logs in to a platform as you.
The rewrite is per surface, because the surfaces are not alike: a clip store wants a title that reads like a scene, a tube site wants one that reads like a search. One job, one platform, stated out loud rather than guessed.
The same rows in the same order, three columns longer. Open it in a spreadsheet, read a dozen, and import what you accept. Nothing is pushed anywhere on your behalf.
What it will never do
Everything that could go wrong at scale here goes wrong in your store, not in a file on your disk — so Trailer never gets near one. The whole product is a file that comes back.
Pricing
Every key starts with 25 rows of credit that cost nothing and are not a trial — no card, no expiry, no reduced output. After that a pack is credit against rows, and credit does not expire. Catalogues are not rewritten monthly; they are rewritten once and topped up when new titles land, so a subscription would be charging you for the eleven months you are not using it.
Enough to read real output on your own catalogue and judge it.
A working back catalogue, done in one pass.
A library built up over years, in one job.
Flat per row, never a percentage of what the listing earns. Metering is counted after Tower 1 returns something usable, so a row that failed was never counted in the first place — that is in app/store.py, not in a support policy. Your licence key is emailed to you within two working days of payment.
Checkout is our own bitcoin server, not a card processor. The units you buy are added to your key: buy from the Buy more box inside the program and they arrive on their own once the payment confirms, or buy here and paste the invoice number from your receipt into that box.
Questions
No, and there is nowhere to give it. You export a file and you import a file.
Every tool that asks for your platform login is asking you to bet your income on their security. We will not ask you to make that bet, which is why the product is shaped as a file in and a file out.
It comes back marked, with the reason, and it is not charged.
The usual causes are an empty description, a title that is only a filename with no words in it, and a row where the word gate held the output back. All three are visible in the returned file rather than quietly skipped.
Rewritten from your own row, one row at a time, so the output is as varied as the input.
The one thing deliberately made consistent is length and structure for the platform, because that is what the platform is measuring.
It cannot. The model is on our own graphics cards in Oregon and nothing about the job leaves the building.
This is the reason the product costs what it costs rather than being a wrapper around an API — the hardware is ours and the electricity bill is ours.
A key. One line of text, issued to you and shown exactly once — only its hash is kept here, so it cannot be looked up later and we could not tell you what yours is. Every key arrives with a free allowance already on it, which is the tier at the top of the pricing above, and the work starts the first time you send a job with that key on it.
Each job is metered in the unit named in the pricing, and a unit that fails — a file that will not read, a row the model held back — is not charged and is named in the job report rather than silently skipped. When an allowance runs out the next job is refused before any work starts, with the number it used printed on the refusal.
More units are bought in bitcoin. The checkout is a bitcoin server we run ourselves. Buy from the Buy more box inside the program and the units are added to your key on their own as soon as the payment confirms; buy from the plan buttons above and paste the invoice number from your receipt into that same box. Each payment adds its units once, to one key.
Export your catalogue, send fifty, read what comes back. Either the titles are better than the ones you have or they are not, and you will know in ten minutes rather than after a subscription.