Skip to main content
No. The user confirms the sign-in in an app they already have — Telegram, WhatsApp, another messaging app or email. There is no separate authenticator to install.
There are several channels, plus email — the user picks the one they have. The list is on Supported channels.
In your own deployment — yes, and that is the normal mode. Channels are configured with your credentials: Channels:Telegram:BotToken, Channels:Max:BotToken and so on. The bot is yours, the user talks to it under your name, and the tokens live in your secret store. The full list of keys is in the configuration reference.In the cloud the set of enabled channels is decided by the project owner in the Console; ask them whose credentials are in use there.
Yes, that is the primary delivery model: Veriqa runs inside your perimeter, next to your auth system. The other option is Veriqa Cloud, for when you would rather not run a server.
The same product, run and maintained by someone other than you: you get a project with its own issuer, applications and channel set, managed by the project owner in the Console — with no edits or redeploys of your application.The cloud suits situations where running a server is not worth it: small sites, off-the-shelf CMSes, a quick start. Details and current status are in Veriqa Cloud.
Channel messages are not billed per message the way SMS is: in WhatsApp, Veriqa replies to the user’s message without a template, and under Meta’s current pricing such replies are free. At any significant sign-in volume, that is a direct saving. Veriqa’s own commercial terms are not published in this documentation — ask about them separately.
No. Veriqa sits alongside it: your system still owns user accounts, while Veriqa issues the tokens and adds the trusted channel the user confirms in. To an application Veriqa is a standard OpenID Connect provider, so your stack does not matter.
No — and this question only concerns .NET. There Veriqa is a connector on top of OpenIddict, which remains the foundation of authentication. On any other stack OpenIddict is not involved at all: the application talks to Veriqa over plain OpenID Connect.
Passkeys are phishing-resistant by design — a higher security bar. Veriqa offers the same convenient flow for simpler scenarios, and works where cross-device passkeys break: Bluetooth off, a virtual machine, a remote desktop.
In part. Some channels — Telegram, for one — report whether the sender is a bot; Veriqa returns that flag in the claims, and the restriction policy can block such sign-ins. This is not an anti-fraud system, but it is a cheap filter that works before an account is created.
Yes. It works with WordPress, Drupal, TYPO3, Joomla and Bitrix without changes on the Veriqa side.The caveats: Joomla’s free version only signs people in to an existing account, Drupal and Joomla require an email address on every sign-in (and Telegram provides none), and the Email channel has been verified with a CMS on Bitrix only. All of it is laid out in Veriqa in a CMS.