Infrastructure
Choose the VPS locations and protocols that fit the markets you serve. Your servers carry the VPN traffic; Flirexa coordinates them from the main panel.
What must exist before the first sale
The product is the complete customer journey
A server that produces configuration files is only one part of the business. The customer also needs a place to register, choose a plan, pay, connect a device, renew access, and ask for help.
Customer operations
Create plans, control access, assign device slots, deliver configurations, monitor usage, and handle support without keeping separate spreadsheets and scripts.
Commercial flow
Connect your payment provider, publish your prices, and let provider-confirmed payments activate access through the customer portal.
A realistic launch sequence
What one installation solves and what remains yours
Flirexa automates the product infrastructure it can safely automate. It does not pretend to create the external parts of your company.
Flirexa deploys
- the admin panel and separate customer portal
- the database, generated secrets, and managed services
- the first local WireGuard and AmneziaWG endpoints
- updates, verification, backups, and rollback tooling
- the workflows for customers, subscriptions, payments, and support
You provide
- a supported Ubuntu server and any additional VPN nodes
- your domain, business identity, prices, and legal terms
- accounts with the payment providers you choose to offer
- marketing, customer acquisition, and first-line business decisions
HostUbuntu Server 22.04 or 24.04 on x86-64 is the supported production baseline
InstallThe guided installer performs preflight checks, deploys dependencies, creates services, migrates the database, and verifies health
AccessThe admin panel manages the service; customers use a separate portal with their own authentication and device views
GrowthBusiness adds up to 10 managed servers; Enterprise removes the server and customer limits
OwnershipCustomer records, configurations, payment history, and VPN traffic stay on your infrastructure
From zero to a working service
A launch plan that does not hide the hard parts
1. Define one sellable offer
Choose the customer, price, subscription length, device allowance, and initial locations. A narrow first offer is easier to support and measure than ten plans built on assumptions.
2. Deploy the control server
Run the installer on a supported clean host. Confirm the admin panel, portal, database, local endpoints, health checks, update channel, and backup target before inviting customers.
3. Connect the business layer
Add the domain and HTTPS, configure outbound email, connect an eligible payment account, enter your terms and privacy text, then make one real low-value test purchase.
4. Test the customer path
Use a new browser and phone. Register, pay, create a device, download or scan the configuration, connect, renew, and open a support request. Test failure paths as seriously as success.
5. Add a second location only when needed
Business can bootstrap a compatible remote node from the panel. Verify routing, DNS, firewall behavior, capacity, and rollback before sending customers there.
6. Operate from evidence
Watch conversion, payment failures, support topics, active customers, server load, and churn. Improve the step that loses customers instead of adding features they have not requested.
Choosing a plan
Start with the operating boundary you actually need
| Situation | Practical starting point | Why |
|---|---|---|
| Testing the concept or serving a small group | FREE | Up to 80 customers, two local endpoints, portal, admin bot, and NOWPayments without a paid licence heartbeat |
| One server but more protocols | Starter | Adds Hysteria2, TUIC, VLESS-Reality, promo codes, and capacity for up to 500 customers |
| A commercial service with several locations | Business | Adds up to 10 managed servers, full provider suite, scheduled backups, customer balance, and per-device DNS protection |
| A fully branded or large operation | Enterprise | Adds full white-label controls, unlimited scale, RBAC, advanced DNS policy, corporate VPN, and standard customer apps |
Do not buy a higher plan merely to avoid planning the service. Upgrade when its operating features remove a real limit or manual cost.
Common questions
Before you launch
Does Flirexa sell VPN access to me?
No. Flirexa is the platform used to operate your service. You choose and pay for the servers, control the customer relationship, and decide the prices.
Can I begin without a paid licence?
Yes. FREE has no time limit and supports up to 80 customers on the installation host with WireGuard and AmneziaWG. You can activate a paid plan later without rebuilding the installation.
Will one command create the entire company?
No. The installer creates the technical operating foundation. Your domain, legal terms, payment accounts, support decisions, marketing, and customer acquisition remain business responsibilities.
Can I move an existing VPN service?
Yes. Enterprise includes a standard migration into Flirexa at no additional Flirexa migration charge. The source, data mapping, canary group, cutover, and rollback window are agreed before work begins.
Can the team build the customer-facing VPN website?
Yes. Under a separate agreement, our team can build a VPN sales website integrated with the Flirexa customer portal. Customers can register, choose a plan, pay, receive device access, renew, and contact support through one connected journey.