
ProjectsVision VPN
Vision VPN
A Remnawave-based VPN platform that brings together a Telegram subscription sales system, a dedicated subscription page, monitoring, and automated backups.
- Role
- Brand identity · Platform architecture · DevOps
- Stack
- Remnawave · Docker · Portainer · Telegram Bot · Grafana · PostgreSQL · Git · Figma
- Period
- 2025
- Outcome
- Managed VPN platform
Overview
VPN infrastructure, managed from one place.
Independent project. Vision VPN is a subscription VPN platform built around Remnawave. It combines user and Xray node management, subscription sales through a Telegram bot, and a subscription page on a separate domain. The system runs in Docker Swarm with server-load monitoring and automatic database backups.
The problem
Running a VPN service involves two connected areas: a clear way for users to purchase and manage access, and a reliable operational layer for users, nodes, deployments, monitoring, and data recovery. When these concerns are spread across unrelated tools, routine maintenance becomes harder and subscription state is more difficult to keep consistent.
Vision VPN separates the user-facing sales and subscription interfaces from infrastructure management while connecting them through Remnawave.
Project scope
The implementation brings the main product and operational concerns into one system:
- Remnawave manages users and Xray nodes.
- A dedicated sales service works through a Telegram bot.
- A subscription page on a separate domain communicates with Remnawave.
- The complete stack is deployed in Docker Swarm.
- Server load is monitored, and the Remnawave and subscription-sales databases are backed up automatically.
Subscription experience
The Telegram bot is the user-facing channel for subscription sales. It gives the sales service a familiar interface without exposing infrastructure controls to customers.
After access is issued, a dedicated subscription page provides subscription information from its own domain. The page communicates with Remnawave, keeping the customer-facing view connected to the panel that manages access.
Service architecture
Remnawave acts as the control plane for VPN access: administrators use it to manage users and the Xray nodes that provide connectivity. The subscription-sales service and the separate subscription page remain distinct from the control panel, so each part has a focused responsibility.
All components run in Docker Swarm. This provides a shared deployment model for the panel, sales service, subscription page, monitoring, and supporting services across the infrastructure.
Monitoring and backups
The monitoring layer tracks server load so infrastructure health is visible during operation. Automatic backups cover both the Remnawave database and the subscription-sales service database, protecting the two stores that are essential to restoring user access and sales data.
Monitoring and backups are treated as parts of the product rather than follow-up maintenance tasks. Backup recovery procedures still need regular verification as the system changes.
Result
Vision VPN brings subscription sales, access management, Xray node operations, deployment, monitoring, and database backups into one operational platform. The result is a system with clear boundaries between customer-facing services and infrastructure control, while Remnawave keeps subscription access connected to the underlying VPN network.
Lessons to carry forward
A subscription service is only as dependable as its operational foundation. Clear service boundaries, observable infrastructure, and recoverable data are essential parts of the customer experience.
Visual showcase
Results
- 10+
- Server locations
- 99.9%
- Service uptime
- 24/7
- Infrastructure monitoring
- 1 Gbps
- Peak download speed
Let's talk
Let's build something.
Have a project in mind or just want to say hello? I'm always up for a good conversation.
Let's talk