Lansweeper alternative

Anyone who uses Lansweeper has usually chosen it deliberately. Its discovery is thorough, it recognizes devices even without credentials, and it merges matches from different sources into a single record. There’s little to criticize there.

The question is what you want to do with the result.

Taken together, these points form a pattern: Lansweeper is built around discovery. What comes after that is missing, lives in the cloud, or needs a bigger plan.

With LOGINventory, that’s part of the same application and runs on your server: handout with signature, dashboards, reports and documents, queries that build on each other with sharing down to the individual query, network map, and integrations. You reach support through our landline number in Munich. License size grows in steps of 25 devices. And software asset management is an edition of the product, not an offering from a partner.

There’s one more question that’s easy to overlook when comparing. If you start with Lansweeper for free, you create a cloud Site, and the inventory is stored at AWS. A purely local installation still exists. It’s just not the route by which you get to Lansweeper, and it lacks part of what the platform can do.

With LOGINventory, the inventory is in your network. Always, and with the full feature set.

What Lansweeper calls “reports” is called a query at LOGINventory: an analysis whose result is a table. On the cloud platform, Lansweeper replaces them with dashboards, and custom reports are being retired there at the end of 2026. According to the documentation, what you can pass on are tables and dashboard tiles, as CSV, Excel, or image. The documentation doesn’t mention designed documents for filing or passing on.

LOGINventory has all of that, separated by purpose, and you design it yourself.

You adapt reports and documents or create new ones, and you drag the fields in with drag & drop. If you want, a task saves them regularly or sends them by email. Examples are on the IT documentation page.

Queries build on each other, and everyone sees their own slice

If you put one query under another, the upper one pre-filters it. Under the query for the Munich location, the software list shows only what’s installed in Munich, and the list of computers without a current update shows only the Munich ones. You attach the same structure, linked, under Berlin and Hamburg. What you add in Munich then appears there too.

Sharing is attached to the same nodes. You share queries, dashboards, and documents with users or groups from Active Directory, and everything below inherits the filter. For each node, you decide whether someone can only view, edit data, or create their own queries. The boundary can be a location, a cost center, or any other attribute in the inventory. If the person responsible creates their own analyses or a document below it, the same filter applies there. How to create and share structures is described in the documentation chapters Queries and Sharing.

On the Lansweeper Platform, saved views sit side by side, each with its own filter, and you share them with specific accounts or with everyone. The documentation doesn’t mention one view building on another. Lansweeper restricts who sees which devices there through fixed criteria: asset type, asset domain, IP location, location, or installation. In the local version, roles only regulate which functions someone may use. Anyone who may see assets sees all of them.

At Lansweeper, technical support runs through a ticket portal. How quickly the first response is supposed to arrive depends on the plan: for medium- and low-severity issues and for questions, Lansweeper’s support page gives a target of 48 support hours on the Starter plan and 24 on the Pro plan. A phone call is provided only on the Enterprise plan, for high-severity issues and by appointment.

Anyone using the free version doesn’t get technical support, but a knowledge base, training materials, and the community. The community’s forum is currently read-only, and the conversation continues on Reddit.

With us, you call. At +49 89 4488870 you reach us in Munich and speak to someone who answers your question in German or English. If that’s faster, we look at your screen with you through remote support. And if you write to us, you usually have a first reply within two hours. Support is included in LOGINventory360 and in maintenance, and during the trial phase it’s included anyway. All ways to reach us are on the Support page.

Lansweeper shows network diagrams on the cloud platform, and the product does a good job of mapping which device is connected to which switch port. For documenting a network, however, the diagrams are missing quite a bit.

According to the vendor, they have to be generated manually before you can view them. If you move objects to a different position, that arrangement is lost on the next reload. The documentation doesn’t mention custom shapes or labels. Diagrams are exported as images. And in the local version, the diagrams don’t exist at all.

The network map in LOGINventory is built from the MAC tables read from the switches and runs on your server. The arrangement is saved, with a separate map for each location or floor. You put a floor plan in the background, label devices with values from the inventory, and add your own shapes and connections. When it opens, the map is compared against the current state: new connections are marked green, changed ones dashed, and devices without a connection get an orange outline. As a PDF, it goes to anyone who needs it.