Skip to content
Koidra
Book a demo

Integrations

Your climate computer stays where it is

Koidra runs on top of the computer you already own. Here is the honest list, rather than a claim about connecting to anything.

Hoogendoorn iSii
Read and write. Hoogendoorn stopped selling iSii on 1 January 2026; we did not stop supporting it.
Hoogendoorn IIVO
Read and write.
Priva Connext
Read and write, including control modules.
Ridder
Read and write.

Running an iSii? You do not need to replace it

Hoogendoorn stopped selling the iSii on 1 January 2026 and is putting its future into IIVO. That is a reasonable decision for them, and it leaves a lot of glass running a computer that works perfectly well on a product line that has moved on.

We read and write both. An iSii house can run autonomous growing now, on the hardware it already has, without a capital project and without a season lost to commissioning. If you later move to IIVO the strategy comes with you, because the strategy was never in the box.

The strategy lives above the climate computerKoidra reads and writes an iSii today and an IIVO tomorrow. The growing strategy is held in Koidra, not in the box, so moving to IIVO later carries it across.Koidrathe growing strategy lives hereHoogendoorn iSiithe computer you haveHoogendoorn IIVOthe one you may move to
The strategy is held above the computer, so changing the computer does not lose a season of it.

Reading is one half. Your growers are the other

Most of what a greenhouse knows never reaches the climate computer. Koidra takes it in as proper data, stored the same way as a sensor reading.

  • Crop registrations your growers take on a tablet in the aisle
  • Photographs of the crop, against the compartment and the date
  • Readings taken by hand where no sensor exists
  • Notes on what was changed, and why

It is also what lets the crop model adapt to what your growers actually see.

Writing back

Reading data is a low-risk integration. Writing setpoints is not, and we treat it that way. Control writes run through the same supervisory layer whether a grower or KoPilot initiated them, inside bounds your head grower sets.

Plenty of sites run for a long time on read-only access, and that is a perfectly good place to be. Everything short of autonomous control needs nothing written back at all.

What is read, what is written, and by whomThe climate computer and the growers' tablets are read into Koidra. Setpoints are written back only through the supervisory layer, inside bounds the head grower sets, whether a grower or KoPilot asked for the change.Write, inside bounds the head grower setsRead, low riskClimate computerKoidraGrowers' tabletsregistrations, photos, readings, notesSupervisory layerClimate computerKoPilot, or a grower
Two things are read. One thing is written, and it goes through the same supervisory layer whoever asked for it.

Tell us what you run

Send us your climate computer and a sample export. We will tell you what we can read, what we can write, and what would need building.

Talk to our team