Bedolaga Bot

The app/handlers/admin directory contains the logic for all administrative functions of the bot. Each module typically exposes a register_handlers function to integrate its logic into the main application. Key administrative areas include:

• Configuration & System: bot_configuration.py (settings), maintenance.py (maintenance mode), system_logs.py (log viewing), and updates.py (version info).
• User & Subscription Management: users.py, subscriptions.py, referrals.py, and pricing.py.
• Marketing & Promotions: campaigns.py, promocodes.py, promo_groups.py, and promo_offers.py.
• Communication & Support: messages.py (broadcasts), user_messages.py (user-to-admin messages), tickets.py (support tickets), and support_settings.py.
• Infrastructure: servers.py, remnawave.py, monitoring.py, and backup.py.
• Content Management: faq.py, privacy_policy.py, rules.py, and welcome_text.py.

The project is organized into a core app directory containing the main logic, divided into functional modules:

• app/bot.py: The main entry point for the Telegram bot.
• app/config.py: Configuration management via the Settings class.
• app/database/: Data persistence layer, including models, migrations, and CRUD operations.
• app/external/: Integrations with third-party services (e.g., CryptoBot, RemnaWave API, YooKassa).
• app/handlers/: Telegram message and callback handlers, organized by feature (e.g., admin, subscription, support).
• app/keyboards/: UI components (buttons/menus).
• app/localization/: Multi-language support.
• app/middlewares/: Telegram middleware logic.
• app/services/: Business logic services.
• app/states.py: Finite State Machine (FSM) state definitions for user flows.
• app/utils/: General utility functions.
• app/webapi/: Web API implementation.

Bedolaga provides a comprehensive suite of tools for running a VPN service via Telegram, categorized into four main areas:

Subscriptions and Tariffs

• Flexible plans (varying durations).
• Traffic management: Unlimited, fixed limits, or add-on packages.
• Device management: Limit the number of devices per subscription (1–20) or disable limits.
• Server selection: Automatic selection or manual configuration.
• Trial periods: Free or paid trials that can convert to full subscriptions.
• Smart cart: Saves selections if the user has insufficient balance.
• Auto-renewal: Triggered 3 days before expiration.
• Gift subscriptions and configurable landing pages.

Payments

• Support for 24+ payment providers simultaneously.
• Unified balance system: Users top up their balance via any method and then purchase using that balance.
• Automatic subscription purchase after successful top-up.
• Recurring payments (saved cards).
• Fiscalization via НалоGo (for self-employed users).
• Automatic payment status verification.
• Guest purchases via landing pages.

Marketing and Promotion

• Promo codes (for money, subscription days, or trials).
• Referral programs with fund withdrawals and partner systems.
• Segmented user mailing lists.
• Custom landing pages with analytics.
• Contests and daily games with prizes.
• Personal offers and discounts.
• Marketing campaigns with tracking.
• Mandatory multi-subscription to Telegram channels (with auto-cancellation if the user unsubscribes from the channel).

Administration

• In-Telegram management panel.
• User, subscription, and payment management.
• Topic notifications for purchases, renewals, and top-ups.
• Automatic database backups with restoration via the bot.
• Maintenance mode (auto-detects Remnawave panel unavailability).
• Traffic and anomaly monitoring.
• RBAC (Role-Based Access Control) with granular permissions.
• Detailed reporting and referral network visualization.
• Global user blacklist/blocking.

All communication follows a specific envelope structure. Commands sent by the client include a type, command, requestId, sentAt, and a payload. Results returned by the server use type: "command.result" and include an ok boolean, the original requestId, and either a payload (on success) or an error object (on failure).

Error Object Schema: When ok is false, the error object contains:

• code: Error identifier (e.g., VALIDATION_ERROR, NOT_FOUND, RATE_LIMITED, PAYLOAD_TOO_LARGE).
• message: Human-readable string.
• retryable: Boolean indicating if the client should attempt the command again.
• details: An object containing additional context.
• retryAfterMs: An integer (or null) specifying wait time before retrying.
• backpressure: Populated only for BACKPRESSURE error types.

// Client Command
{
  "type": "command",
  "command": "ticket.list",
  "requestId": "string",
  "sentAt": "2026-07-09T00:00:00Z",
  "payload": {}
}

// Successful Result
{
  "type": "command.result",
  "command": "ticket.list",
  "requestId": "string",
  "ok": true,
  "receivedAt": "2026-07-09T00:00:00Z",
  "payload": {}
}

// Failure Result
{
  "type": "command.result",
  "command": "ticket.list",
  "requestId": "string",
  "ok": false,
  "receivedAt": "2026-07-09T00:00:00Z",
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "string",
    "retryable": false,
    "resourceType": null,
    "resourceId": null,
    "details": {},
    "retryAfterMs": null,
    "backpressure": null
  }
}