Comparisons

These pages compare Cendarum to categories, not to named products.

That is a deliberate constraint, and it costs us something. “Cendarum vs <competitor>” pages attract search traffic, and we are not writing them.

The reason: we have not tested any competitor’s current behaviour, and asserting specifics about someone else’s product from their marketing pages is exactly the kind of sloppiness the rest of this site is built to avoid. A comparison table where our column is verified and theirs is guessed is not a comparison — and getting caught doing it would undermine every other claim we make, which are the claims that actually matter.

So: categories, described in terms of the architectural trade-off that separates them from us. Those trade-offs are structural and don’t drift with someone’s release notes.

The pages

Page	The comparison
vs a .env file	The real incumbent, and the one to read first
vs cloud secret managers	Server-side decryption, and what it genuinely buys
vs password managers	Adjacent tools, different workflow
When not to use Cendarum	The honest disqualifiers

The rule these pages follow

Every one of them names something the alternative does better. Not as a rhetorical move before the pivot — actually better, in cases where you should pick it.

If a comparison page only lists reasons to choose us, it is an advertisement wearing a table’s clothes. The most useful page in this section is when not to use Cendarum, and if you are evaluating seriously you should read it first.