The whole PWA stack - on your own server
The panel, storefronts, traffic distribution, filtering and stats install on your VPS. No third-party service sits between you and your traffic - domains, database and funnels are yours alone.
What gets installed on your server
One command brings everything up: the panel, traffic distribution, filtering, storefronts and analytics.
Panel and core
Web interface, API access and real-time notifications.
Traffic handling
Split distribution, filtering, white pages and serving the storefronts themselves.
Data and analytics
Visits, installs and conversions - the whole history stays with you, reachable without an intermediary.
Operations
HTTPS certificates and platform updates without manual work.
What that gives you in practice
The difference from renting is who owns the data, the domains and the traffic bill.
Domains, offers, sub IDs and stats live in your database - no intermediary sees them.
Cloudflare, the registrar and the filtering service run on your keys, domains stay in your account.
A plan caps seats and domains, not visits: there is no per-install fee.
What the server needs to be
A clean VPS on Ubuntu or Debian with ports 80 and 443 free. Starting points per plan are below.
| Plan | vCPU | RAM | Disk |
|---|---|---|---|
| Free | 2 | 4 GB | 20 GB |
| Solo | 4 | 8 GB | 40 GB |
| Team | 6 | 16 GB | 80 GB |
| Agency | 8 | 32 GB | 160 GB |
Traffic is unlimited; peak load sets the real need. The full checklist is in the documentation
What you'll have to handle yourself
Your own server means control, but also responsibility. What stays on you:
Pay for the VPS and watch its resources - disk and load grow with traffic.
Set up Cloudflare, registrar and filtering service accounts - they are not part of the licence.
Go through the install: about 15 minutes by the guide, on a clean server with root.
Bring the stack up on your server
Two weeks free, no card required. Installation is one command on a clean VPS.