ETL, pipeline and migration testing

SQACE tests whether data processing delivers the correct result.

It does not crash. It returns wrong numbers that look plausible. From your business rules, SQACE computes the expected result as a second, rule-based calculation and compares it with what your pipeline actually produced.

Request a demo How it works
RUN KESt-Q4-EXAMPLE, on-prem
RUN KESt-Q4-EXAMPLE, on-prem COMPLETED
SOURCE Oracle JDBC, LOCATION On-Prem/EU-Cloud, ACCESS read-only, REST /api/v1/runs
interest_income Expected 12,480.00 Actual 12,480.00 verified
tax_rate Expected 0.2638 Actual 0.2638 verified
tax_amount Expected 3,156.07 Actual 3,292.22 deviation
Rule IF a partial exemption applies, THEN the capital-gains tax is the interest income times the tax rate, reduced by the exemption. In the actual run, the exemption was not applied.

Expected is the second, rule-based calculation. Classified as a calculation-rule deviation in the tax_amount field, tracked across runs.

Run reproducible, versioned, in the audit trail. Security and architecture
Illustrative example, synthetic values
In production since 2020 at:

On premises or EU cloud, no telemetry, full audit trail. Security and architecture

We verify the result, not just whether the data looks good, and not just whether nothing changed.

SQACE

Verifies whether the processing produced the correct business result, through a rule-based expected/actual comparison.

DQ monitoring

Shows whether the data looks plausible. It does not answer whether the processing computed the right result.

Regression testing

Shows whether something changed. It will not catch an error that was in the logic from the start.

DQ monitoring and regression testing stay useful. SQACE adds the question of whether the result is correct in business terms.

Adoption without a big bang

Start small, expand release by release.

You do not have to build a rule set before SQACE delivers value. The entry point is a regression test, everything else grows step by step.

First regression test on day one, with no rule set at all.

  1. 01

    Regression

    Start immediately, no rule set. SQACE compares today's run with the last one and shows every change.

  2. 02

    Rule sets

    Author business rules in the visual builder, without SQL. SQL is available for edge cases.

  3. 03

    Expected/actual

    The expected result as a second, rule-based calculation, set against the actual, deviations classified down to field and rule level.

  4. 04

    Automated

    Grow the ad-hoc run into a scheduled, CI/CD-triggered suite in minutes.

What SQACE does

Five questions that decide your data testing.

Verify the correct result

From your business rules, SQACE computes the expected result as a second, rule-based calculation and finds logic errors that DQ monitoring and regression tests miss.

What gets checked?

Start small, automate fast

Integrated tools for the whole data-testing workflow. Start without SQL, drop to SQL for edge cases, and grow from an ad-hoc check to a scheduled, CI/CD-triggered suite in minutes.

How fast do you start?

Explain deviations and record them defensibly

Deviations are classified down to the field and rule level, explained in business terms and tracked across runs. With an audit trail and versioning in a protected data space.

How do you prove it?

Roll out across teams, license projects not heads

A standardized method organization-wide, licensed per project rather than per head with unlimited users, integrated via REST API, with transparent public pricing.

How does it scale?

Verify independently, especially with AI

What gets checked is the observable result, independent of tool, method and of the AI that built the pipeline.

Why now?

Evidence from banking
In use at:

LBBW has used SQACE as its central platform for data testing since 2020. At Commerzbank, an anti-money-laundering monitoring pipeline is verified fully automatically with SQACE.

Figures from LBBW, documented publicly

40%
less effort in the data-testing lifecycle
50%
less effort to create test cases
up to 90%
shorter test runtime
6
applications in production, scaling toward 70 to 80

At LBBW, SQACE is the central platform for data testing. The figures shown are documented publicly on sqace.io.

LBBW, public reference (Jens Wauer)

Over 20 years of banking-domain depth (FINARIS, formerly RapidRep). Made in Europe, Frankfurt am Main.

For your role

Where you start.

CDO and Head of Data

Defensible evidence for audit and the board, classified and tracked across runs.

Regulatory reporting

Test and QA

Start with regression tests right away, no rule set. Validate ad hoc, reuse, automate.

Release verification

Business and domain experts

Test logic in the visual builder, no SQL, validated against real data.

How it works

IT and Security

An independent verification authority, on premises or EU cloud, with audit trail, permission concept and automatic deletion.

Security and architecture
Why now

AI writes the pipeline. Who checks the result?

More and more processing is built with AI, faster and more error-prone. Syntactically correct code does not mean a logically correct result. SQACE is the independent authority that checks the observable result, outside the stack and the AI that built the pipeline.

Where SQACE fits

See SQACE on your data.

In a demo we show the expected/actual comparison on one of your use cases. Or start with a proof of concept on a single pipeline.

Request a demo See pricing