In-house hardware, firmware, and software

Our own technology, from sensor to your systems.

We connect instruments, log their measurements, and deliver data your operation can use. One common foundation for water, geotechnical, and industrial-asset monitoring, without relying on any single network or platform.

4–20 mA / Pulse RS-485 / Modbus SDI-12 / BLE Vibrating wire 4G LTE / Ethernet LoRa / Satellite

Interfaces and networks supported by the VigiaBOX family.

01 / A common technology foundation

Connect instruments.
Without siloing their data.

A piezometer, a water sonde, and a temperature node speak different languages. We keep acquisition, communications, and data delivery separate, so adding a new source does not mean redoing the integration.

Ilustración de la arquitectura de Wolke: instrumentos en terreno, VigiaBOX, redes celular, LoRaWAN y satelital, Connection Broker y destinos
1

Instruments

2

VigiaBOX

3

Local HMI

4

Site network

5

RokkaBOX

6

Connection Broker

7

Your operation

  1. Instruments

    Piezometers, wells, and heat-traced lines, ours or third-party.

  2. VigiaBOX

    Reads every instrument, logs on site, and resends after an outage.

  3. Local HMI

    Runs the zone from the enclosure, even if the link drops.

  4. Site network

    4G, LoRaWAN, or satellite, depending on coverage and power.

  5. RokkaBOX

    VigiaBOX in a geotechnical configuration, for vibrating wire.

  6. Connection Broker

    Identifies the source, keeps the original, and delivers.

  7. Your operation

    GeoVigía, SCADA, or your cloud, over REST API, MQTT, or Azure Service Bus.

You don't need a Wolke device at every source: the Broker also takes in sources that already transmit.

02 / Multi-signal acquisition

Many instruments.
One consistent way to connect their data.

VigiaBOX, our family of data acquisition, logging, and telemetry devices, reads the signals on site and prepares them for a common data architecture. Explore VigiaBOX

VigiaBOX / Wolke technology Equipo VigiaBOX de adquisición y telemetría desarrollado por Wolke
Acquisition · Local logging · Communications
Process signals

4–20 mA, pulse, and status inputs.

Analog readings, counts, and discrete signals: flow, level, and equipment status.

Digital instruments

Modbus RS-485 and SDI-12.

Third-party sondes, meters, and stations, with reading and interpretation configured per instrument.

Distributed sensors

BLE links at the asset.

ThermoGuard nodes and third-party BLE sensors: more measurements without wiring every signal back to the gateway.

Geotechnical instrumentation

Vibrating wire.

RokkaBOX extends the VigiaBOX family to piezometers and other vibrating-wire instruments.

RokkaBOX / Connected geotechnics

Vibrating wire also joins the data network.

Four vibrating-wire channels per RokkaBOX. Geotechnical data acquisition, local logging, and delivery to the mine site's systems.

4
vibrating-wire channels By the RokkaBOX team

Each reading carries the instrument's identity, timestamp, reference values, and calibration, so the monitoring record keeps its context.

RokkaBOX con panel solar montado en un poste, cableado hasta un piezómetro de cuerda vibrante
RokkaBOX mounted on a pole, connected to a piezometer.
03 / Site-specific communications

The network changes.
Where your data goes doesn't.

A mine site with cellular coverage, a remote lagoon, and a distributed instrument network are not the same problem. We combine networks point by point, based on distance, power consumption, and available service.

4G / LTE

Telemetry from sites with cellular coverage, without relying on your local network.

The most common network at mine sites.

4G + satellite

Both networks in one device: if cellular is unavailable, the data goes out over satellite.

Automatic network switching.

LoRa / LoRaWAN

Long-range, low-power radio for networks with many points; a gateway collects the data and sends it on.

Environmental sensors and distributed networks.

Satélite / Iridium

Telemetry where there is no terrestrial coverage, as the primary link or as backup.

Backup when no other network is available.
Close to the instrument

BLE for nodes and on-site diagnostics. Ethernet when the device sits on the plant network; Wi-Fi if the project calls for it.

04 / Wolke Connection Broker

A new instrument.
Not a new integration from scratch.

The Broker decouples how each device sends its data from how your system receives it. It preserves the original message, interprets the variables, and delivers them to one or more destinations: your platform keeps a stable data contract, and the next sensor is integrated at the edge.

Diagrama del Connection Broker: desde tus equipos, el Broker conserva el mensaje original, interpreta las variables y entrega a tus sistemas, con trazabilidad de cada envío
ENTRADAS
VigiaBOX / RokkaBOX
Gateways y equipos compatibles
Fuentes MQTT / HTTP
WOLKE CONNECTION BROKER

Original → Interpretación → Entrega

Identidad · Decodificación · Grupos y reglas

Registro original Estado por destino Historial
DESTINOS HABILITADOS
Webhook / API REST
MQTT / Azure Service Bus
GeoVigía / Sistemas propios
ORIGIN

The original message is kept.

The received message and its interpretation are stored separately, so the original can always be reprocessed.

NORMALIZATION

Different sources, usable data.

