Frequently Asked Questions


In addition to the demo videos on this web site you can try the following options:

  • Demo version of CVO Portal right here: login – demo; password – demo.
  • Some mobile apps on Google Play and App Store.
  • You can also purchase the demo kits with Leantegra hardware and software.

Yes, please contact us by e-mail or chat (web site) and we would be glad to analyze your requirements.

Yes, this is possible. For this purpose we created the demo kits, which help to reduce the initial costs and risks. We can advise the most optimal configuration for your pilot project.

Yes, we have an in-house engineering team with software engineers, hardware engineers, QA, DevOps, project managers etc.  


Yes, we support both on-premise and cloud-based installations for CVO Portal and the rest of server software. For the cloud our choice is Amazon AWS, but we’re not limited to Amazon only. 

Yes, this is definitely possible. Please contact our sales team for more information.

Leantegra servers include the web portal (CVO Portal), the data warehouse (DWH) for analytics and the edge server (PowerGate). All of them can be hosted on Amazon AWS, but a more optimal configuration includes the edge server on Intel NUC box and the web portal together with DWH on a dedicated server instance.

  • Without data warehouse and analytics – Intel Core i7, 16 Gb RAM, 256 Gb SSD.
  • With data warehouse and analytics – Intel Xeon E5+, 64-96 Gb RAM, 512 Gb SSD. 

No, PowerGate server installation is needed for RTLS only. If your project is about indoor navigation or/and proximity marketing, then the edge servers are not needed.

Installing the Intel NUC box for hosting PowerGate server is optional. The whole setup can be installed on Amazon AWS. But please consider the issue of RTLS performance and latencies. The local server box with PowerGate will definitely improve both performance and user experience.


Please consider that we can provide some discounts or even free-of-charge hardware or software to our selected partners. But this is possible for the later-stage engagements only – when we will see enough traction and orders. Early-stage customers or partners need to purchase the demo kits. 

Yes, we support both BLE 5.0 and BLE 4.x in hardware and software. The upcoming release of our new RTLS anchor will support BLE 5.1 standard for AoA-based localization (planned for Q1 2020).

Yes, you can. No integrations or coding activities are needed to make them work with CVO Portal and the mobile SDK.

Yes, this is possible for both indoor navigation and proximity marketing. RTLS and asset tracking scenarios are different, we need to analyze your requirements before any final answers.

The default average lifetime is 12 months, but it can vary depending upon several parameters: blink rate, usage of accelerometer, TX power etc.

Wireless charging is used for WiBeat UWB with recharging time varying from 24 hours to 1 month. More specific values depend upon the configured blink rate and the accelerometer-assisted UWB transmissions (less motion = less recharging).

The default average is one beacon every 7-15 meters. But our team can provide better estimations for your project requirements.

Please provide us the floor plans and we will provide the detailed estimations. Our basic formula is about 200 sq.meters per 4 x BLE RTLS anchors and 400 sq.meters per 4 x UWB RTLS anchors.

Yes, WiRange devices can be powered using PoE or regular DC supply (regular power socket). Data connectivity can be organized through the local Wi-Fi network.

Indoor Navigation and Proximity Marketing

Yes, the mobile SDK works without internet for indoor positioning and indoor navigation. For example: if a smartphone loses an internet connection, then it will be localized and routed correctly.

Yes, the mobile SDK does some local caching in the background – both rules and some content. So the push notifications will keep coming even with the connectivity interruptions. 

Yes, this is supported. No extra configurations or customizations are needed.

Unfortunately Google stopped supporting the Google Nearby project in 2017-2018 for both iOS and Android platforms. It means that a mobile app is needed for proximity marketing. Still, we support both Eddystone and iBeacon protocols on all levels: BLE beacons, SDK, apps, CVO Portal.

White-labeling of Leantegra Pilot App or Sandbox App is a good option here. Our reference apps can be easily branded for your pilot projects. Normally this is a matter of several days.


Both API and visualizations supply the coordinates in (LAT, LON) format. It is more suitable and more compatible with 3rd-party GIS, mapping and BI tools.

Please check “RTLS Quality Checklist” picture on the following web page. It shows the common LOS-NLOS scenarios, which are supported by Leantegra RTLS.

Please consider that UWB has country-specific regulations and limitations. Some countries, such as Ukraine, prohibit using UWB RTLS for the commercial installations. BLE RTLS has a worldwide allowance, because it operates on the standard 2.4 GHz Bluetooth. Some other advantages of BLE RTLS:

  • Longer battery life without replacing or recharging – BLE beacons might live for years on a single charge.
  • Supported by smartphones and mobile apps – for administration or project-specific features.
  • ​Price for RTLS tags – by default UWB tags are more expensive than BLE tags/beacons: 2-3 times more expensive.

In the lab environment and pure LOS scenarios – yes. In the real-life projects and installations – very unlikely. More probable location accuracy for UWB RTLS is 30-50 cm on an average basis.

3D RTLS implementation is still in progress – using the barometer sensors for WiBeat devices. The release is expected somewhere in Q1 2020. For now we support multi-floor 2D RTLS, where different floors can simulate different “levels” of 3D RTLS.

We use cookies to personalize your experience. By using our website you agree to our Privacy Policy