Shipmark / Guides

Companion apps for connected devices under the CRA: what counts as the product

Updated 17 November 2026 · 8 min read · Based on Regulation (EU) 2024/2847 and the Commission guidance of 27 July 2026

Short answer: the companion app is covered, and so is the manufacturer's cloud behind it.

  • An app installed on the user's phone is software supplied to the user, so it is a product with digital elements when it is made available in the EU in the course of a commercial activity.
  • A product with digital elements includes its "remote data processing solutions" (Article 3(1)). The cloud service that lets the app control the device is one when it passes a three-part test.
  • The manufacturer is whoever markets the product under its own name or trademark (Article 3(13)), not whoever wrote the code.
  • That company carries the obligations for the app and the backend together: risk assessment, third-party component due diligence, vulnerability handling and reporting.

The setup this guide is about

A company sells a connected device, such as a thermostat, a smart lock, a wearable or a toy. Users control it from an app, and the app talks to a cloud service that the company built or had built. Three things can be in scope: the device and its firmware, the app, and the backend. Teams often treat them as three separate projects with three separate owners. The CRA does not.

1. The app is a product with digital elements

The Cyber Resilience Act (Regulation (EU) 2024/2847) applies to products with digital elements made available on the market whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network (Article 2(1)). A companion app exists to connect to a device and a service, so that condition is met almost by definition.

Article 3(1) defines a product with digital elements as "a software or hardware product and its remote data processing solutions", including software or hardware components placed on the market separately. According to the Commission guidance, software that is provided to and run on the user's side, such as an app downloaded from a store, is a product with digital elements, while a service used only through a browser is not on that basis alone. For the wider picture see does the CRA apply to mobile apps?

"Made available" means supplied for distribution or use in the course of a commercial activity, "whether in return for payment or free of charge" (Article 3(22)). A companion app is usually free to download, but it supports a product that is sold, so the commercial context is normally obvious.

2. The cloud behind the app: the three-part test

Article 3(2) defines remote data processing as data processing at a distance for which the software is designed and developed by the manufacturer, or under the responsibility of the manufacturer, and the absence of which would prevent the product from performing one of its functions. The Commission guidance turns this into three cumulative questions:

  1. Does the processing happen at a distance?
  2. Would the product be unable to perform one of its functions without it?
  3. Was the software designed and developed by the manufacturer, or under its responsibility?

Recitals 11 and 12 give the two cases that matter here. If a mobile app needs an API or database from a service built by the manufacturer, that service is a remote data processing solution (recital 11). Cloud-enabled features from the manufacturer that let users control a device remotely, such as smart home devices, are within scope because they are part of how the product works (recital 12).

SituationPosition under the guidance
The manufacturer's own cloud service for onboarding and configuration of the deviceLikely part of the product
The manufacturer's over-the-air update serviceSame reasoning: likely part of the product
The manufacturer's own application running on rented infrastructure (IaaS or PaaS)Can still be remote data processing: who operates the servers is not the deciding factor
Generic third-party storage or SaaS the manufacturer did not developNormally not remote data processing, but a dependency to assess
The Wi-Fi or cellular link itselfA communication channel, not automatically remote data processing
Back-end systems that do not interact with the product (CRM, HR tools)Not remote data processing
A manual alternative to a remote function (a physical switch)Does not automatically take the remote function out of the analysis

These rows summarise the guidance as reported by law firms and independent guides, and the examples in it are fictional archetypes. Check the text of the guidance for your own case. Note also that commentators describe the guidance as approved but dependent on formal adoption in all languages, so confirm its current status on the Commission's page.

3. Who is the manufacturer?

Article 3(13) defines the manufacturer as a person who develops or manufactures products with digital elements, or has them designed, developed or manufactured, and markets them under its own name or trademark, whether for payment, monetisation or free of charge. A device brand that commissions an agency to build the app, and publishes it under the brand's name in the stores, is the manufacturer of that app. The agency is a supplier, unless it also markets the app under its own name. The longer version of this question is in agency or client: who is the manufacturer?

The same applies to the backend. If the brand had it built by a contractor, it was developed "under the responsibility of the manufacturer", and the second and third conditions of the test above are met.

4. One product or two?

The sources I read do not say whether a device and its companion app are one product or two for conformity purposes. What the text does establish is narrower: Article 3(1) says software or hardware components placed on the market separately are products with digital elements, and the guidance says modules with their own functionality that can be bought or subscribed to separately are standalone products. An app that is distributed through an app store separately from the device may therefore need its own analysis. Treat this as an open point: decide it deliberately for each product line, write the reasoning into the technical documentation, and revisit it when the guidance is formally adopted or updated.

5. What this means for the app team

Because the manufacturer's obligations attach to the product and its remote data processing solutions together, an app team should not scope its CRA work at the app alone.

ObligationWhat to include for a companion app
Risk assessment (Article 13(2))The app, the backend functions it depends on, the device link and the data flows between them. See the risk assessment template.
Third-party components (Article 13(5), 13(6))Due diligence on SDKs and libraries in the app and on third-party services the backend uses. A vulnerability found in a component must be reported to whoever maintains it.
Vulnerability handling (Article 13(8))Vulnerabilities of the product, including its components, must be handled effectively for the support period. A backend flaw is a product flaw.
Reporting (Article 14)Actively exploited vulnerabilities in the product must be notified within 24 hours (early warning), 72 hours (notification) and 14 days after a fix is available (final report). In our reading, an exploited flaw in the manufacturer's own cloud is within that duty, because the backend is part of the product. See the reporting guide.
Support periodOne period per product version, covering the app and the services it needs. See the support period guide.

A practical way to start is the one-page map per remote function that SCHUTZWERK recommends: what the device does without it, who is responsible for the software, which data flows through it, which dependencies it has, and where its documentation is kept. A short list of the app's remote functions (pairing, firmware update, remote control, history sync) gets you most of the way.

Start with the dependencies: see what is inside your companion app and whether any component has known vulnerabilities.

Open the free scanner

Questions teams ask

Is a companion app covered if it is free? A price is not required. Article 3(22) covers supply "in the course of a commercial activity, whether in return for payment or free of charge", and the app supports a product that is sold.

Is our cloud API covered if it runs on a hyperscaler? It can be. The guidance says the operator of the servers is not the deciding factor. The test is whether you designed and developed the software, or had it developed under your responsibility, and whether a product function depends on it.

Is the third-party service we use for push notifications or storage covered? Generic third-party services you did not develop are normally not your remote data processing solution. They remain dependencies that your risk assessment and Article 13(5) due diligence must cover.

Sources

This guide summarises EU law and non-binding Commission guidance for practical use. It is not legal advice. Related: Does the CRA apply to mobile apps? · Who is the manufacturer? · CRA risk assessment template · CRA vulnerability reporting · The CRA support period.