Verne Passepartout · Telegram Auth-as-a-Service
Passwordless Login for Your Users, Powered by Telegram No Passwords, No Email Flows, Zero Friction
Let your tenant's end-users sign in with a single tap in Telegram. Passepartout handles the bot bridge, tenant-scoped identities, and secure tokens — so you ship authentication without building it.
curl -X POST https://api.vernesoft.com/v1/passepartout/login/start \
-H "Authorization: Bearer vrn_passepartout_•••"
# => { "nonce": "n_9f2c…", "deep_link": "https://t.me/your_bot?start=n_9f2c…" }The Password Problem
Why Rolling Your Own Auth Slows You Down
Passwords, email verification, and reset flows are a constant source of friction, support tickets, and security risk. Building them yourself means weeks of work you will maintain forever.
Traditional / In-House Auth
- ✕ Password storage and reset flows you must secure and maintain forever.
- ✕ Email verification delays and deliverability issues block sign-ups.
- ✕ Every tenant's users blur together without hard isolation boundaries.
- ✕ Bot credentials scattered across configs and env files in plaintext.
Verne Software Passepartout
- ✓ Passwordless Telegram login — no passwords to store or leak.
- ✓ Instant sign-in via deep link — no email round-trips.
- ✓ Tenant-scoped identities isolated per tenant in Ory Kratos.
- ✓ Bot tokens encrypted at rest with AES-256-GCM.
Core Features
Everything You Need to Ship Telegram Auth
Passwordless Telegram Login
Your users authenticate with a single tap in Telegram. No passwords to remember, store, or reset — and no email verification flows to maintain.
Tenant-Scoped Identities
Every tenant's end-users are fully isolated. Identities live in a shared Ory Kratos, namespaced per tenant, so one customer's users never overlap with another's.
Drop-In Bot Setup
Create a bot with @BotFather, paste the token into your dashboard, and enable it. Passepartout handles the rest — no public webhook or infrastructure required.
Deep-Link Login Flow
Start a login to receive a nonce and a t.me deep link. The user taps Start in your bot, and you poll for status until an access token and user profile are returned.
Encrypted Bot-Token Storage
Bot tokens from @BotFather are encrypted at rest with AES-256-GCM. The bridge uses Telegram long-polling, so you never expose a public webhook endpoint.
Multi-Language SDKs
Official SDKs for Node, PHP, Python, and Rust ship a first-class passepartout resource, so you can integrate login in minutes from any stack.
Nautilus Ecosystem
The Perfect Match with Verne Gate
Passepartout brings your users in through Telegram, while Gate secures your own API keys and admin access. Deliver post-login events reliably with Relay — one platform for identity and infrastructure.
Developer Experience
Add Telegram Login via API
Start a login, share the deep link, and poll for completion — in any language. Validate the returned tokens with a single introspection call.
# 1. Start a login — returns a nonce and a Telegram deep link
curl -X POST https://api.vernesoft.com/v1/passepartout/login/start \
-H "Authorization: Bearer YOUR_NAUTILUS_KEY" \
-H "Content-Type: application/json"
# => { "nonce": "n_9f2c…", "deep_link": "https://t.me/your_bot?start=n_9f2c…" }
# 2. Poll for status until the user taps Start in your bot
curl "https://api.vernesoft.com/v1/passepartout/login/status?nonce=n_9f2c…" \
-H "Authorization: Bearer YOUR_NAUTILUS_KEY"
# => { "status": "completed", "access_token": "…", "user": { "id": "…" } }FAQ
Frequently Asked Questions
How does the Telegram login flow work?
Your app calls POST /v1/passepartout/login/start to get a nonce and a t.me deep link. The user opens it and taps Start in your bot; your app then polls GET /v1/passepartout/login/status until it returns a completed status with an access token and user profile.
Do I need to run a public webhook for the Telegram bot?
No. The Passepartout bridge connects to Telegram using long-polling, so there is no public webhook to expose or secure. You only configure your bot token from @BotFather in the dashboard.
How are my users kept separate from other tenants?
Every tenant's end-users are namespaced independently in the shared Ory Kratos identity store, and each tenant configures its own Telegram bot. Bot tokens are encrypted at rest with AES-256-GCM.
Get Started Today
Give Your Users
Passwordless Login
Skip the passwords, the email flows, and the maintenance. Ship secure Telegram authentication for your platform today.

