v2hub: an ecosystem for developers

Описание и применение

Разработчики получили возможность предлагать VPN‑услуги, используя v2hub как централизованную систему управления подписками, при этом пользователи сохраняют контроль над доступом провайдеров.

Задача

Developers needed a way to offer VPN services to users without managing subscriptions themselves, while keeping user tokens private and allowing users to control provider access.

Результат

Developers can now offer VPN services without building their own subscription infrastructure, while users maintain full control over provider access and can manage all subscriptions in one place.

Рабочий процесс

• 1. Developer creates a provider account and obtains a provider API token.
• 2. Developer requests access to a user via the API, triggering a pending request.
• 3. If the user exists, the provider receives a connection link to send to the user; if not, the server returns an HMAC‑signed invite link for user creation and connection.
• 4. User follows the link, approves or rejects the request.
• 5. Upon approval, the provider can create, update, or delete subscriptions for that user, but only those it created.
• 6. Users can revoke provider access, which hides the provider’s subscriptions but does not delete them; reconnection restores visibility.

Доказательства

A provider is a separate account type that can, with the user's consent, manage that user's subscriptions.

Источник

If a user approves or rejects the request. Only after approval can the provider do anything with subscriptions.

Источник

A single user can connect a limited number of providers — five by default.

Источник