LinkDesk Features and Current Limits

WayaDesk / Software and buying

A feature list is useful only when its boundaries are clear. LinkDesk v0.5.0 includes billing, access, customer-service and recovery workflows, but some rules apply only to particular access methods. Check that the feature you need exists in the path you plan to deploy.

Implemented operating features

The application includes verified-payment workflows, local Hotspot vouchers, persistent subscribers, local PPPoE and a FreeRADIUS bridge. Operations tools include guided setup, router-health information, encrypted backups, restore utilities, staff permissions, a customer portal, support tickets and transactional SMS integration.

Limits that affect package design

Current data caps apply to supported local Hotspot vouchers. They should not be sold as enforced PPPoE or RADIUS data quotas. Strict global simultaneous-session enforcement for RADIUS PPPoE is also not included. Treat these as package-design constraints when agreeing what you will sell to customers.

• Match each required feature to the actual access method.
• Distinguish router observations from application records.
• Identify integrations that require an external account or separate service.

Licensing and delivery boundaries

The seller-prepared package supports product-key activation and signed licence-file import. Online keys require an HTTPS activation service. The purchased activated version can retain its local licence, but payments and messaging still depend on their own services. A software entitlement is not an internet-service subscription.

Evidence to ask for

Automated development checks do not establish real router behaviour, live M-Pesa payment handling, SMS delivery or FreeRADIUS daemon authentication on your equipment. Request a pilot report with the actual configuration and observed results. Keep unresolved limitations visible in the quote rather than hiding them behind a long feature checklist.