PoweredDeveloper/radix-vpn
1
0
Fork 0
Code Issues 5 Pull requests Projects 5 Releases Packages Wiki Activity Actions
RadixVPN source code
60 commits 5 branches 0 tags 2.5 MiB
  • Python 97.5%
  • Shell 1%
  • Dockerfile 1%
  • Mako 0.5%
Find a file
Exact
kkmlmust a6f689f7ef chore: add envelope(
2026-08-03 20:58:56 +03:00
.forgejo/issue_template chore: add chore issue template 2026-07-09 23:15:24 +03:00
backend chore: add envelope( 2026-08-03 20:58:56 +03:00
client/telegram-bot fix(backend): add payment management 2026-07-24 19:10:11 +03:00
docs fix(infrastructure): change docker compose protection rules; healthchecks; add redis to architecture 2026-07-13 03:57:58 +03:00
infrastructure/headserver feat(telegram): send subscription url to user 2026-07-23 00:57:43 +03:00
.gitignore fix(infrastructure): change docker compose protection rules; healthchecks; add redis to architecture 2026-07-13 03:57:58 +03:00
radix-vpn.code-workspace feat(telegram-bot): add redis; add logger; update todos; create workspace 2026-07-13 00:21:08 +00:00
README.md docs: create project architecture; update README 2026-07-07 13:32:04 +03:00

README.md

Radix VPN Documentation

Version: Draft v0.1
Project: Radix VPN

Radix VPN is a subscription-based VPN service built around a centralized management server (Head Server) and multiple distributed VPN Nodes. The architecture separates infrastructure management, business logic, and VPN services into independent components.

Main goals:

  • centralized VPN management
  • scalable node architecture
  • easy deployment of new servers
  • centralized monitoring
  • automatic configuration management
  • CI/CD with development and production environments
  • Telegram-first user experience

Documentation Map

Document Description
Architecture High-level design, component boundaries, service flows, SPOF, TrixUI replaceability
Backend FastAPI role, clients, TrixUI adapter, source-of-truth rules
Database ER diagrams, entities, sync strategy, identifier mapping
Authentication Telegram login, signed tokens, admin login, 2FA
Deployment Ansible, CI/CD pipeline, TrixUI provisioning research
Business Logic Subscriptions, balance, devices, referrals, freeze, notifications
Security HTTPS, firewall, SSH, Fail2Ban, secrets, database isolation
Operations Backup strategy, monitoring, disaster recovery

Quick Answers

Question Document
What runs on the Head Server today? Architecture — Current deployment model
User paid — what happens next? Architecture — Service flows
Who owns user records? Backend — Source of truth
What database tables exist? Database
How are backups handled? Operations — Backup strategy
What if TrixUI is replaced? Architecture — TrixUI replaceability

Links

Name Link
Telegram Bot Bot Link
Telegram Channel Channel Link
Website Later