IRIS is now called Yres
IRIS and Yres are the same product. The name changed with version 1.56; the functionality, the vendor and your existing environment did not. If you are looking for documentation about IRIS, you are in the right place: everything below is about the platform you know.
Last updated:
What changed
Only the name and the address. The product is called Yres, the website has been at yres.eu since September 2026 instead of oogopdata.nl, and support goes to feedback@yres.app (until version 1.56 that was Feedback@iris-dwh.nl). Old links to oogopdata.nl keep working: they redirect automatically to the matching page on yres.eu, including from an old document or an external site.
The vendor is unchanged: Plainwater B.V. in the Netherlands. Your contract, your environment, your data and your agreements are not affected by the rename.
What stayed the same
Everything the product does. The same seven load types, the same SCD2 history, the same Azure Data Factory pipelines in your own tenant, the same change management and the same monitoring. An environment delivered under the name IRIS keeps running unchanged under the name Yres. There is no migration, no conversion and no reinstall.
Why you still come across IRIS in your own environment
Technical names were deliberately left alone. Renaming a database, a resource group or a pipeline that is already in production breaks references in scripts, reports and CI/CD wiring — on your side and on ours. The name of an object says nothing about what it does, so that cost does not pay for itself.
Depending on how old your environment is, you may see:
- In prose and in the interface we use Yres throughout
- The knowledge base spells object names exactly as they appear in your database, so both forms show up there
- If you meet a name you cannot place, it is in the glossary of the knowledge base
| What you see | What it is |
|---|---|
| IRIS_DWH | the name of the Azure SQL database holding your data warehouse |
| kv-iris-…, adf-iris-… | the key vault and the Data Factory in your resource group |
| Dynamic Workflow IRIS | the generic load pipeline; on newer versions Dynamic Workflow YRES |
| IRIS_VERSION | the setting holding your database version; on newer builds YRES_VERSION |
| AllowUpdatesInIrisSchemas | the setting called AllowUpdatesInYresSchemas on newer versions |
| CustomIris | the schema for your own objects; newer environments use CustomYres |
Where the documentation lives now
The full knowledge base is at yres.eu/en/wiki, in English and Dutch. It covers the concepts (load types, history, change management), the setup per source, the object-level reference and the glossary where the old and new names sit side by side. The Yres Academy adds courses with knowledge checks and a certificate.
Frequently asked questions
Is Yres the same product as IRIS?
Yes. Only the name changed, with version 1.56. The functionality, the vendor (Plainwater B.V.) and your existing environment are unchanged.
Do I have to do anything now that IRIS is called Yres?
No. There is no migration or reinstall. An environment delivered as IRIS keeps running unchanged.
Why does my database and my Azure still say IRIS?
Technical names such as IRIS_DWH, kv-iris-… and adf-iris-… were deliberately not renamed. Renaming running resources breaks references in scripts, reports and CI/CD, while the name says nothing about what the object does.
Do my old links to oogopdata.nl still work?
Yes. Every old URL redirects automatically to the matching page on yres.eu, including from external sites and old documents.
Has the support address changed?
Yes. Feedback goes to feedback@yres.app; until version 1.56 that was Feedback@iris-dwh.nl.
