Proqio alternative: how to choose a geotechnical platform

In brief

• Do not compare the number of icons on the website. First define what data must enter the system and what decision it must trigger.
• Proqio publicly describes centralisation of data from geotechnical, structural and environmental sensors; the broader Encardio Rite offer also includes geospatial services.
• Inclify focuses on automatic HTTP/JSON data, alarms with a reaction history, data quality, chain inclinometers and dynamic signals.
• If you need manual field readings, LiDAR, InSAR or a ready-made compliance report generator, do not assume support in either product. Demand a demonstration of the full process.
• The safest decision is a parallel pilot with the same data source, the same thresholds and the same acceptance test list.

The comparison was verified on 30 August 2026 based on public manufacturer pages. We do not assess deployment quality, support or functions not visible in the documentation. If the supplier shows a function in the offer that is not on the website, record it in the pilot protocol and verify it on your own data.

What Proqio is, and what Inclify is

A geotechnical monitoring platform is software that collects data from instruments, preserves context, performs calculations, shows changes and triggers the agreed response. The definition is deliberately broader than a dashboard. A nice chart without quality control, an alarm and a decision trail does not close the monitoring process.

The official Proqio description presents the product as a cloud platform that centralises current data from geotechnical, structural and environmental sensors. Encardio Rite lists piezometers, strain gauges, accelerometers, fibre optic systems and its own data loggers, among others. The website describes configurable dashboards, thresholds, notifications, trend analysis, reports and multi-project management. In the broader offer, the manufacturer also describes scanning, InSAR, GNSS and inspections. This does not prove that Proqio itself ingests and combines every one of these data classes; that scope needs a demo and a statement in the offer.

Inclify is a Polish online platform for automatic structural and geotechnical monitoring. It accepts data from loggers or concentrators through an explicit HTTP/JSON contract, stores time in UTC, recalculates values using project equations and shows them on dashboards. It has threshold alarms and missing-data alarms, state history, operator acknowledgement, temporary mute, e-mail, SMS and in-app notifications. It also has ready-made workflows for vertical chain inclinometers and vibration events: time history, FFT, 21 third-octave bands and RMS/MAX envelopes.

These are not two identical products with different logos. Proqio belongs to the broader Encardio Rite instrumentation and services ecosystem; this relationship may be an advantage or a limitation depending on the contract, data delivery format and responsibility for integration. Inclify has a narrower core: automatic sensors, data quality, alarm response and calculations for specific measurement classes. The question is therefore: which scope is essential in this contract?

First the decision flow, then the feature list

Start with one sheet of paper. Write down the event you want to avoid, the evidence that should confirm it and the person authorised to react. For a diaphragm wall, this may be a growing displacement profile, no new readings from a key section or an exceedance in strut force. For a slope: a combination of pore pressure, inclination and rainfall. For a building next to the works: vibration and a lasting change in tilt. A practical context for source selection is described in the guide to deep excavation geotechnical monitoring.

Then follow the data path:

1. the device creates a measurement with an unambiguous time stamp;
2. transmission delivers it to the platform;
3. the platform validates the frame and recalculates the value;
4. the chart shows the trend without hiding gaps;
5. the rule evaluates the threshold or missing data;
6. the right person receives the message;
7. the operator acknowledges the event and starts the procedure;
8. after a week, the data, settings and response can be reproduced.

If the request for proposal does not define these eight steps, suppliers will show incomparable presentations. One will impress with a map, another with an app, a third with the number of sensors. None will answer whether the contract manager will know what to do on Monday at 7:40.

Proqio or Inclify: decision matrix

The table below is not a ranking. The Proqio column is based on the official Encardio Rite and Proqio descriptions available on 30 August 2026. The Inclify column is based on the currently operating product. "Not publicly confirmed" does not mean "absent"; it only means that before purchase you must obtain written proof and show it in the pilot.

How to read the matrix result

