Why DLH?

The data platform for operational businesses, from first sync to governed AI.

Our mission

DLH.io is a complete data platform for organizations that run on operational systems: point of sale, HR and payroll, ERP, and the databases behind them. DLH includes DLH Data Sync for managed data movement, self-hosted agents for systems behind your firewall, dbdeux, the managed dbt platform, for transformation, a shared catalog and semantic layer, and analytics and embedded dashboards with Bideux. Every product runs against the warehouse or lakehouse you already own.

DLH started with a mission: give every organization, not only the ones with large data teams, a fast and trustworthy path from scattered operational data to confident business decisions. A regional restaurant group, a multi-site manufacturer, or a ten-person finance team should get the same data foundation that large enterprises spend years building, without hiring a platform team to run it.

That idea became the DLH platform. Instead of buying an ingestion tool, a dbt host, a catalog, a BI tool, and an AI layer separately and stitching them together, you get one account, one security model, and one monitoring layer across the whole path from source to answer. You start from proven best practices and pre-built models, not a blank canvas.

DLH has since grown from a data pipeline service into a full platform. dbdeux turned managed dbt into a complete analytics engineering workspace. The SQL Server and Oracle agents brought hybrid deployment to systems that never touch the public internet. Bideux brings governed dashboards into the applications your customers and teams already use.

What makes DLH different

Warehouse-native: your data stays yours

DLH moves and models your data, but your warehouse or lakehouse is always the system of record. Data lands in Snowflake, Databricks, BigQuery, Redshift, Microsoft Fabric, Azure Synapse, MotherDuck, PostgreSQL, or your own object storage, in open formats. Nothing is held hostage in a proprietary store, so your data is never locked in.

• Bring your own warehouse. Use the cloud data platform you already have, or start one with us.
• Open table formats. Agents write CSV, Parquet, Delta Lake, or Apache Iceberg directly to Amazon S3 or Azure Data Lake Storage Gen2.
• Your compute, your control. dbdeux runs dbt in your warehouse, so models and results live where your team and your BI tools already work.
• Usage-based pricing. Pay for the data you sync and the work you run, not for idle capacity.

Built for operational data, not just SaaS apps

Generic ELT tools treat a POS system or a payroll platform like any other API. DLH is built around the systems operational businesses actually run on, so the hard parts are already solved.

• 100+ maintained connectors with deep coverage of POS (Toast, Aloha, Brink, Square, Lightspeed, Simphony), HR and payroll (Dayforce, Workday, Paycor, Gusto), ERP and finance (NetSuite, Oracle, SAP Business One, QuickBooks), and the databases behind them.
• Change data capture and incremental syncs, with historical re-sync for a whole source or a single entity when you need it.
• Pre-built data models and analytics packages, so your first useful dashboard is days away, not quarters.
• Multi-location by design. Consolidate hundreds of stores, plants, brands, or franchisees into one consistent model.

Hybrid by default, with no inbound ports

Some systems should never be exposed to the internet. DLH agents are lightweight services installed next to the source, on premises, in a private cloud, or on a locked-down VM.

• SQL Server and Oracle Agent. Replicates tables with full loads, Change Tracking, or Change Data Capture, chosen automatically per table, with schema drift handling, SCD Type 2 history, and column masking.
• Aloha POS Agent. Collects back-office data from every Aloha store and consolidates it daily or intraday.
• Outbound only. Credentials stay inside your network, and data is pushed out to your own storage and warehouse.
• Centrally managed. Every agent run reports to DLH, so you get run history, missed-run detection, and alerts in one place.

Managed dbt with dbdeux

dbdeux is the managed dbt platform. Teams build in a browser-based IDE, review every pull request with Slimmer CI and AI review, and schedule state-aware runs that skip models whose results would not change. Cost insights show what every job, pull request, and model costs in your warehouse. Moving from dbt Cloud is a guided import, and dbt 2.0 can run alongside dbt Core one job at a time.

Governed and AI-ready

Data is only useful when people agree on what it means. DLH gives every team one catalog of tables, columns, owners, and lineage, and one governed definition for every metric.

• Catalog and semantic layer. Definitions live in Git, publish as pinned versions, and serve the same numbers to the app, to BI tools over Arrow Flight SQL, and to scripts through the API.
• Data products and share links. Package models and metrics with owners and SLAs, and share a read-only catalog with stakeholders who do not have a login.
• Grounded AI. The Atlas co-pilot reads your real schema and models, and any MCP assistant, such as Claude or Cursor, can explore projects and query governed metrics within the permissions you grant. Every assistant action is recorded in the audit log.

