AshVPN is being prepared around device-tier plans, Demand-led location planning, and a future account dashboard for setup, billing, support, and device-slot control.
The staging site explains the planned customer journey without claiming live automation before the backend is connected.
Choose a plan by device allowance: 1, 2, 5, or 10 device slots. The customer offer stays simple instead of charging separately by location.
The current staging model collects preferred VPN locations during testing, with final availability decided later.
Before payment goes live, checkout shows the selected plan, device allowance, billing term, discount, total, and VAT/tax note.
The full platform is intended to issue separate setup material for each active device slot, rather than sharing one setup across every device.
The planned customer dashboard should provide VPN config downloads and QR codes after successful account and payment setup.
The account area is being planned for billing view, setup guidance, support contact, and basic device-slot management.
Later, customers should be able to replace a device. The old VPN config should be invalidated before a new config is issued for the replacement device.
When subscriptions, trials, or paid access expire, the backend should enforce access rules and prevent expired device configs from remaining active.
Live payments, automatic account creation, VPN issuing, QR generation, revoke/replace tools, and expiry enforcement are planned but not connected in this staging build yet.