SQACE SQACE

Test ETL, migrations and reporting

Data processing rarely crashes. It delivers wrong results that look plausible.

SQACE verifies, through rule-based expected-vs-actual comparison, whether pipelines, ETL and migrations compute correctly. It checks the result, not just whether the data looks healthy.

In production at LBBW and Commerzbank.

Verification run · capital-gains tax Deviation

What the pipeline returned

€3,292.22 looks plausible

What the rule expects

€3,156.07 rule-based, verified

Difference €136.15, classified as a calculation-rule deviation in field kest_betrag.

The rule

If a partial exemption applies, capital-gains tax is the capital gain times the tax rate, less the exemption. In the actual run the exemption was not applied.

Illustrative example, synthetic values.

In production since 2020 at
On-premise or EU cloud, no telemetry

Evidence

Proof, not claims.

Every figure names its source and links to the full case. Coverage and effort stay reported separately.

15,847 records

A capital-gains-tax calculation, verified fully automatically.

Expected result computed from rules, one deviation found and classified.

Method: expected-vs-actual See the run

6 → 70–80 applications

LBBW is rolling out independent verification broadly.

Publicly documented reference on sqace.io.

Source: LBBW See the reference

At Commerzbank, an anti-money-laundering monitoring pipeline is verified fully automatically.

A cleared banking reference.

Source: Commerzbank See the case

≈ 80 % coverage

Around 80 % of data processing can be covered with the rule-based approach.

An honest scope statement, not an effort figure.

Method: scope, not effort How that works

The product

See the verification run, not just the promise.

The rule is built in the visual editor, without SQL. The run checks record by record and records every deviation.

SQACE · Mission: KESt-Q4
On-premise
Easy Query Rule set Expected/Actual Run

Rule set · capital-gains tax

  • IF a partial exemption applies
  • THEN capital-gains tax = capital gain × tax rate − exemption
  • ELSE capital-gains tax = capital gain × tax rate

Assembled visually in the rule editor, without SQL. SQL is available for edge cases.

Latest run

15,847 records checked

One deviation, classified as a calculation-rule deviation in field kest_betrag.

Illustrative example, synthetic values.

Adoption without a big bang

Start small, expand release by release.

You do not need a rule framework before SQACE pays off. Verification grows step by step.

A first regression test on day one, with no rule framework.

  1. Regression

    Compare today's run against the last. Every change becomes visible, with no rule framework.

  2. Rule sets

    Capture business rules in the visual editor and validate them on real data. Without SQL.

  3. Expected/Actual

    Set the expected result, a second rule-based calculation, against the actual and classify deviations.

  4. Automated

    Run it as a scheduled, CI/CD-triggered suite and track it across runs.

For your role

Three roles, three proofs.

Sponsor, champion and gatekeeper each find the proof that answers their question.

CDO and Head of Data

Defensible proof for audit and the board, not just dashboards.

At LBBW, independent verification grows from 6 to 70–80 applications, with deviations tracked across runs.

See the evidence

Head of Test / QA

A fast start, without months of setup.

Begin with regression tests on day one, no rule framework, then expand functional verification release by release.

How it works

CISO and compliance

No new risk from new data access.

On-premise or EU cloud, no telemetry, audit trail, versioning and automatic deletion. Built in, not bolted on.

To the trust center

Data sovereignty

Auditable, sovereign, operated in Frankfurt.

An independent verification instance must not create new risk. SQACE is built so your data space stays under your control.

On-premise or EU cloud

SQACE runs in your environment or a European cloud. Your data never leaves your space.

No telemetry

No usage or content data flows out, by architecture.

Audit trail

Every run is reproducible, versioned and traceable in the audit trail.

Permissions

A role and permission model down to object level, with physically separated data spaces.

Automatic deletion

Configure retention periods; data is deleted automatically afterwards.

Made in Europe

Built and operated by FINARIS in Frankfurt am Main.

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 functionally correct result. SQACE checks the observable result, independent of the tool and of the AI that built the pipeline.

How SQACE checks

Origin

Over 20 years of banking-domain depth.

SQACE comes from FINARIS, from over 20 years working on data processes in banks (formerly RapidRep). Built and operated in Frankfurt am Main.

20+ years

Banking domain, from FINARIS and its predecessor RapidRep.

Frankfurt

Built and operated on the Main, made in Europe.

Independent

A verification instance outside your pipeline stack.

See SQACE on your data.

In a demo we show the expected-vs-actual comparison on one of your use cases. Or see a full verification run first.