A decoder for each device turns every format into named variables with units.

DISTRIBUTION

One source, multiple destinations.

Each device or group delivers to its assigned destinations, under its own rules.

TRACKING

Received doesn't mean delivered.

Each delivery records its status, attempts, and response, so you can tell a source failure from a receiver failure.

Retry a delivery Resend historical data Reprocess the original message
05 / Commissioning and operation

Commission on site.
Configure from anywhere.

The device is commissioned on site, with no data coverage needed. Once installed, it is configured, diagnosed, and updated remotely. Fewer field visits.

In the field, over BLE

Scanning, signal readings, status, and configuration from an Android app, without relying on cellular coverage.

Remotely, from the platform

Configuration read and write, remote commands, and a trace of every message.

Link diagnostics

VigiaBOX receives on two antennas and reports the signal on each. That way you can tell a weak-coverage area from a faulty sensor.

06 / Continuity and autonomy

Built for outages.
Not just for connectivity.

Data backup, power, and diagnostics are part of the same system. Continuity takes more than choosing an antenna.

Ilustración de una estación en alta cordillera en tres momentos: transmite con normalidad, guarda las mediciones durante un corte de enlace y las reenvía al volver la señal
1

Normal link

2

Link outage

3

Link restored

  1. Normal link

    Each measurement goes out to the platform as soon as it is taken.

  2. Link outage

    The device keeps measuring and stores every record on site.

  3. Link restored

    Resends the backlog in order, with its original timestamps, and confirms it reaches its destination.

An important distinction.

Recovering historical data is no substitute for a timely alert. If the system stops acquiring data because it runs out of power, it cannot reconstruct measurements it never took. That is why we size the solar panel, batteries, and backup to the sensors, power consumption, climate, and operating cadence.

above4.500masl Mine site in the high Andes, in continuous operation.
down to−30 °C Ambient temperature at that same site. Device operating range: −30 to 50 °C
100 ThermoGuard nodes on heat-traced lines at a single plant.
Dozens of MUSUX units operating in tailings, desalination, and oceanography.
07 / Open integration

Your platform shouldn't limit what you can measure.

Use GeoVigía, our monitoring and reporting platform, or receive the data in your own systems. Acquisition, the Broker, and visualization are separate pieces, so you do not need to change your platform.

GeoVigía: centro de control operacional con instrumentos vigentes, disponibilidad de datos, episodios TARP y entregas DGA (datos de demostración)
GeoVigía · operations control center · demo data
GeoVigía: episodio TARP de un piezómetro con su regla configurada y expediente (datos de demostración)
TARP event · rule and case file · demo data
01 · Web platform

GeoVigía

Control center, historical data, TARP events, reconciliation with the DGA (Chile's water authority), and automatic reports by email, PDF, or Excel. Deployed in the Wolke cloud, on-premises, or hybrid.

Pantalla HMI local en un gabinete de planta, con datos de demostración
02 · In the field

Local HMI

A screen on the enclosure to operate the zone even if the link goes down.

03 · Your systems

SCADA, Power BI, or your cloud

Delivery via REST API, webhooks, MQTT, or Azure Service Bus, with delivery status for each destination.

08 / Security

Security at every stage, from device to screen.

Your data travels through field devices, public networks, and the cloud. We protect each stage with controls your cybersecurity team can review.

Ilustración de los cuatro tramos protegidos del dato: la estación en terreno bajo una cúpula, el enlace dentro de un conducto de vidrio, la nube con su réplica y su bóveda de secretos, y las personas tras un control de acceso
1

Device

2

Link

3

Cloud

4

People

01 · Device

VigiaBOX in the field

  • Supports per-device credentials, each limited to its own topics.
  • Local Bluetooth configuration with authenticated pairing.
  • Modbus writes and output control only when the project enables them.
02 · Link

Encryption in transit

  • The device initiates its own connections to the platform.
  • Supports MQTT over TLS with server certificate validation.
  • Deliveries to your systems over HTTPS, MQTT over TLS, or Azure Service Bus, authenticated per destination.
03 · Cloud

Microsoft Azure

  • Infrastructure in Chilean and US regions.
  • Databases and storage encrypted at rest.
  • Secrets managed with Azure Key Vault.
  • Automated backups, with retention and redundancy set per service.
04 · People

Controlled access

  • Administration through Microsoft Entra ID with two-step verification (MFA).
  • Role-based permissions and logical separation of data between customers.
  • Sign-in logging and audit trails for access and configuration changes.
  • Remote access over a segmented VPN, only to authorized devices and services.
Continuous monitoring

We assess vulnerabilities with Microsoft Defender for Cloud, centralize logs in Azure Monitor, and get alerts before a certificate expires.

ISO/IEC 27001

Implementation in progress: our information security management system.

For your review

Technical documentation of our architecture and controls for your cybersecurity team. Write to us

Device and link controls are enabled according to the model, firmware, and configuration used in each project.

Let's talk

Which instrument or location is hard to connect?

Tell us what you need to measure, what the site is like, and where the data needs to go.

Let's talk about your project