Device footprint
How many networks, sites or field kits you expect to keep reachable.
lanhopper does not have public plans or published prices yet. We would rather be clear about that than invent a pricing table before the product and deployment model have settled.
These are discussion inputs, not plan boundaries. They help us understand what kind of packaging would be fair and practical.
How many networks, sites or field kits you expect to keep reachable.
Whether the primary need is occasional support, active operations, lab work or customer service.
What matters around rollout, ownership, account structure, review and support expectations.
How pricing should map to the value of solving remote access without heavyweight network setup.
Until the public model is ready, the useful next step is understanding the deployment. That keeps the conversation honest and avoids fake packages.
Tell us what networks you need to reach and why lanhopper is a better fit than VPN or manual tunnels.
Share the likely number of devices, sites, users and access modes involved.
If there is a fit, we can discuss what an early deployment path should look like.
A familiar pricing grid would look finished, but it would also imply decisions that have not been made yet.
Start with the network access problem. Pricing can follow only after the shape is real.