Cost calculator
What does the same Azure environment cost without Yres?
Yres runs on Azure Data Factory and Azure SQL in your own tenant. Move the sliders and see what those resources cost per month if you build it yourself, and what they cost with Yres.
Systems you connect, such as AFAS, Exact or SAP
Average number of tables you load per source
How often the data is updated each day
Data models for Power BI or other reporting
Total Azure
€3,677 per month less on Azure resources
Self-built on Azure
€4,518per month
With Yres
€840per month
| Self-built on Azure | With Yres | |
|---|---|---|
| Orchestration and copying (Data Factory) | €96 | €96 |
| Database (Azure SQL) | €4,380 | €744 |
| Compute outside the database | €41 | €0 |
Yres Advanced: €674 per month, fixed price.
Not included: the hours to build the environment yourself, keep watch over it and adjust it with every change.
How are costs calculated?
This is an estimate, not a quote. The calculator uses rules of thumb and rounded Azure list prices for West Europe (pay-as-you-go, without reservations or discounts). In specific cases the real outcome can differ strongly: because of the size of your tables, the weight of your models, your own Azure agreements or a different setup. If you want to know precisely, book a demo.
What we compare
The same Azure resources, twice: self-built on Azure Data Factory and Azure SQL, and the same work with Yres. Per month of 730 hours, everything times the number of environments. The three layers below add up to the total.
1. Orchestration and copying (Data Factory)
The same on both sides. Per table per refresh: 6 activity runs at €0.00093 and one Copy of at least 1 minute on 4 DIU at €0.233 per DIU-hour. About €0.021 per table per refresh.
Now: 75 tables, 1 times a day.
2. Database (Azure SQL)
Self-built, the database sits on the peak tier around the clock, the tier that can handle the load. Azure does not scale a SQL database well on its own, so in practice it stays high. Yres sits on the base tier and scales up to the peak tier only while loading, then straight back down. That is part of Advanced and Ultimate; for Essentials we count no scaling benefit.
Which tiers depends on the total number of tables (sources × tables per source). Now: 75 tables, so S3 as base and S9 as peak.
Load window per refresh: 1 minute per table plus 45 minutes per reporting model, at least 3 minutes and never longer than the time between two refreshes. More refreshes means going to peak more often and therefore a smaller difference. Now: 165 minutes per refresh, 84 of the 730 hours a month on peak.
| Tables in total | Base | Peak |
|---|---|---|
| 0 – 5 | S1 | S3 |
| 5 – 10 | S2 | S3 |
| 10 – 25 | S3 | S4 |
| 25 – 50 | S3 | S6 |
| 50 – 250 | S3 | S9 |
| more than 250 | S3 | S12 |
Azure SQL tier prices (per month)
DTU model, Standard tiers, West Europe, rounded.
| Tier | Per month |
|---|---|
| S0 | €13.70 |
| S1 | €27.40 |
| S2 | €68.40 |
| S3 | €137 |
| S4 | €274 |
| S6 | €547 |
| S7 | €1,095 |
| S9 | €2,190 |
| S12 | €4,380 |
3. Compute outside the database
Self-built counts one Data Flow (Spark cluster) per reporting model per refresh: 8 vCores, 10 minutes including start-up, at €0.255 per vCore-hour. About €0.34 per run.
Yres counts nothing here: all transformations are SQL in your own database. The Yres factory contains no Data Flows.
Plan and licence
The plan follows from the number of sources and environments, as on the pricing page: Essentials up to 2 sources and 1 environment (€350), Advanced up to 5 sources and 2 environments (€674), above that Ultimate (€997). The licence is shown separately and is not part of the Azure amounts.
What stays out of the sum
Storage, Key Vault and a self-hosted integration runtime, if any: the same on both sides and small. The hours to build an environment yourself, keep watch over it and adjust it with every change: not included.
Where the difference comes from
The database scales around the load
Azure does not scale a SQL database well on its own. Self-built, it stays on the heavy tier. Yres raises it while loading and brings it straight back down afterwards.
No compute outside the database
All transformations are SQL in your own database. No Spark cluster, no server that has to keep running, no second bill.
The same Data Factory, counted equally
Copying and orchestration cost the same with Yres as without. We leave that as it is; the difference is in the two layers above.
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.