0.6 — first public release

Veriqa 0.6.0 was published on September 23, 2026 — the first release anyone can install. To your application Veriqa is a standard OpenID Connect provider; the user confirms the sign-in in a messenger or a mailbox they already use — Telegram, WhatsApp, other channels or Email.

​

What’s in it

​

Channels

• Built in: four channel adapters. Each channel is a separate adapter and is switched on in configuration. Supported channels covers what each one adds to the claims and whether the user has to send a message; Channel setup walks through setup end to end.
• Email in two modes: the classic magic link, on by default, and the one-tap email, where the user sends a pre-filled email — which mode to choose.
• A channel of your own as a .NET adapter inside your host — Build your own channel adapter.

​

Deployment modes

• Embedded in ASP.NET Core. Veriqa extends OpenIddict in your own host and leaves token issuance to it — Quickstart .NET.
• Self-hosted server in Docker. Your application stays a plain OIDC client on any stack — Quickstart self-hosted, with client quickstarts for Node.js, Java and Python.
• OS service. The same server from a self-contained archive as a systemd unit or a Windows service — no Docker and no .NET runtime on the machine — Install as an OS service.

​

Scenarios

• Passwordless sign-in — a QR code on screen, confirmation in a messenger, sign-up in the same step.
• Sign-in with channel linking — the user signs in and the product gains a live channel.
• Second factor and step-up — a fresh confirmation before a sensitive operation.
• Replacing SMS codes, leads without CAPTCHA and account recovery.
• Sign-in surfaces — smart TV, kiosk, a device with no keyboard.
• Server-to-server confirmation — your backend asks a person to confirm an action, such as a payment or a data transfer, with no sign-in and no redirect; Confirmed form submission builds on it.

​

Also included

• Three ways to learn that the confirmation happened: the redirect back, live status over SignalR and status polling — How a sign-in completes.
• A transaction store on InMemory, EF Core or Redis, and the OpenIddict database on PostgreSQL or SQL Server — Storage.
• The initiator context in the confirmation message — who started the sign-in and from where, with an optional offline GeoIP provider.
• An audit trail, off until you enable it — Security and data handling.
• Sign-in page design, localization and extension points — Configuration & customization.
• Verified integrations with CMS engines and business systems.

​

Where to get it

• NuGet packages on nuget.org, version 0.6.0 for all 26 packages. The core is MPL-2.0; Veriqa.Core.Contracts, Veriqa.ServiceDefaults and Veriqa.Samples are MIT.
• Docker image veriqa/veriqa on Docker Hub, tags 0.6.0 and latest, linux/amd64: docker pull veriqa/veriqa:0.6.0.
• OS service archives for linux-x64, linux-arm64 and win-x64 with a SHA-256 sums file — attached to the repository’s releases; Install as an OS service explains how to download and verify them.
• Source code — the repository at veriqa.app/source.

​

0.6.1

A maintenance update with no change in behavior: package descriptions, search tags and package READMEs.

​

Known limitations

Known limitations lists what 0.6 does not have and what behaves differently than you might expect; deviations from the OIDC specifications are in OIDC and OAuth 2.0 support.