The most important row is not about technology. If the primary contract deliverable is an automatic PDF report in an agreed layout, Inclify does not meet that requirement today without an additional process. If the core is a manual survey campaign with offline work, you also need a different process. If, however, the core is automatic sensors, engineering charts, stream reliability and documented alarm response, a focused platform can cover the required scope without extra modules.

When Proqio is the more reasonable choice

Shortlist Proqio if the project needs a wide data landscape and a single supplier for hardware and services. Do not assume, however, that InSAR, geodetic measurements, scanning, environmental data and point sensors will automatically end up in one Proqio environment. For each class, ask for a demo of import, visualisation, alarming and data delivery, and record integration responsibility in the offer.

The second case is compliance reports and automatic reporting as a contractual requirement. Proqio publicly declares these functions. A slide is not enough. Ask for the exact report you will attach to the monthly record. Check units, date range, threshold version, gap marking and data sources. "It has reports" is a marketing feature; "it creates our artefact without manual correction" is a test outcome.

The third case is choosing one hardware and services ecosystem. If you want one supplier to provide sensors, loggers, installation, transmission, the platform and international support, the Encardio Rite offer groups these elements in one contractual relationship. You will assess the impact of that relationship only after reviewing responsibilities, interfaces, support conditions and data delivery. The contract should specify the format of measurements, configuration and history after the cooperation ends.

When Inclify is a better fit

Inclify is worth checking when you already have automatic loggers or are building a system that must work without manual data transfer. The integration contract is explicit: the device or concentrator sends HTTP/JSON frames with UTC time, channel ID and raw values. The platform validates the data, applies project equations and stores the result. History from the old system can be sent the same way with the original time stamps. There is no measurement file import. The technical conditions for such a pilot are described in the guide to connecting existing loggers.

The second case is a team for which alarm is an operational process. Each channel can have its own warning and alarm level with hysteresis. Missing new measurements can have a separate rule. When the state changes, the user receives a notification according to their preferences, acknowledges ownership of the event and the system records the person and time. The alarm can be muted until a specific date. There is no automatic escalation chain or rate-of-change alarm; the organisational procedure still belongs to the team.

The third case is monitoring that needs ready-made sector views. For a vertical chain inclinometer, the platform calculates the profile from a fixed base upwards based on segment lengths, on the A, B and resultant axes. The configuration has versions, so a geometry change does not have to overwrite the meaning of earlier periods. For vibration, the time history, FFT and RMS/MAX values in 21 third-octave bands are available. This does not create automatic standard compliance or fault diagnosis. A specialist interprets the result.

Finally: Inclify has a data quality report. It determines the actual cadence as the median interval, counts expected and received samples, freshness, gaps and continuity. This means that "the system works" does not only mean that the page opens. More on stream acceptance can be found in the guide to seven measurement data SLA metrics.

Illustrative scenario: a wall, vibration and one request for proposal

Assume the contract covers a deep excavation wall, two vertical chain inclinometers, strut force sensors, piezometers and vibration recording on the neighbouring building. The investor wants threshold alarms, missing-data control and a monthly summary. The example is illustrative; it does not describe a real deployment.

If the monthly summary must be an automatic PDF in an approved template, and laser scans plus field observations must also feed into one dashboard, Proqio may receive a high score only after a demo of those operations and confirmation in the offer. Inclify has project documents, dashboards, CSV and chart images, but no generator for that PDF or native intake of scans as a measurement series.

If the daily decision is: "has the wall profile changed, are all sources fresh and who took over the alarm?", Inclify has a ready set of elements. The pilot should include one controlled gap, one exceedance, a reference change and a full dynamic event. You then compare the result and the process, not the sales presentation.

The same project may ultimately use more than one tool. A higher-level platform can centralise contract data, while a specialised process performs analysis of a specific signal class. A hybrid architecture only makes sense when the contract clearly identifies the source of truth, the synchronisation direction and the place where thresholds are configured. Two independent alarms with different values are worse than one more modest system.