Secure and compliant from day one

Security is built into every layer, not bolted on.

• SOC 2 Type II audited and GDPR compliant.
• Encryption in transit (TLS 1.2+) and at rest (AES-256), with encrypted credential stores.
• Identity and access through SSO (Google Workspace, Okta, Entra ID), role-based access, scoped service accounts, and audit logs.
• Network controls with static egress IPs for allowlisting, SSH tunnels, and outbound-only agents.

Who uses DLH and why

Multi-location operators: restaurants, retail, hospitality, and franchise groups

Operators want one answer to "how did we do yesterday?" across every location, brand, and system. They do not want to export spreadsheets from five POS and payroll tools, and they do not have time to build a data team before they get answers.

Why they build on DLH

• POS, labor, payroll, and back-office data from every location in one model
• The Aloha POS Agent and native POS connectors cover even on-premises store systems
• Pre-built models and dashboards deliver value in days, not quarters
• Daily or intraday refreshes match how operations actually run
• One platform scales from ten locations to thousands without re-architecting

Industrial operators: manufacturing and energy (oil and gas)

Plants, field sites, and operations centers run on ERP systems and on-premises SQL Server and Oracle databases that cannot be opened to the internet. These teams need production, maintenance, and financial data in the cloud without weakening their security posture.

Why they build on DLH

• Self-hosted agents extract from SQL Server and Oracle with no inbound ports
• Change data capture keeps the cloud copy current without heavy load on production systems
• Open table formats (Delta Lake, Iceberg) in your own S3 or Azure storage keep data portable
• Consolidated, multi-site models give leadership one view across plants, wells, and regions
• A practical path to retire legacy databases and heavyweight CDC tools on your own timeline

Data and analytics engineering teams

Analytics engineers want to ship reliable models quickly without running infrastructure for dbt, CI, scheduling, and documentation. They also want their warehouse bill to stay predictable.

Why they build on DLH

• dbdeux provides a managed IDE, CI, scheduling, and catalog for dbt in one place
• State-aware runs and cost insights cut wasted warehouse spend
• Works with the warehouse and Git provider the team already uses
• Guided migration from dbt Cloud keeps existing projects, environments, and jobs
• Atlas AI and MCP access speed up development without giving up control

Finance, HR, and operations leaders

Leaders need numbers that reconcile across departments and answers they can trust without filing a ticket with the data team.

Why they choose DLH

• One governed definition for every metric, from revenue to labor cost
• Pre-built analytics for HR, payroll, and finance systems such as Dayforce
• Dashboards and BI tools that all read the same semantic layer
• AI assistants that answer from governed metrics, not guesses

Software companies and partners

Product teams want to offer customers real analytics inside their own application without building a dashboard engine from scratch.

Why they build with Bideux

• Customizable dashboards that render inside your own UI
• Dashboards defined as code, querying your warehouse directly
• End users can edit layouts and export to CSV, XLSX, PDF, PPTX, or PNG
• AI can propose dashboards from a prompt

How it works: the DLH platform architecture

The DLH platform is built on one idea: move data once, model it in your warehouse, define it once, and use it everywhere. DLH runs the control plane, which schedules, secures, and monitors every pipeline and job. Your warehouse or lakehouse is the data plane, where your data and models live. Because every layer shares one account, one security model, and one monitoring layer, each product you add works with the others from day one.

  SOURCES                     MOVE                          LAND
  POS, HR and payroll,  --->  DLH Data Sync (cloud)   --->  Your warehouse or lakehouse
  ERP and SaaS apps,          SQL Server & Oracle Agent     Snowflake, Databricks, BigQuery,
  on-prem databases,          Aloha POS Agent               Redshift, Fabric, S3 or ADLS
  files and streams           (agents are outbound only)    (Delta Lake, Iceberg, Parquet)
                                                                       |
                                                                       v
  ACTIVATE                    GOVERN                        MODEL
  Dashboards and Bideux, <--  Catalog, semantic layer, <--  dbdeux, the managed dbt platform,
  BI tools, AI assistants     data products, share links    SQL transformations

  ACROSS EVERY LAYER: SOC 2 Type II security, SSO and RBAC, logs and alerts, audit log, APIs

Each layer is useful on its own. Many teams start with Data Sync or an agent to land their data, then add dbdeux to model it and the semantic layer to govern it. Because the layers share one platform, there is no new vendor, contract, or security review each time you add the next one.

Get started

Questions along the way? Talk to our team or browse the FAQ.