DAXIA Data · the engineering surface

The workbench that reconciles itself.

Used during the data integration window by data engineers and migration consultants. After data is migrated it supports continuous integration. The workflows can be maintained. The complete data platform is already in place. Two pods — Migrate and Business rules — over one backend and one medallion estate. Every run is streamed while it happens and recorded where an auditor can read it.

  1. Raw

    Bronze

    Clean and reshape Bronze in place, or model a table by hand. Moving it onward is a Silver mapping’s job. Every replicated table is reconciled, or marked unverified.

    • Rules
    • Add table
    • JSON transform

  2. Modelled

    Silver

    Model, map and refine inside Silver — design tables, bring Bronze in, clean in place. The rules are SQL you can read, stored with the estate.

    • Add table
    • Silver mapping
    • Rules
    • Compose

  3. Trusted

    Gold

    Map Silver columns onto their Gold targets, ready for Reporting to consume. History is kept as SCD2 behind active-only views, on tamper-evident ledger tables.

    • Gold mapping
    • Add table
    • DAXIA tables

What DAXIA Data does, section by section

Migrate · Connections

A connection is tested before it is saved, and the app never holds a password.

One tenant-wide registry. Nine connection types; three engines can be a Gold source; ADLS deploys and replicates like a database. A connection row carries a secret reference, never the secret. The backend resolves it under its managed identity at the moment it connects. Custom connections are supported. Deploy, replicate, programs and copy require a source; the file importer requires a target. The tag is shown on every row because the server enforces it.

Migrate · Data quality

Column by column, with a word for what was found.

Scan one table interactively, or scan every table on a target and get a workbook — one sheet per table, a Summary, and a Method sheet that explains the count. Scan all enumerates tables through the same allow-list the query surfaces use, so it cannot copy a hidden Gold table into a shared workbook. It is the most expensive button in DAXIA, and rate-limited to three runs an hour. The info button surfaces how the findings are determined.

Migrate · Deploy

Take your schema and data from Source to Bronze.

Streams while it happens. Any error is flagged and explained. Supports copy job activity, so that the run will not stop at a one-time activity — define, schedule and that’s it.

Migrate · Explore data

An object tree, a SQL editor, and an assistant that is ready for your questions.

Ask in plain words and follow up in the same conversation; each answer is a query that runs, with its SQL one click away. The assistant sees only tables the caller may read, every call is logged, and it can be switched off per tenant. No data is ever passed to the assistant. A workbench in two modes — Data operations and Report definition — that open the same editor and run through the same rules. What changes is the framing, not the capability.

Business rules · Model

One semantic model, validated where it is declared.

Relationships, measures, hierarchies, a generated date table and row security, edited in one place. Report Builder’s canvas and this surface edit the same object; there is no second join editor. Time intelligence compiles to window aggregates. YTD, QTD, MTD, running total, prior, delta and moving average are measure functions that compile to SUM(SUM(x)) OVER (…) — legal T-SQL, and how year-to-date is written in SQL Server.

Business rules · Transform

All in one place.

See, explore, define, refine. Bronze is source, nothing more. Silver is yours to rule — transform, manage, add business logic. Gold is your source of truth: reporting derives from here.

Business rules · Transform · Silver mapping

Define Silver based on Bronze or based on your particular needs.

Map Bronze tables to corresponding Silver tables. Run will copy the data. A mapping can be scheduled and run in a pipeline.

Business rules · Transform · Silver rules

Executed always in place, on the tables it refers to.

Transform your data to meet your business needs — this will be taken to Gold.

Business rules · Orchestrate

Take your rules, composes, mappings — you define the order, then schedule on cron.

Every run is logged. Every failed run is properly explained.

Business rules · Semantic pack

Publish a slice of Gold to someone who never signs in.

Name a set of Gold tables, decide who may read them, and hand a report author a URL, a token and a page of Power Query. The author holds no DAXIA role and can reach nothing but the tables the pack names.

The pack’s table list is the allow-list.

The feed authenticates with a pack token, not the product’s front door. Four live checks run on every request — token active, not expired, pack published, holder still a member — so revoking any one cuts access on the next call, with nothing to redeploy.

The token is shown once and never recoverable.

dxsp_ plus 32 random bytes, hashed at rest. It is unique tenant-wide, so one lookup resolves it and the URL slug is checked against the pack that came back — a token cannot be probed against other packs.

One refusal message for every rejection.

An unknown token, an expired one, a retired pack, a removed member and a wrong slug are indistinguishable from outside. A feed that told them apart would be an oracle for pack names.

  • Gold tables
  • Entra group
  • Pack token
  • Power Query handout
  • Publish

The one hard guarantee

Every table you replicate is reconciled, or it is marked unverified.

Three numbers, not two: what the source held, what the writer believes it wrote, and what Bronze actually holds. Which pair disagrees is the whole diagnosis, and all three are stored on the run.

source_rows · copied_rows · target_rows

“We did not check” and “we checked and it matched” are never the same word.

unverified is its own verdict — the honesty rule the audit pack’s not_available follows. A mismatch fails the table; rows are left in place, because the next run reloads from scratch anyway.

Gold cannot be edited.

SCD2 backed by the ledger table preserves all history. An admin can restore any Gold table — through Restore Production — to any point in time its ledger history covers.

After the data integration

DAXIA Reporting

Where every number is defensible.

Explore, build and read on Gold, and keep the books in an ERP where a posted journal is immutable.

  • Explorer
  • Builder
  • Insights
  • Enterprise
  • Financials
  • Group Reporting
See DAXIA Reporting

The Platform

Built to be audited.

The architecture, the security model and what a deployment into your subscription looks like.

  • Medallion
  • Security
  • Deployment
See the platform

Bring a source. We will replicate it in front of you.

Name a system and a few tables. The walkthrough runs the migration window on something that looks like yours, with the person who built it.

Request a walkthrough Read about the platform