HANECSReguFrame

HANECS / EMBEDDED ASSURANCE

Regulation becomes a manageable engineering process.

ReguFrame connects the CRA, EU AI Act and embedded engineering — accessible for SMEs and robust enough for technical evidence.

CRA / AI Act QuickCheck ↗ SME readiness check ↗ Explore the tool suite ↓

No new compliance team required. Start with what you already have.

ASSURANCE MAP / 01SYSTEM OVERVIEW
01CompassScope & classificationCRA · AI Act
02EvidenceConnect evidenceReq · Code · Test
03SentinelSystem in operationModel · Sensor · Edge
04LifecycleBeyond the releaseSBOM · CVE · OTA
REGUFRAMECONTINUOUS ASSURANCE
evidence ready 84%
ALERT / PHP2SHELL · 26 OCT 2026

Two critical PHP vulnerabilities. Is your website affected?

CVE-2026-109618 and CVE-2026-109619: understand the advisory, check public PHP indicators and identify the next steps.

Start the PHP security check
Built for the real world CRAEU AI ACTISO 26262ISO 21434UNECE R155/R156
LIVE / PRODUCT SCOPE NAVIGATORCRA · EU AI ACT

NO LOGIN / FIRST ORIENTATION

What applies to
your product?

Select your product type and the properties that apply. ReguFrame turns this into an initial view of the CRA, EU AI Act and the evidence to prepare next.

01Select a product type
PRODUCT SCOPE / LIVE CONFIGURATION GUIDED
02Which properties apply?
CRA / DIGITAL PRODUCT
EU AI ACT / AI SIGNAL
03 / INITIAL ORIENTATIONCRA scope likely — verify
CRA · verifyAI Act · no AI signal

Your profile indicates a digital product with lifecycle responsibilities. Start by connecting the product profile, components and support period.

  • Prepare the cybersecurity risk assessment
  • Connect the SBOM and vulnerability process

Orientation based on your selection — not legal advice or a final conformity assessment.

CONCEPT UI / REGUFRAME WORKSPACEFROM SCOPE TO EVIDENCE

EXAMPLE PRODUCT VIEW

Turn answers
into a system view.

A possible view of the future ReguFrame workspace: one shared perspective on the product profile, regulatory scope, technical evidence and the ongoing lifecycle.

CONCEPT UI

Illustrative product view — not a live dashboard or a final conformity assessment.

01 / THE STARTING POINTCOMPLIANCE SHOULD FEEL LIKE ENGINEERING

No compliance team?
No problem.

Your team builds products, not binders. ReguFrame translates regulatory requirements into the language, processes and artefacts your engineering team already uses.

01

Unclear scope

Does the CRA apply to our device? Is our AI application high-risk? The first question should not require a legal research project.

SCOPE CLARITY
02

Scattered evidence

Requirements, code, tests, the SBOM and model documentation live in different places. Their relationship gets lost.

TRACEABILITY
03

Open lifecycle

A release is not the end. Vulnerabilities, updates, support periods and field monitoring need a process.

CONTINUOUS ASSURANCE
02 / THE TOOL SUITEFROM FIRMWARE COMMIT TO FIELD EVIDENCE

Four modules.
One continuous thread.

ReguFrame does not replace your toolchain. It connects what already exists and turns it into a traceable assurance case.

01◌

ReguFrame Compass

Product profile, scope and risk class — through clear questions instead of legal clauses.

  • Check CRA relevance
  • Classify the AI Act category
  • Prioritise next steps
START HERE ↗
02⊙

ReguFrame Evidence

Capture technical evidence where it is created — in the engineering process.

  • Requirements ↔ Code ↔ Test
  • Connect the SBOM and model card
  • Export the evidence pack
MAKE IT TRACEABLE ↗
03⌁

ReguFrame Sentinel

Runtime assurance for sensors, models and safety-relevant edge systems.

  • Sensor and model health
  • Detect drift and anomalies
  • Make fallbacks traceable
WATCH THE EDGE ↗
04↻

ReguFrame Lifecycle

Security and compliance responsibilities continue after release.

  • Keep CVEs, VEX and the SBOM in view
  • Manage the support period
  • Updates and field evidence
KEEP IT ASSURED ↗
03 / HOW IT FEELSCOMPLIANCE COMPASS / CONCEPT DEMO

THREE QUESTIONS TO A CLEARER START

The first answer
is not an expert opinion.

An SME needs orientation first: what applies to us, which artefacts do we already have, and which next step moves us forward?

PRODUCT PROFILE GUIDED

What does your company develop?

INITIAL ORIENTATIONCRA likely relevant
↗

Next step: gather the product profile, component list and planned support period.

Technical first assessment, not legal advice. The manufacturer remains responsible for the final conformity assessment.

04 / BUILT FOR SMESLOW FRICTION / HIGH SIGNAL

No big-bang project.
A better next step.

ReguFrame is built for the reality of smaller product teams: limited capacity, established processes, real deliveries and no time for another abstract system.

01

Plain language first

No legal matrix as the starting point. Begin with a clear question, then build defensible evidence.

02

Use what you have

Git, tickets, tests, SBOMs and existing safety artefacts become the starting point.

03

Evidence, not paperwork

Every claim gets a source, an owner and a status — from commit to release.

04

Engineering-grade privacy

Designed for sensitive product data: clear data flows, on-premises options and HANECS embedded expertise.

05 / WHY NOWTHE CLOCK IS ALREADY RUNNING

The deadlines are running.
The time to get oriented is now.

The best time for compliance is not the final month before market launch. ReguFrame makes the first step small enough to start today.

11.09.2026
CRA reportingReporting of actively exploited vulnerabilities and severe incidents.
11.12.2027
CRA main obligationsCybersecurity requirements across planning, development and maintenance.
02.08.2028
AI Act / regulated productsRules for high-risk AI in regulated physical products.

Timeline last reviewed on 12 October 2026 using European Commission publications. Other AI Act obligations already apply; the product deadline does not cover every AI system. CRA timeline ↗ · AI Act ↗

NEXT STEP / 30 MINUTES

Start with
your reality.

One product. One component list. One shared view of what already exists — and what matters next.

Request a readiness check ↗