View on Desktop

Plan Manager is desktop-only for now. Open this link on a computer to create plans and manage nodes.

planmanager.sentinel-p2p.com

Back to sentinel.co

dVPN Plan Manager

Build and operate a subscription dVPN service on Sentinel. Create plans, pick your nodes, and connect any payment method — all from one console.

Steps to create a subscription plan

1

Register provider

Claim your on-chain operator identity.
2

Add dVPN nodes to the plan

Curate and link the nodes your subscribers will connect to.
3

Configure card / 3rd-party off-chain payments

Trigger subscriptions from Stripe, PayPal, or any checkout you already use.
4

On-chain fee-auth gasless transactions

Issue fee grants so subscribers connect without ever holding a token.

Open source on GitHub

Plan Manager is fully open-sourced — clone the repo and run it locally on your own machine.

Sign in to Plan Manager

Pick a sign-in method.

Sign in with email

Enter your email. Privy will send a one-time code, then create or unlock an embedded Sentinel wallet for your account. Powered by Privy.

Sign in with recovery phrase

Paste your 12 or 24-word mnemonic. It is encrypted with AES-256-GCM and stored only in an httpOnly cookie scoped to your browser. The server never writes plaintext to disk.

recovery phrase

Your seed is encrypted in your browser cookie with AES-256-GCM. The server never sees plaintext after this request, never logs it, and never writes it to disk.

What we store: a single httpOnly + SameSite=Strict cookie (spm_sess) holding your mnemonic encrypted with AES-256-GCM. Random 12-byte IV, 16-byte auth tag, scoped to this origin only.
Where the key lives: a 32-byte server key, persisted as .session-key with 0600 permissions, or supplied via SESSION_KEY env var. The key never leaves the server; the cookie never leaves your browser.
What happens on each request: the cookie is decrypted in memory, the wallet is derived inside an AsyncLocalStorage context for that one request, then dropped. No globals, no logs.
On logout: the cookie is cleared, the per-process wallet cache entry for this mnemonic is dropped, the page is reset.
Verify yourself: lib/session.js

Create a new account

We'll generate a 24-word mnemonic for your account. The phrase is encrypted with AES-256-GCM and stored in an httpOnly cookie scoped to your browser — it is never written to the server's disk. Write the phrase down before you continue. If you lose it, the wallet and any funds are gone forever.

Back up your recovery phrase

Write these 24 words down in order. Store them somewhere safe and offline. This is the only way to recover your wallet.

I have written down my 24-word recovery phrase and understand that it is the only way to recover my wallet. Sentinel cannot restore it if lost.

OR

You will need P2P tokens. Plan creation costs ~0.5 P2P, linking ~1–2 P2P per node. A freshly funded operator wallet with 8 P2P covers the full first-run flow.

Security FAQ

How each sign-in method protects your key — with direct links to the source.

Keplr

Key custody: Private key stays inside the Keplr extension. Server never sees a key, mnemonic, or seed.
Signing flow: Server returns unsigned signDoc.

Keplr signs locally via signDirect.

Server decodes AuthInfo, derives sent1…, rejects mismatched session.
Login: ADR-36 signArbitrary over a one-time nonce. Cookie issued only on signature verify.

Source server.js · keplr-challenge / keplr-login server.js · /api/tx/broadcast-signed

Email Privy

Key custody: Private key in Privy's embedded-wallet enclave, scoped to your authenticated email. Plan Manager holds only an auth token.
Signing flow: Server returns unsigned signDoc.

Privy → Cosmos adapter signs under your session.

Same pubkey-derivation check as Keplr.
Recovery: Re-login with the same email. MFA and account-recovery via docs.privy.io.

Source blue-js-sdk #23 · Privy signer adapter blue-js-sdk #24 · SentinelClient wiring

Recovery phrase

Encryption: AES-256-GCM, random 12-byte IV + 16-byte auth tag per session.

32-byte server key from SESSION_KEY env var or .session-key (0600).
Cookie: spm_sess · HttpOnly · SameSite=Strict.

Origin-scoped. Cookie stays in browser; key stays on server.
Per request: Decrypted in memory inside AsyncLocalStorage for one request, then dropped. No globals, no logs, no disk.

Source lib/session.js · encrypt / decryptMnemonic lib/session.js · runWithSession

Create new wallet

Generation: Fresh BIP-39 24-word mnemonic via @cosmjs/crypto.

Shown once for offline backup.

Backup-confirm checkbox required before session finalises.
Storage: Same path as Recovery phrase: AES-256-GCM in the spm_sess HttpOnly cookie.
Critical: Lose the 24 words and the wallet — plus any P2P — is gone. Sentinel cannot restore it.

Source server.js · /api/wallet/generate server.js · /api/wallet/confirm-backup

Sentinel

Plan Manager

Main

Dashboard

Provider Identity

Create Plan

Your Plans

dVPN Servers

Add Nodes

Your Nodes

Operations

Payment

Subscribers

Earnings Soon

Fee Grants

CLI

Install CLI

CLI Commands

Wallet connected

Address

Loading...

Balance

--

Dashboard

— —

sentinelhub-2 · v12

Demo mode — read-only preview on a public operator. Clone the repo and set MNEMONIC in .env to run your own.

Get the source →

Connecting to Sentinel network...