Service providers
Issue and renew access via bot and panel under one policy; aim to reduce routine “access dropped” support load.
Structured network access
Ship a VPN ecosystem with client, panel, and bot out of the box
Padawan combines an Android OpenVPN-based client, an admin panel, a Telegram bot, and cloud-side entitlement sync — one place to track who has access, for how long, and under which role. White-label UI, phased delivery, and launch advisory (scope defined in contract).
- Centralized validity periods and device roles
- Consistent branding across client and admin surfaces
- Less manual profile and spreadsheet work in typical setups
Single ecosystem
White-label UI
OpenVPN + cloud registry
Launch support
Who usually benefits from this profile
Teams that provision or operate remote access and see growing device counts and manual toil. Any business case and ROI should be modeled for your own operating model.
Integrators and agencies
A coherent deliverable for end clients: unified brand, clear onboarding, deployment documentation.
IT and admins
Centralized device roles, expiry awareness, fewer one-off profile handoffs to each new user.
What you receive as a product
Not unrelated repos, but an aligned path: end-user client, management UI, and automation around the access lifecycle.
Android client
OpenVPN under the hood: profiles, device and expiry checks, role-based UI — without unnecessary filesystem exposure on the handset.
Admin panel
Devices, stats, OpenVPN nodes, notifications, and administration aligned visually with your brand and this site.
Telegram and cloud
Bot and sync (e.g. via cloud storage): one source of truth for client and panel — authorized devices and dates.
Technical scope
Components cover the path from an admin decision to a stable VPN session on device.
OpenVPN servers
Operate nodes from the panel, client profiles, and infrastructure checks without console hopping.
Device roles
Full access, router mode, or handset-first — scales without breaking the architecture.
Notifications
FCM for important events: access granted, expiry reminders, service notices.
Industry context and references
We do not publish customer names without written permission. Below are typical segments; logo slots are reserved for partners and clients after placement is agreed.
- Carriers & service providers
- Systems integrators & MSPs
- Corporate IT
- Distributed-access teams
Partner / client
Partner / client
Partner / client
Partner / client
Legal notice: Site content is informational; deliverables, licensing, and liability are defined in your agreement and/or individual commercial proposal. “OpenVPN” may be a trademark of OpenVPN Inc.; reference does not imply endorsement.
How it works for end users
Four steps from an admin action to an encrypted tunnel.
Access decision
Admin registers the device in panel or bot: validity, customer, role.
Sync
Record lands in cloud storage; client and panel read the current registry.
On-device check
App validates identifier and dates; UI adapts to role.
VPN session
Connect to OpenVPN profile; traffic follows your policy.
Why an ecosystem instead of “just OpenVPN”
Typical manual flow vs. Padawan. Outcomes depend on your infra and policies.
Ad hoc
- Chats, spreadsheets, manual .ovpn distribution
- Harder device inventory and expiry visibility
- Inconsistent UX between panel and client
- Higher support risk as you scale headcount
Padawan
- One loop: bot, panel, client, cloud
- Validity and roles in one registry
- Unified visual brand, white-label
- Streamlined onboarding in a standard deployment
User onboarding
A clear path for subscribers. Profile details and panel URL are set during your implementation.
1
Get access
Admin grants authorization via bot or panel. Without a system record, the client check will not pass.
2
Install the app
Install your APK or build from a trusted channel. Notifications optional for service pushes.
3
OpenVPN profile
Import .ovpn or pick a server from the in-app list per your runbook.
4
First launch
Device and cloud-side expiry check; screens match role (full / router / phone).
For administrators: protect API tokens and the panel, back up authorization data, and audit device lists on a schedule.
Plans and delivery formats
Indicative tiers for budgeting. Final estimates follow a short discovery call: node count, branding, SLA, training. Figures below are in RUB; international quotes available on request.
Numbers are planning ranges; we lock scope in a written proposal.
Start
Pilot or small footprint
from 79 000 ₽
one-time package license
- Entry white-label (logo, colors)
- Deployment consultation
- Installation documentation
Popular
Professional
Production with bot and panel
from 249 000 ₽
implementation + environment setup
- Full stack: client, panel, sync
- Telegram bot tuned to your workflow
- 30 days launch support
- One training cycle for your team
Enterprise
Integrations, on-prem, SLA
Custom
contract and roadmap
- Custom integrations and policies
- Priority support options
- Expanded brand and UI
- Source and on-prem options
Amounts are indicative budget signals only and do not constitute a binding public offer in any jurisdiction. Final pricing, timelines, and deliverables are fixed in a commercial proposal and/or contract after technical scoping. Taxes (including VAT or equivalents) apply according to applicable law and your entity.
Pre-sales questions
Typical topics before a deployment.
Is this cloud SaaS or self-hosted?
You usually host the panel and nodes; sync may use cloud storage under your policy. Enterprise covers on-prem and integration details.
Can we rebrand fully?
Yes. White-label covers naming, logos, and palette in client and panel. Depth depends on the selected tier.
What do you need from us to start?
Servers for panel and OpenVPN, a domain if required, cloud accounts if you use a Drive-compatible flow, and a responsible admin on your side.
How long is a typical rollout?
Pilots can be days with ready infra. Production with bot and training often lands around 2–4 weeks depending on queue and approvals.
Is there support after go-live?
Professional includes a launch support window. After that, a separate maintenance agreement or time-and-materials as agreed.
Discuss your scenario
Share scale: user count, VPN nodes, bot and cloud sync needs. We reply with a suggested work package and timeline band.
Ready to tighten how access is run?
We align the ecosystem to your brand and processes — from discovery to user go-live.