What we build on Microsoft Azure and Fabric
Five kinds of work, from bringing data in to putting it in front of the people who use it. Each is available as a project. Two are also products.
Data integration
Your data lives in CRM, ERP, finance and operational systems, in databases and in spreadsheets. We bring it into one governed store and keep it current, with every pipeline built to the same standard.
- Pipelines in Azure Data Factory and Microsoft Fabric
- Databases and files, scheduled and monitored
- As a product: Dobler Insights checks and loads spreadsheets and CSV files, and copies databases into daily snapshots
Lakehouse and warehouse
Lakehouse, operational data store or warehouse: the right storage depends on how the data is used, how often it changes and who reads it. We design it on Microsoft Fabric or Azure and build it to stay current.
Often the answer is more than one, each in the role it does best.
Governance and recovery
Governance that holds up because it is part of how the platform runs, not added afterwards: standards, lineage and access enforced from the first pipeline, so drift does not build up between audits.
- Governance built into projects from the start
- As a product: Fabric Control governs, backs up and recovers a Microsoft Fabric estate on operational metadata alone
Dashboards and reporting
Power BI dashboards and reports that people use, on a data model they can trust: every metric defined once, so finance, operations and sales work from the same numbers.
- Semantic models, reports and paginated reports in Power BI
- As a product: Dobler Insights puts them in front of every viewer without a Power BI license for each one, with row-level security for any sign-in
Migration to Azure
SQL Server, SSIS packages and on-premises warehouses moved to Azure Data Factory and Microsoft Fabric as a planned project: an inventory of what each package does, an order of migration, and validation as each piece moves.
How you get it
The same five capabilities, three ways. Projects and ongoing work are priced at a flat fee set by the scope; we do not bill by the hour.
- As a product. Dobler Insights for dashboards and data intake, Fabric Control for governing and protecting Microsoft Fabric. Each has its own site.
- As a project. Scoped, built and handed over: a working, documented platform that is yours to run.
- Ongoing, on request. When you want us to run what we built, we monitor, maintain and improve it under an ongoing agreement.
Questions we hear
Do you do one-time projects or ongoing work?
Both. Most work starts as a project with a clear scope. When it is done, the platform is yours to run; if you would rather we run it, we do that under an ongoing agreement.
How do you price the work?
Every engagement has a flat fee, set by its scope. We do not bill by the hour.
Which cloud do you build on?
Microsoft Azure and Microsoft Fabric, with Power BI for reporting.
Do we have to use your products?
No. Dobler Insights and Fabric Control are separate products with their own sites. A project does not depend on either of them.
Who does the work?
Proprietary agents carry the repetitive engineering. Senior practitioners set the architecture, review the work and stay accountable for the result. How the agent model works.
Tell us what you are building.
A platform to build, a migration to plan, or one of our products to evaluate: it starts with a conversation.