Dobler Data Solutions designs, builds and runs data platforms on Microsoft Azure and Microsoft Fabric. The same engineering produced our own products, Dobler Insights and Fabric Control, and it is available for your project, with ongoing operations when you want them.
Clients include PersonalMed and 4L Data Intelligence.
| Capability | As a product | As a project | Ongoing |
|---|---|---|---|
| Dobler Insights | |||
| Fabric Control | |||
| Dobler Insights | |||
Data integrationFiles and databases brought into one place. Dobler Insights checks and loads spreadsheets and CSV files and copies databases into daily snapshots; on a project, we build the pipelines in Azure Data Factory and Microsoft Fabric.
Lakehouse and warehouseLakehouse, operational data store or warehouse, chosen for how the data is used and built on Microsoft Fabric or Azure. How we compare the three.
Governance and recoveryFabric Control governs, backs up and recovers a Microsoft Fabric estate on operational metadata alone. On a project, governance is built into the platform from the first pipeline.
Dashboards and reportingPower BI dashboards and reports in front of everyone who needs them. Dobler Insights does it without a Power BI license for each viewer, with row-level security for any sign-in.
Migration to AzureSSIS packages and on-premises warehouses moved to Azure Data Factory and Microsoft Fabric as a planned project. Read our migration playbook.
Ongoing means we run what we built, when you ask us to. Projects and ongoing work are priced at a flat fee.
We build our products the way we build client platforms, on Microsoft Azure, Microsoft Fabric and Power BI. Each one has its own site.
Power BI dashboards and reports for every user, without a Power BI license for each one.
Governance, backup and recovery for Microsoft Fabric, on operational metadata alone. Your data never leaves your tenant.
Most work starts as a project with a clear scope. When it is done, the platform is yours. If you would rather we keep running it, we do.
We map your sources, your users and the outcome you need, and agree the scope and a flat fee before the work starts.
Agents carry the repetitive engineering. Senior practitioners set the architecture and review every piece of it.
You get a working, documented platform, and the knowledge to run it yourselves.
If you want us to operate it, we monitor, maintain and improve it under an ongoing agreement.
Every engagement is priced to its scope. We stopped billing by the hour, and wrote down why: Why we walked away from the billable-hour model.
Proprietary agents carry the repetitive work of the data lifecycle: ingestion, modeling, governance and operations, continuously. Senior practitioners set the architecture, enforce the standards and stay accountable for the result.
The work does not stop for handoffs, and the knowledge does not leave with a person.
How the agent model worksArchitecture, migration, governance and analytics on the Microsoft data stack, from the people who build on it.
Fabric Control's governance tier is free forever for one Azure tenant: health, capacity, refresh outcomes, drift and who has access in one view. How to get…
Managed BI answered a real question: who keeps the reporting alive after go-live. The answer held; the delivery model didn't. Here's what changed and why.
Most data governance fails the same way. Not with a dramatic breach, but quietly: standards that were set carefully at the start erode a little each week…
A platform to build, a migration to plan, or one of our products to evaluate: it starts with a conversation.