Compare

How we compare

Most organisations looking at us are looking at two or three other things at the same time, usually a global badge platform and a design tool. These pages set out what each is actually built for, so you can rule us out quickly if we are the wrong shape.

How these pages are written

Every comparison page here carries a section saying who should choose the other product, and means it. There are requirements we do not meet, the clearest being interoperability: our credentials are checked on their own verification page and cannot be read by another platform, so an organisation that needs that should use a platform built for it.

We compare on structure rather than on feature checklists and price tables. Competitors change both quarterly, a page that tracks them is out of date within a month, and a stale price is a worse guide than no price. What changes slowly is the shape of a product: whether your team operates it, what a recipient has to do to receive a credential, and what a stranger has to do to check one. Those questions decide most of these choices.

Where a fact about another product matters to the argument, we describe what it is designed to do rather than assert what it costs today. Check current pricing with the vendor. That now includes ours: our own price is published in full, VAT shown, on our pricing page, and it is left out of these comparisons so a table never sets one number we can keep current against several we cannot.

Not sure which category you need?

Tell us what you issue, how often, and who asks you to confirm it later. If a design tool covers you, that is a short and useful conversation.