Two entries whose answers actually diverge

Each page here puts two entries beside each other on a column where their answers genuinely diverge. Pairs whose answers merely differ in price are not here, because a price gap is a packaging decision rather than a finding. As of 2026-09-22.

Fig. 1 The test is whether a reader would act differently, not whether the two values look different in a table.

A comparison is worth a page when the two vendors are not answering the same question in different words. A switch in settings and a benefit on a plan grid are two different mechanisms with two different sets of consequences, and putting them in one row of the support table flattens that into a column called control. Putting them on one page does the opposite.

Pairs are chosen by the shape of the disagreement, not by product category. Two avatar tools that both stop marking at the same price are less interesting than an avatar tool and a film generator whose first paid plans disagree about whether payment removes anything at all. The register is organised around statements, so the pairs are too.

Nothing on these pages is scored, ranked or recommended. Both columns carry the vendor's own wording, the address it was read from and the date it was read, and the argument in the prose is about what the two statements let a reader do, not about which product is better run.

1The pairs

A switch and a benefit — One vendor's mark comes off with a setting; the other's comes off with a subscription.
Two off-switches — Two documented ways to stop the mark, one held by an integrator and one by an operator.
Buying later, or not — One crossing point cleans whatever comes next; the other cannot reach the files already made.
The first payment — On one entry the cheapest paid plan is clean; on the other it is still marked, and the page says so.
No free plan, or a stated one — One vendor publishes no free plan at all; the other lists its own watermark among free features.
A standard or a price — One entry names the standard in the file and no plan; the other names a plan and nothing in the file.
Who reads the signal — Two named schemes, and only one comes with a route somebody outside the vendor can use.
Inside or around — A manifest attached around the picture and a signal carried inside it fail in opposite directions.
One price, two nouns — Two avatar tools cross at the same figure and use different words for the thing being removed.
Marking and licence — Two grids where the marking boundary and the commercial licence sit in different places.
Crossing points with no figure — Two boundaries whose price cannot be quoted, for two entirely different reasons.
A reference and a card — An interface reference that lists everything and no provenance field, beside a card that names two mechanisms.
Trial output, two shapes — One free tier leaves a permanent mark on everything it made; the other simply runs out.
A reason, or no route — One vendor publishes a switch and an argument for using it; the other publishes no route at all.
Ten dollars, or twenty-eight — Two grids, one where the first payment is enough and one where the third plan is.
The described marks — The two entries that say what their visible mark actually looks like, and both scope it to one surface.
No free plan, or one that runs out — Neither has a standing free tier, and only one of them ever produced a marked file.
Outside a price list — Two marking statements published somewhere other than a pricing page, and only one names anything.
Named, or avoided — One grid lists its own watermark among free features; the other never prints the word at all.
Two routes, one model — Both sell the same models two ways; one documents both routes and they disagree, the other stays silent.

Ordered by the column they disagree on, so the pairs arguing about the same thing sit together.

Elsewhere in the register: Generators, Fields, Readings, Implementers, Questions, Findings, Source documents, Terms, Learn, Data. Field definitions live on the protocol page.