Commercial VPN platform
- PLpgSQL 87.7%
- TypeScript 12.3%
| db/migrations | ||
| docs | ||
| src | ||
| .env.example | ||
| .gitignore | ||
| docker-compose.yml | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
VPN Platform
Commercial VPN sales, subscription, referral, billing and provisioning platform.
Architecture
This repository contains proprietary clean-room business logic. Remnawave is treated as an external control plane and is integrated only through its public/API contract. No Remnawave or third-party bot source code is copied into this repository.
Core domains
- Telegram client bot
- Customer & device management
- Plans, orders, payments and subscriptions
- Referral & promo engine
- Provisioning adapter
- Node health/capacity selection
- Support tickets and notifications
- Admin/RBAC/audit
- Analytics and unit economics
Environments
- development
- staging
- production
Production deployment, live payment credentials and irreversible infrastructure changes require a separate release approval.
Delivery stages
- VPN-01 Foundation & Repository Bootstrap
- VPN-02 Security Hardening
- VPN-03 Remnawave Integration
- VPN-04 Billing
- VPN-05 Telegram Client Bot
- VPN-06 Device Management
- VPN-07 Smart Provisioning
- VPN-08 Admin
- VPN-09 Support & Automation
- VPN-10 Full QA & Production Freeze
Security baseline
Secrets are never committed. Payment success is accepted only from verified provider callbacks/API reconciliation. Provisioning uses bounded API operations, not arbitrary shell access. Every privileged action is audited.