Frequently asked questions

Yres is a data warehouse automation platform for Microsoft Azure. It automates building, loading and managing your data warehouse: from source connection to Power BI dashboard. You design pipelines visually in the Yres interface; Yres translates this to Azure Data Factory pipelines.

Yres Advanced costs €674/month. Fixed price, no surprises. See the pricing page for all packages.

Yres stands out through native Dutch ERP connectors (Exact, AFAS, SAP), preset sources (CBS, Tweede Kamer), visual pipeline design that translates directly to ADF, automated health checks, point-in-time rollback per table and transparent pricing without hidden costs. Where other tools are often generic, Yres is specifically built for the Dutch market and Azure.

Yres also uses ADF as engine, but abstracts the complexity. Where dbt+ADF costs weeks of configuration and offers no native Dutch ERP connectors, Yres delivers this in one platform with visual pipeline design, monitoring, health checks and preset sources.

Yes. All pipelines in Yres, data ingestion, orchestration, technical operations, are ADF pipelines. You design them visually in Yres, Yres generates and manages the ADF resources.

No. Yres works with your existing Azure databases. No forced migration.

Yes. Yres offers visual lineage at object level (tables, views, procedures, functions, materialized views) with impact analysis. So you can see what breaks downstream when you change something. Column-level lineage is currently not available.

Currently Yres offers lineage at object level (tables, views, procedures, functions), not at column level. Object-level lineage gives you insight into dependencies and impact analysis for changes.

Yres generates ADF pipelines. The platform manages them fully. Existing manual ADF pipelines can continue running alongside Yres.

Yes. Full CI/CD integration via Azure DevOps with DTAP.

Pipelines that Yres generates are managed by Yres. Whatever you put in the custom folder always stays, through regeneration and through upgrades. You outsource the standard work and keep the exceptions.

Seven load types and generic connectors for REST, OData, files and Microsoft Graph cover most of it, with pagination and authentication as configuration. If a source genuinely does not fit, you load it alongside into the same database.

Yes. The warehouse is an ordinary Azure SQL database in your own subscription. Your own tables, views, procedures and pipelines alongside it are normal use, not an exception.

Through DTAP and your own Azure DevOps. A change moves to the next environment as a whole, including everything it depends on. Nobody edits anything in production.

The database and the ADF side always ship together, and migrations are version-gated, so you land on the same point from any version. Your own objects and your custom folder are left alone.

The entire administration lives as ordinary tables in your own database. You query, back up and export it with the SQL tooling you already have. Nothing sits on our side.

That is what the pattern is for. Every source is configured the same way, every load logs the same, every failure looks the same. You ask a successor to know one pattern, not thirty exceptions.

We impose no restrictions when you leave. Your history, your pipelines, your configuration and your secrets live in your own Azure and keep working. The engine itself is encrypted: you can run it, not read it. You build further with your own SQL and ADF.

Yres is an official partner of Exact Online, AFAS and SAP (Analytics Cloud, S/4HANA, HANA, Datasphere). We also support databases, REST APIs, OData, Salesforce, Dynamics 365, SharePoint and more.

Yes. In addition to the preset connectors, Yres can connect any source via REST API, OData, ODBC or custom connectors. A custom source is often delivered within a single day of consultancy hours. Contact us to discuss your specific source.

Yres is ISO 27001 certified. Data always stays in your own Azure tenant; Yres does not host customer data. Access runs through Azure AD SSO with a fine-grained role-based access control (RBAC) setup, while network access is shielded by firewall rules.

All data stays in your own Azure tenant, in the region you choose. Yres has no access to your data and does not store customer data outside your environment.

Yes. Yres integrates with Azure AD (Entra ID) for Single Sign-On with role-based access control.

That depends on your environment, but the first sources are typically connected within a few days. No months-long implementation projects.

Yes. Yres works with your existing Azure SQL Database, Synapse, or other Azure data stores. No migration needed.

Switching to or from Yres is always open for discussion. We are happy to discuss this in an architecture session so we can understand your situation well and create a suitable migration plan.