Knaq vs liftnet

Choosing the right elevator monitoring platform

While both platforms monitor vertical transportation equipment, they represent fundamentally different approaches to how that monitoring is done, where the data lives, and what you can do with it.

Cloud-native

  • Cloud-based platform accessible from any device.

  • Operations, maintenance, leadership, and field teams all share the same real-time data.

  • Alerts push via SMS, email, phone call, and mobile notifications.

  • Native iPhone and Android apps support field response and maintenance workflows.

OEM-agnostic

  • Works across any manufacturer, any equipment age, and any controller type.

  • Supports legacy relay logic and pre-PLC controllers from the 1970s onward.

  • Installs in 30 to 120 minutes per unit with no operational disruption.

  • Cellular connectivity by default minimizes IT coordination.

Predictive maintenance

  • Machine learning models analyze unit-level data for early signs of failure.

  • Flags at-risk units before they break down so teams can schedule proactive work.

  • Customers like Sound Transit turn $25,000 emergencies into $2,000 scheduled repairs.

  • Helps reduce unplanned downtime and eliminate emergency repair categories.

Full portfolio

  • Monitors elevators, escalators, moving walkways, HVAC systems, pumps, compressors, generators, baggage handling systems, train compressors, and other industrial equipment.

  • Unifies visibility across multiple equipment types in a single platform.

  • Works well for complex facilities and multi-site operations.

Open API

  • Customers own their data and get full API access.

  • Integrates with CMMS, BMS, and BI platforms.

  • All hardware, firmware, cloud, and software engineering is done in-house in New York.

  • Straightforward pricing with a one-time hardware fee, lifetime warranty, and software subscription.

On-premise

  • On-premise system limited to a central monitoring station inside the facility.

  • Access is restricted to whoever is physically at that station.

  • Remote status checks and mobile response workflows are not supported.

  • No mobile app for technicians or on-the-go teams.

OEM-dependent

  • Uses OEM-dependent hardware that often cannot interface with older equipment.

  • If the controller cannot integrate, no data is captured.

  • Deployment timelines increase because of integration and hardwired connectivity requirements.

  • Facility network access and IT coordination are typically required.

Reactive monitoring

  • Provides reactive monitoring only.

  • No predictive maintenance capability.

  • Teams still respond after breakdowns or alerts instead of before failures.

Conveyances only

  • Limited to conveyance monitoring only.

  • No pathway to expand into other critical equipment types.

Closed ecosystem

  • Data is siloed within the on-premise system with limited export options.

  • Development is outsourced with limited internal engineering knowledge.

  • Pricing is fragmented across hardware, software, and maintenance contracts.

Port Authority of New York and New Jersey
We have been looking for a solution to monitor elevator and escalators for a couple of years… Knaq gives us the ability to do that.

Port Authority of New York and New Jersey

John F Kennedy Airport
"The email and text messaging alerts are a huge help to our operations."

John F Kennedy Airport

Sound Transit
"When we start seeing an increased number of elevator re-levels, it can be an indicator that there is an issue with the valve . With Knaq, we get ahead of it and turn what would be an emergency repair with extended down time into a minor adjustment or repair on our timeline"

Sound Transit

Denver International Airport
"Knaq has helped us accomplish a 60-70% reduction in Work Orders generation."

Denver International Airport

See the difference for yourself

Most organizations start with a pilot on high-priority equipment to validate the platform before scaling. Knaq engineers will work with your team to scope the right assets, deploy hardware, and configure the dashboard to match your workflows.

step 1234/4

What type of environment are you monitoring?

What types of equipment are you looking to cover?

How large is the initial deployment?

Based on your selections, most teams in similar environments start with a focused initial deployment and expand in phases as operational needs become clearer.

Pricing varies based on equipment types, deployment scope, site complexity, and installation logistics, which is why we typically recommend a brief conversation with an engineer to validate the right approach for your environment.

Talk through this with a Knaq engineer
Full Name*
Email*
Phone
Thank you! Your submission has been received!
A Knaq engineer will reach out shortly.
Oops! Something went wrong while submitting the form.
}) } } } } }) } } } } } } } } } } }) } } }) } } }) }) }) }) } }) } }