Pricing in progress

Pricing is being shaped around real deployments.

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.

Published pricing status
No plans, tiers or prices are final
Not yet publicly packaged
Early deployments case by case
Plan names not defined
Feature bundles not promised
Public pricing coming later
What may matter

The right pricing model depends on how lanhopper is used.

These are discussion inputs, not plan boundaries. They help us understand what kind of packaging would be fair and practical.

DEV

Device footprint

How many networks, sites or field kits you expect to keep reachable.

USE

Access pattern

Whether the primary need is occasional support, active operations, lab work or customer service.

OPS

Operational needs

What matters around rollout, ownership, account structure, review and support expectations.

FIT

Commercial fit

How pricing should map to the value of solving remote access without heavyweight network setup.

What happens now

Early pricing conversations stay intentionally simple.

Until the public model is ready, the useful next step is understanding the deployment. That keeps the conversation honest and avoids fake packages.

No pricing promises here. This page is only a placeholder for the future pricing model. Any real commercial discussion should happen directly.

Describe the use case

Tell us what networks you need to reach and why lanhopper is a better fit than VPN or manual tunnels.

Sketch the deployment

Share the likely number of devices, sites, users and access modes involved.

Agree on next steps

If there is a fit, we can discuss what an early deployment path should look like.

What this is not

No artificial Free, Pro, Enterprise table.

A familiar pricing grid would look finished, but it would also imply decisions that have not been made yet.

We are avoiding pretend certainty.

  • No published monthly prices.
  • No fixed plan names or plan limits.
  • No promised feature packaging.
  • No implied SLA, support tier or enterprise bundle.

Curious whether lanhopper fits your deployment?

Start with the network access problem. Pricing can follow only after the shape is real.