Will WayaDesk work with your network? Use this checklist to prepare a compatibility enquiry before buying LinkDesk software.
Review your MikroTik equipment, access method, host and payment setup. If any item is uncertain, ask us to review the requirements before choosing a licence.
Ask about my setupRead system requirements →
1. Identify your MikroTik gateway
Record the router model, RouterOS version and number of routers you want to manage. Confirm how the billing host will reach the MikroTik equipment. A list of models alone does not establish that a particular network configuration is ready.
If you use TP-Link, Tenda or other access points, distinguish them from the gateway enforcing paid access. Read access points and MikroTik billing before buying equipment.
2. Choose your customer access method
- Hotspot: review packages, vouchers, login-page reachability and supported local data-cap rules.
- Local PPPoE: review subscriber records, payment entitlement, renewal and expiry behaviour.
- FreeRADIUS: plan a separate Linux FreeRADIUS service and acceptance tests for the integration.
Review the current feature limits. Strict global concurrent-session enforcement for RADIUS PPPoE is not included in the currently documented scope.
3. Prepare an available Windows or Linux host
Your deployment needs an appropriate host that stays available for the workflows you rely on. The published deployment guidance describes Windows or Linux with Python 3.11+. Check the current installer instructions, network access, storage, backup plan and restart procedure before rollout.
Public customer checkout needs an appropriate HTTPS setup. Activating a licence locally does not make online payments or SMS work without their required connections.
4. Separate licence payment from subscriber payments
Buying LinkDesk through WayaDesk checkout is the software purchase. Collecting internet payments from your subscribers requires your own configured M-Pesa merchant integration.
Tell us whether you already have a merchant setup. Read the M-Pesa merchant preparation guide. An SMS provider account is also needed if you want notifications.
Send a useful compatibility enquiry
- Router model and RouterOS version
- Number of routers and sites
- Hotspot, PPPoE or FreeRADIUS workflow
- Available Windows or Linux host
- Whether your M-Pesa merchant setup is ready
- Existing customer migration and any required SMS features
General equipment and workflow details are enough to start. Keep router passwords, payment API secrets and private customer records out of your initial enquiry.
5. Confirm your licence and pilot plan
Choose the managed-router allowance for one installation. Router allowance is not a tested subscriber-count or bandwidth guarantee. Review current licence prices and request a larger allowance if your requirements exceed the listed packages.
Before migrating paying customers, test payment, access, renewal, expiry, restart and backup restoration on your intended deployment. Include SMS and FreeRADIUS tests where applicable.
Your next step
Requirements understood? Compare licence packages and agree the pilot. Need a walkthrough? Open the interactive demo now. Need help installing? Ask for a separate setup quotation.
Compare software licencesOpen demo · Discuss setup assistance