HOLOIN
Book a demo
Menu

live · Agriculture

For the grower whose schedule waters whether it rained or not.

Watered when the soil says so.

Irrigation that waits for the soil, holds for rain and meters every litre — and it’s yours.

See it on a farm like yours — 15 min →What you need
North Field · Zone A · Thalvenna Farm · its twinlive
Soil moisture
28% target, reached
Valve
closedon its own report
Water
520L · metered

RuleIrrigate when dry: water the zone until the soil says enough; refuse a run when it has rained more than the rain hold you set.

  • 20:23:25Run requested · the valve opens on its own report
  • 20:23:26Flow confirmed · the meter moved
  • 20:23:42Run ended · target 28 % reached, valve closed · 520 L
  • 20:23:25Zone B refused · Rain hold (the rule's setting): 12 mm in the last 24 h at the farm's weather station (limit 5 mm).
What the twin holds: moisture by depth · EC · crop stage · valve · flow · runs · historydemo run
1The problems

What a grower actually hears.

Four sentences from the people who run fields. Each one is answered below, with the screen that answers it.

the grower, the morning after the rain
“The schedule watered the field the morning after it rained.”
Answered by the rain hold ↓
the grower, at the valve box
“We water by the clock, not by the soil.”
Answered by a run that ends at the soil’s target ↓
the farm manager, walking the rows
“A valve stuck and we found out from the crop.”
Answered by no flow, no run ↓
the owner, at the water bill
“Nobody can say how much water each zone used.”
Answered by metered litres, per zone and run ↓
2How HOLOIN answers each

Four problems, four screens.

Each answer below is something the product did in the demo run, shown on the screen where it did it.

Problem 1 · “It watered after the rain.”

A run is refused when it has rained more than your hold.

Before a run opens a valve, HOLOIN reads the farm’s weather station. If more rain fell in the window than the rain hold you set, on the farm or in the rule, the run is refused before any valve moves, and the reason is stored.

Outcome No watering right after rain.
Zone · rain hold↓
The zone panel of North Field · Zone B: dry at both depths against the crop stage’s band, its rule’s run refused by the rain hold with the reason in the rule’s own words, nothing watered today, and the twin’s maturity line.
From a demo run: Zone B’s run refused by the rain hold, the reason in the rule’s own words.
Problem 2 · “By the clock, not by the soil.”

Watered until the soil says enough.

A rule can start a run when a zone’s soil is dry. The run ends when moisture at the roots reaches the target (the crop stage’s, or one you set), not on a timer. The run records why it ended.

Outcome Each zone gets the water its soil asked for.
Zone · irrigation run↓
The zone panel of North Field · Zone A after its rule watered it: status normal, moisture at both depths back within the crop stage’s band, the last run completed with its water, today’s water, no open alarms, and the twin’s maturity line.
From a demo run: Zone A after its rule watered it: moisture back in its band, the run completed and the day’s water.
Problem 3 · “A valve stuck.”

No flow, no run: the valve closes and an alarm goes off.

Opening a valve is a command, and the valve counts as open only on its own report. If the flow meter shows no water within minutes, the run is stopped, the valve closed and a critical alarm raised. A valve that won’t close is its own alarm.

Outcome A stuck valve is an alarm the same morning, not a brown patch a week later.
Zone · run
requestedRun of Zone Athe valve opens on its own report20:23:25
flowWater flowingconfirmed by the meter20:23:26

From the demo run. The run started at 20:23:25; the meter confirmed water flowing at 20:23:26.

Problem 4 · “How much water.”

Every litre, per zone and per run.

The meter counts what each run used. The zone keeps its runs; the farm adds them up.

Outcome The water bill reads like a list of runs.
Water · Thalvenna Farm
this runZone Acounted by the meter520 L
farmAll runsthe farm’s runs in the demo4,560 L

From the demo run. 520 litres for this run of Zone A; 4,560 litres across the farm’s runs in the demo.

And the rest of the day’s work

The field mapZones coloured by their state on a demo map, nothing fetched from the internet.
Moisture by depthEach probe’s moisture at each depth, against the crop stage’s band, with its target beside it.
Crop stageThe zone’s crop and its stage, beside its readings.
SchedulesA run can follow a schedule; once the farm’s rain hold is set, it refuses a scheduled run too.
The technician’s phoneWork orders and alarms, each with the zone’s location; every action offline-safe.
The weather stationRain, temperature, wind, read into the farm.
ReportsWater per farm, field or zone, with litres, depth and the number of runs: a table or a CSV.
Ready-made definitionsThe probes, valves and meters listed with how each was verified.
3The twin of a zone

The zone is the record. Everything attaches to it.

A zone is a piece of a field with its soil probe; its irrigation group has the valve and the flow meter, here read over LoRaWAN; a weather station serves the whole farm.

Soil
Moisture by depth

Moisture, temperature and conductivity at each depth.

Crop
Its stage

The crop and its stage.

Valve
Open or closed

On its own report.

Flow
The meter

What the meter counted, per run.

Runs
Each run, and why

Started, flow confirmed, ended and why, or refused and why.

Then
History

Every reading against the zone; its last runs on the twin, every run on the runs list.

A field is split into zones, and each zone’s soil is judged on its own, against its crop stage’s band; the field map shows every zone’s status at once.

Agriculture · field map · demo map
Thalvenna Farm on the demo map: North Field and South Field, each split into Zone A in green and Zone B in amber, each zone labelled with its soil moisture.
Thalvenna Farm’s two fields on the demo map: each zone coloured by its soil-moisture status and labelled with its reading — green within its band, amber outside it.
4What the twin changes in the day’s work

Less water. Fewer surprises in the rows.

Stated as changes, not as numbers: your numbers are yours to measure, and Why it pays gives you the arithmetic.

Before
  • The schedule waters after the rain.
  • A run ends when the timer does.
  • A stuck valve is found from the crop.
  • Water use is a monthly bill.
  • Each zone is a line in a notebook.
With the twin
  • A run is refused when it has rained more than the rain hold you set.
  • A run ends when the soil reaches its target.
  • No flow, no run: the valve closes and an alarm goes off.
  • Litres per zone and per run.
  • Each zone a twin, on a map, with its history.
5OT and IT

OT and IT, in one twin.

Thalvenna Farm · LoRaWAN · the gateway
LoRaWAN gateway · heard · uplinks todayok
radio
Soil probe · Zone A · heardok
Valve · Zone A · heardok
Flow meter · heardok
The gateway is a device too. When a registered gateway goes quiet, the devices last heard through it are traced to it on their own — nothing to wire up: one alarm names the gateway and the probes and valves behind it are held under it, once the Upstream cause rule is switched on (it ships on for any company that has declared connections; a LoRaWAN-only farm turns it on once).

OT and IT, in one twin. Probes, valves and meters are the OT, read through the bundled LoRaWAN network server; the gateway that carries their radio is the IT. The twin records which devices each gateway hears, so once the Upstream cause rule is switched on, a lost gateway is one alarm, not one per device.

OT · what is measured

Soil moisture, temperature and conductivity at each depth, the valve’s state, the meter’s volume, the weather station’s rain: each a LoRaWAN device the twin places in its zone.

IT · what keeps it reporting

The bundled LoRaWAN network server and the gateways it hears; a device registered once, in HOLOIN, with its keys kept encrypted. Each device’s twin shows its radio quality and the gateway it was heard through; the gateway’s twin shows its uplinks.

6How it’s deployed

Buy the devices. Everything else comes inside.

One install bundle carries the servers a farm needs. The gateway hears the probes, valves and meters; you draw the zones and place each device.

You supply
  • One Linux server with Dockeryours, or one we run for you in the country you choose
  • The probes, valves and metersany model listed, or your own with a published map
  • The ports your IT opensthe install guide lists them
Inside the install
  • The LoRaWAN network serverfor the probes, valves and meters, through a gateway on the farm
  • The MQTT endpointfor devices that publish
  • The HTTP endpointfor devices that push JSON
  • The database, the backups, the web entryone compose file, one address
Kept running by the install itself
  • One scriptready in 2 min 42 s on the acceptance box (run 39194860273)
  • Nightly backup, monthly restore drilla failed one is an alarm in the product
  • Upgrade in placesame volumes, registrations and readings intact, proven on every release
  • No telemetrythe bundled servers’ phone-home is off; CI fails if any container reaches out

The servers this kind of asset uses, each shown only when its acceptance run passed; statuses from the facts file.

7Without HOLOIN

Five systems, or one.

The same farm, run the usual way. No names: the categories are what matters.

Bought separately
  • An irrigation controller — runs by the clock.
  • A probe vendor’s portal — moisture graphs, the decision left to you.
  • A weather service — a forecast, not the farm’s own rain.
  • A water meter read by hand — a monthly figure.
  • A notebook of zones — kept by whoever remembers.
Five contracts, five logins, no path from one to the other. When a zone goes dry, nobody can say why.
In HOLOIN
  • Runs by the soil — ended at the target, refused after rain.
  • The probe in the rule — the reading starts the run and decides when it ends.
  • The farm’s own station — its rain holds the run.
  • Litres per run — the meter confirms and counts.
  • A twin per zone — on a map, with its history.
One installation, one database you own, one price counted in devices.
8What it costs

Counted in devices. Never in people.

One licence per installation, per year, by device tier. A probe or a valve is a device; a grower’s login and a technician’s phone are not. Add growers and technicians without a change to the bill.

The whole grid, every tier and every pack, is on Pricing — published, with what counts as a device and what is included.

US$4,000a year
Twelve zones on two farms: a probe, a valve and a meter in each, a weather station and a gateway on each farm — the 100-device tier, from the published grid.
  • The platformUS$2,500
  • The Agriculture packUS$1,500
  • Growers and techniciansincluded
  • The LoRaWAN network server, the phone appincluded
9Secure, and kept running

Your server. Your farm’s data. Nothing phones home.

Not a policy page: each of these is a property of the software you can check on your own server.

One installation, yours

Installed from a bundle that carries everything it needs. Never a shared cloud: one installation per customer, or one your integrator runs for you, each client a company of its own.

PostgreSQL you own

Every reading, alarm and record in a database you administer. A nightly backup you can restore anywhere, drilled monthly.

A valve opens only on a rule or a person

A valve opens only by a rule a person turned on, a schedule a person set, or a person’s command, and only if that valve is allowed to take commands. It counts as open only on its own report; no flow on the meter within minutes stops the run with an alarm. Every command is logged.

Nothing phones home

No telemetry in the product, none in the bundled servers. Proved with the network sealed on every release.

Your rules stay yours

Lines, rules, schedules and what the twin learned are text and arithmetic in your database; they leave with you.

An audit log that can’t be edited

Every change, by whom, from where — append-only in the database itself, for seven years, even for the database’s own administrator.

10The four questions

What you actually want to know.

Do I have to install anything?

No. We run HOLOIN for you on a dedicated server in the country you choose, never shared with another company, and you can take it with you. If you have your own servers, install it there instead; same product.

What do I need?

A probe, a valve controller and a flow meter in each zone, a weather station on the farm, and a LoRaWAN gateway. The install guide lists the ports.

What does it cost?

Per installation, per year, by device tier: from US$4,000 a year for the platform and Agriculture, up to 100 devices. The whole grid is on Pricing. No per-seat fees; every grower and technician is included.

Who do I call?

Hours, channel and response time: on request. Every installation can produce a support bundle on demand, a readable archive with no personal data or secrets, which your IT team can check before it goes to us.

11The way in

See it running on yours.

I’m responsible for the fields

Fifteen minutes on a farm like yours — no slides.

See it on a farm like yours — 15 min →Get demo access →

I install systems for clients

One installation per client, each a company of its own. The LoRaWAN network server inside, the ports in the install guide.

Start a partner conversation →