Get started
- Sign-in methods compared
- Basic scenarios
- Getting the phone number and email
- Collecting extra claims
- Ready-made recipes
- .NET quickstart
- Node.js quickstart
- Java quickstart
- Python quickstart
- Self-hosted quickstart
- Install as an OS service
- For AI agents
- FAQ
Samples
- Samples
- Sign-in on a website via a messenger
- Step-up, second factor, human-in-the-loop
- Nova Stream — streaming on a TV
- Helio — customer support
- Claude Code mod
Videos
- Sign-in on a website
- Sign-in on a TV
- Step-up on a TV
- Sign-in on a desktop
- Step-up on a desktop
- Sign-in on a phone
- Step-up on a phone
- Claude Code: a tool call
- Claude Code: a long command cycle
- Claude Code: two approvers
Concepts
- How Veriqa differs
- Architecture
- How the auth flow works
- Hop mode
- OIDC + Veriqa explainer
- Initiator context
- How a sign-in completes
Installation and configuration
- Configuration & customization
- Declare your own configuration keys
- Storage
- Client compatibility
- Behind a reverse proxy
- Preparing for production
- Security and data handling
Monitoring
Messengers and channels
Use cases
- All use cases
- Integration scenarios
- Passwordless sign-in and registration
- Sign-in and channel linking in one action
- Second factor, step-up and action confirmations
- Replacing SMS codes
- Leads and feedback without CAPTCHA
- Account recovery
- Sign-in surfaces
- Smart TV and keyboard-free surfaces
- Place and identity
- Approving AI-agent actions
- Stronger sign-in with a chain of channels
- Resilience to a personal-data leak
- Honest voting on any website
Cloud
- Veriqa Cloud
- Connecting to the cloud
- Channel buttons on your own page
- Sign-in window settings (ui_config)
Ready-made recipes
- Ready-made recipes
- Passwordless sign-in for a Node.js, Python or Java web app
- Sign in with Telegram on a WordPress site
- Moving off SMS codes
- Confirming a sensitive operation in a messenger
- Team sign-in to GitLab, Grafana or Nextcloud
- A website form with a verified contact
- Sign-in on a Smart TV or a kiosk
Veriqa and CMS
Veriqa in business systems
Reference
- Configuration reference
- Server-to-server confirmation API
- OIDC and OAuth 2.0 support
- Known limitations
Releases
- Coming next
- 0.6.6 — sign-in with a code and fixes from live runs (upcoming)
- 0.6.5 — Messenger, WeChat and Viber (upcoming)
- 0.6.4 — Instagram, sign-in page texts and PathBase (upcoming)
- 0.6.3 — the sign-in page and channel restriction policies (upcoming)
- 0.6.2 — hop mode, the HTTP channel and claim completion (upcoming)
- 0.6 — first public release