How to run a low-risk pilot

A parallel pilot does not require shutting down the existing system. Its purpose is to resolve specific hypotheses.

1. Choose one section and, illustratively, 10-30 channels. Select the number according to the project; the sample must be representative and possible to verify manually.
2. Write down the expected units, references and formulas. This will be the test benchmark, not the result of one of the platforms.
3. Send the same data to both systems. If this cannot be done without manual conversion, count its cost as part of the total cost of ownership.
4. Set identical thresholds. Do not compare alarm quality with different rules.
5. Introduce controlled events. Delayed sample, missing data, exceedance, configuration change and range export.
6. Measure the outcome. Time to detection, number of messages, calculation consistency, ability to reproduce the configuration and operator time.
7. Ask people outside measurement. The project manager should be able to identify the state, basis and owner of the action without product training.
8. Release a data sample. Before the pilot ends, download the measurements and results, then check whether another team can interpret them.

Pass criteria must be defined before the demo. Otherwise the result depends on how the presentation is conducted, not on the test. Use the monitoring platform selection checklist to set acceptance conditions as well.

How this looks in Inclify

The Inclify team starts with a check of the existing data source and one example frame. If the logger or concentrator can send HTTP/JSON, the same hardware can stay in the field. The platform stores time in UTC, applies project equations, builds dashboards and configures alarms for channels. For a vertical chain, it creates the profile and the trend by depth; for a complete dynamic event, it shows the time history, FFT and 21 third-octave bands.

In the pilot, it is worth checking not only a "good day" but also missing data, wrong time, exceedance and a threshold change. The audit log shows values before and after the change, the alarm history preserves transitions and acknowledgement, and the quality report assesses completeness and freshness. Raw exchanges with the device are stored for the configured period, by default seven days; this is not an indefinite archive.

Inclify does not replace InSAR, scanning, manual series entry or an automatic PDF report generator. If these are hard requirements, say so before the pilot. If the goal is an automatic flow from logger to documented decision, it can be verified on one asset without replacing sensors.

Limitations of the comparison

Public pages do not show all licence variants, integrations, limits or services available in a specific region. The broader Encardio Rite offer is not automatic proof of Proqio functions, and the absence of a function on the website does not prove that it is not available. Every requirement concerning InSAR, LiDAR, scans, manual observations, reports and alarms must be confirmed in the current demo, offer and acceptance protocol.

The comparison does not assess support quality, cost or deployment outcome. It also does not replace the monitoring design and the engineer's assessment. Inclify has documented limits: it does not accept manual series from files, does not generate a contractual PDF and does not replace remote sensing tools.

Red flags in both offers

• "We support every sensor" without showing a trial frame and the output in engineering units.
• "Real time" without defining cadence, delay and missing-data alarm.
• "AI predicts failure" without methodology, validation set and engineering oversight.
• "Full audit" without testing a change in threshold, reference and formula.
• "Open platform" without a data delivery format after the contract ends.
• "Standards compliance" without stating the scope, standard version and responsibility for interpretation.
• "Automatic reports" without generating the actually required artefact.

Do not ask the supplier whether the system is flexible. Ask them to perform five operations on your sample. Flexibility that cannot be accepted in a test is a promise.

Sources and further reading

• Encardio Rite: Proqio Integration - official scope of data centralisation, dashboards, alarms, reports and sensors; accessed 30.08.2026.
• Encardio Rite: geotechnical data management - official context of the instrumentation and data management offer.
• ISO 18674-1:2015 - general principles of geotechnical monitoring.
• ISO 18674-3:2017 - measurement of displacements along a line by means of inclinometers.
• USACE EM 1110-2-1908 - selection, operation and interpretation of instrumentation.
• How to choose a structural monitoring platform: checklist - broader set of purchasing questions.

What next

Do you have a sample data frame and a list of requirements? Book a short compatibility review. You will receive a written indication of which elements Inclify covers today, which require integration and which should stay out of scope.