> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 0.6 — first public release

> Veriqa 0.6, the first public release: sign-in and confirmation through trusted messengers behind a standard OpenID Connect provider, embedded in .NET or run as a server.

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](/docs/guides/supported-channels) covers what each
  one adds to the claims and whether the user has to send a message;
  [Channel setup](/docs/guides/channels) 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](/docs/guides/channels#which-mode-to-choose).
* **A channel of your own** as a .NET adapter inside your host —
  [Build your own channel adapter](/docs/guides/custom-channel-adapter).

### Deployment modes

* **Embedded in ASP.NET Core.** Veriqa extends OpenIddict in your own host and leaves token issuance
  to it — [Quickstart .NET](/docs/quickstart/dotnet).
* **Self-hosted server in Docker.** Your application stays a plain OIDC client on any stack —
  [Quickstart self-hosted](/docs/quickstart/self-hosted), with client quickstarts for
  [Node.js](/docs/quickstart/node), [Java](/docs/quickstart/java) and [Python](/docs/quickstart/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](/docs/quickstart/os-service).

### Scenarios

* [Passwordless sign-in](/docs/scenarios/passwordless-login) — a QR code on screen, confirmation in a
  messenger, sign-up in the same step.
* [Sign-in with channel linking](/docs/scenarios/channel-linking) — the user signs in and the product
  gains a live channel.
* [Second factor and step-up](/docs/scenarios/step-up) — a fresh confirmation before a sensitive
  operation.
* [Replacing SMS codes](/docs/scenarios/sms-replacement), [leads without CAPTCHA](/docs/scenarios/lead-capture)
  and [account recovery](/docs/scenarios/account-recovery).
* [Sign-in surfaces](/docs/scenarios/surfaces) — smart TV, kiosk, a device with no keyboard.
* [Server-to-server confirmation](/docs/reference/confirmation-api) — 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](/docs/integrations/confirmed-form) 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](/docs/concepts/completion).
* A transaction store on InMemory, EF Core or Redis, and the OpenIddict database on PostgreSQL or
  SQL Server — [Storage](/docs/guides/storage).
* The [initiator context](/docs/concepts/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](/docs/guides/data-handling).
* Sign-in page design, localization and extension points —
  [Configuration & customization](/docs/guides/customization).
* Verified integrations with [CMS engines](/docs/integrations/overview) and
  [business systems](/docs/integrations/apps).

## 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](/docs/quickstart/os-service)
  explains how to download and verify them.
* **Source code** — the repository at [veriqa.app/source](https://veriqa.app/source).

| Area | Packages |
| - | - |
| Server and engine | `Veriqa.Core.AuthServer`, `Veriqa.Core.TransactionEngine`, `Veriqa.Core.Configuration`, `Veriqa.Core.Contracts` |
| Channels | `Veriqa.Core.ChannelAdapter`, `Veriqa.Core.BaseChannels` (metapackage: Telegram, WhatsApp, Email), `Veriqa.Core.ChannelAdapter.Telegram`, `Veriqa.Core.ChannelAdapter.WhatsApp`, `Veriqa.Core.ChannelAdapter.Email`, `Veriqa.Core.ChannelAdapter.Max`, `Veriqa.Core.ChannelAdapter.Redis` |
| Stores and events | `Veriqa.Core.TransactionEngine.EntityFrameworkCore`, `Veriqa.Core.TransactionEngine.Redis`, `Veriqa.Core.TransactionEngine.RabbitMq`, and the PostgreSQL and SQL Server migrations: `Veriqa.Core.TransactionEngine.Migrations.*`, `Veriqa.Core.AuthServer.Migrations.*` |
| Audit trail | `Veriqa.Core.AuditTrail`, `Veriqa.Core.AuditTrail.EntityFrameworkCore`, `Veriqa.Core.AuditTrail.Migrations.*` |
| Other | `Veriqa.Core.AuthServer.MaxMind`, `Veriqa.ServiceDefaults`, `Veriqa.Samples`, `Veriqa.Core.ChannelLocales` |

## 0.6.1

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

## Known limitations

[Known limitations](/docs/reference/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](/docs/reference/oidc-capabilities).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.