Skip to content
Trust Quality AssuranceManufacturing Intelligence

About us

Built by quality engineers who got tired of exporting spreadsheets

Trust Quality Assurance was founded by people who ran plant quality functions and spent their evenings reconciling data from three systems to answer one question. The product is the tool we wanted then, built to the standard an auditor would accept.

countries in production
14
production lines connected
180+
offices
4
cloud regions (EU, US, APAC)
3

Mission

Make quality drift visible while it can still be corrected, in every plant, on every shift — and make the evidence of control available the moment someone asks for it.

Vision

A manufacturing industry where quality decisions are made from live, shared data rather than from end-of-shift reports and institutional memory.

How we operate

Four commitments we are willing to be held to

These are the rules we apply when a commercial incentive and an engineering judgement disagree.

Measurement before opinion

We record a baseline before changing anything and report against it, including when the result is smaller than the customer hoped.

Engineering over marketing

Product claims are written by the engineers who built the feature. If a capability has limits, the documentation states them.

Customer data is not our asset

Process parameters, recipes and images stay inside the customer tenant. No cross-customer model training, ever.

Say no to bad pilots

If the data or the process discipline is not there yet, we say so and propose what to fix first rather than selling a deployment that will fail.

Leadership

Manufacturing background first, software second

Every member of the leadership team has either run a quality function or built industrial data infrastructure at scale.

AB

Dr. Annika Brandt

Chief Executive Officer

Twelve years in automotive quality management, including plant quality director for a tier 1 supplier across four European sites. PhD in production engineering.

Focus: Customer outcomes, enterprise agreements

MS

Marek Sowiński

Chief Technology Officer

Built industrial data platforms for battery and semiconductor manufacturers. Previously principal engineer on a high-throughput historian and analytics stack.

Focus: Architecture, edge and platform reliability

PR

Dr. Priya Raman

VP Applied AI

Computer vision and anomaly detection in industrial inspection. Led model governance for a regulated medical device programme.

Focus: Model quality, explainability, governance

TL

Thomas Lindqvist

VP Engineering

Distributed systems and platform engineering. Scaled a multi-tenant industrial SaaS platform from single-site pilots to global deployment.

Focus: Delivery, developer experience, quality of the codebase

EM

Elena Marchetti

VP Customer Success & Solutions

Quality engineer turned solution architect; ran multi-plant QMS rollouts in electronics and medical devices before joining.

Focus: Deployment, adoption, measured value

DO

David Okonjo

VP Security & Compliance

Information security leadership in regulated manufacturing, including SOC 2 and ISO 27001 programme ownership and validated-system change control.

Focus: Security programme, validation, customer review

Engineering culture

How the product actually gets built

Manufacturing customers run our software for a decade. That constraint shapes how we write, review and release it.

Engineers who have stood on a line

Solution architects and product engineers spend time on customer shop floors every quarter. Feature decisions are argued with plant evidence, not personas.

Trunk-based, reviewed, reversible

Small changes, mandatory review, feature flags and staged rollout. Validated tenants are pinned and updated only inside agreed windows.

Documentation is part of the change

A feature is not done until the documentation and the API reference describe it, including its limits and failure behaviour.

Support is staffed by engineers

Technical questions reach someone who can read the code. There is no scripted first line between a customer engineer and ours.

Technology stack

Chosen for uptime on plant hardware, not for novelty

The same build artefacts run in managed cloud, in a customer's own subscription and inside an air-gapped plant network.

Edge

  • Rust and Go services
  • OPC UA / MQTT clients
  • ONNX runtime for on-edge inference
  • Containerised, signed releases

Chosen for predictable memory use and long uptime on plant hardware.

Data

  • Columnar time-series storage
  • Append-only event log
  • Graph traversal for genealogy
  • Versioned master data

Sub-second query on hot partitions with retention measured in years, not weeks.

Intelligence

  • Python model services
  • Gradient-boosted and sequence models
  • Computer vision (CNN / transformer)
  • Model registry with lineage

Every released model is versioned, monitored for drift and reversible.

Application & platform

  • TypeScript and React
  • Kubernetes on regional cloud
  • OpenTelemetry observability
  • Infrastructure as code

The same artefacts deploy to managed cloud, private cloud and air-gapped sites.

Quality commitment

We are held to the standards we sell

It would be difficult to argue for measured process control while running an unmeasured engineering organisation. These are our own operating numbers.

monthly availability SLA
99.95%
third-party penetration test
Annual
minimum API version support
24 mo
features documented at release
100%

Release discipline

Every release ships with documentation, API reference updates and regression evidence. Validated tenants are pinned and updated only in agreed windows.

Incident transparency

Customer-impacting incidents get a written post-incident review with timeline, cause and corrective action — the same standard we ask of suppliers.

Customer advisory group

Quality leaders from six sectors review the roadmap quarterly. Features that no plant will operate do not get built.

Global presence

Local engineering where the plants are

Deployment support is delivered in the customer's time zone. Data residency follows the region, not the office.

Stuttgart

Germany

Headquarters · engineering, solutions

Coverage: DACH, Northern and Southern Europe

Detroit

United States

Americas customer engineering

Coverage: North America, Mexico

Singapore

Singapore

APAC solutions and support

Coverage: Southeast Asia, Japan, Korea

Kraków

Poland

Platform engineering

Coverage: Global engineering delivery

Start the evaluation

Find out where quality drift is hiding in your plant.

Bring one line, one defect family or one audit workflow. We will map the available data sources, quantify the cost of the current detection delay, and show the fastest route to measurable control.

  • 45-minute technical walkthrough

    With a solution architect who knows manufacturing data, not a scripted demo.

  • NDA before any data review

    We can assess feasibility from sample exports without production access.

  • Written pilot scope

    Baseline metrics, success criteria and exit conditions agreed up front.