QEP Engineering Assurance Platform

Engineering assurance,
backed by evidence.

Mclasa QEP continuously analyses your engineering environment, identifies what matters, investigates engineering risk and verifies that changes achieved their intended outcome.

QEP / Engineering Intelligence
Engineering IntelligenceProduct screenshot area
Designed for genuine QEP product imagery — no simulated customer data.
Deterministic where possibleAI where it adds valueEvidence you can trace

The assurance lifecycle

From repository to verified outcome.

A continuous, governed path from engineering signal to release decision.

01

Understand

Build a living view of repositories, systems and engineering context.

02

Detect

Continuously examine the signals that reveal engineering risk.

03

Investigate

Trace what was observed, why it matters and what the evidence proves.

04

Act

Turn governed findings into engineering work without losing their provenance.

05

Verify

Produce fresh evidence that the intended engineering outcome was achieved.

06

Release

Bring available evidence together to support an informed decision.

Why QEP exists

Your engineering evidence is everywhere. Your assurance should not be.

Source control, CI/CD, work tracking, security, cloud, observability and test systems each hold part of the truth. QEP creates a governed assurance layer across that environment—without demanding wholesale replacement.

Source & architectureTesting & reliabilitySecurity & dependenciesAPIs & configurationObservabilityBusiness context

Repository intelligence

See the estate. Understand the risk.

Deterministic analysers examine architecture, testing, dependencies, APIs, security, reliability, observability, documentation and configuration—turning scattered signals into evidence with context.

  • Know where attention is required
  • Connect technical signals to business criticality
  • Treat absent evidence as unknown, never healthy
QEP / Repository Intelligence
Repository IntelligenceProduct screenshot area

Investigation

Move from signal to understanding.

QEP / Quality Findings
Quality FindingsProduct screenshot area

Quality Findings preserve what was observed and why it became a finding. Optional AI-assisted investigations can help go deeper while keeping provenance visible and engineering judgement in control.

What was observed?What evidence proves it?What should happen next?

A foundational principle

Deterministic where possible. AI where it adds value.

Deterministic evidence remains foundational. AI is optional and supports investigation—it does not replace engineering judgement or manufacture certainty where evidence does not exist.

Verification

Finding something is not enough.

QEP separates the original, immutable evidence from the engineering response. Verification produces new evidence to show whether the intended outcome was actually achieved—not whether a ticket was simply moved to done.

  • Preserve the original evidence
  • Keep response and outcome distinct
  • Support informed release decisions
QEP / Verification
VerificationProduct screenshot area

Built for the environment you have

Evidence into work. Context intact.

QEP is designed to connect with source repositories, CI/CD, cloud engineering systems and issue workflows. Projects can support native work management and evidence-driven engineering improvement without losing the source finding.

Engineering systemsQEP assurance layerGoverned workVerified outcome

Built for engineering leaders

Release with confidence. Every time.

QEP reduces uncertainty by providing continuous, evidence-backed assurance across the software lifecycle.

  • See the engineering truth, not just the metrics
  • Focus attention where evidence shows it matters
  • Prove outcomes instead of assuming them

CTO & VP Engineering

See risk across the estate and make traceable decisions.

Engineering & Quality leaders

Apply a consistent evidence and verification model.

Platform Engineering

Prioritise engineering improvement with context intact.

DevSecOps

Connect security signals to governed engineering outcomes.

Security and trust

Source code is sensitive. The platform is designed accordingly.

QEP’s trust model centres on minimised access, customer boundaries, evidence provenance and optional AI. We describe current and planned controls precisely as the platform evolves.

Explore our security approach

Engineering assurance, backed by evidence

See Mclasa QEP in action.

Explore how evidence moves from engineering signal to verified outcome.

Request a demo