Shipmark / News

PWA or native app: does shipping a web app get you out of the CRA?

· 5 min read · CRA news

A smartphone lying on a work desk next to a laptop keyboard, a plant and sheets of paper
Photo: Grabster on Unsplash

In short: the CRA regulates products you place on the market, not services people use over a network, so a browser-only web app is generally outside it and an installable app is not. That line is deliberate, and it is not a free pass.

  • This is an analysis piece. The question was raised in a 20 October 2026 article by cyberresilienceact.eu; it builds on the Commission's CRA guidance of 27 July 2026.
  • Remote-only software such as most websites is generally out of scope, per a law-firm summary of that guidance. Software running on the user's device is in scope.
  • A backend can still be pulled in if the app cannot work without it and you built it for that app.
  • Choosing a PWA only to avoid the CRA may leave you outside both the CRA and NIS2, but not outside the GDPR or your customers' security questionnaires.

The question

On 20 October 2026 cyberresilienceact.eu answered a reader who had noticed something odd: the same codebase, API and data flows fall under the Cyber Resilience Act if they are wrapped for an app store, but seemingly not if they are served as a progressive web app (PWA) in a browser. Does the CRA reward web-only deployment? The technical reading is right, the article says, but the distinction is intended. We checked that reading against the regulation and the Commission's guidance.

What the law says

The CRA, Regulation (EU) 2024/2847, applies to "products with digital elements". Article 3(1) defines that as a software or hardware product and its remote data processing solutions. Article 3(2) defines remote data processing as processing at a distance for which the software is designed and developed by the manufacturer, and without which the product could not perform one of its functions.

Recital 12 adds the limits. Cloud solutions count only if they meet that definition. Cloud features that let users control a product remotely are in scope. Websites that do not support a product's functionality, and cloud services outside the manufacturer's responsibility, are out. Cloud computing services themselves, including SaaS, fall under NIS2 (Directive (EU) 2022/2555) for medium-sized and larger entities.

What the Commission's guidance adds

The Commission published its first implementation guidance on 27 July 2026 (communication C(2026) 5252). It is non-binding and, per the Commission, covers the scope of remote data processing solutions, among other topics. The Commission's announcement does not spell out the web-app rules, so we relied on the law firm LexGO's summary of the guidance, dated 11 September 2026. According to LexGO, the guidance says remote-only software, such as most websites and web applications, is generally outside the scope, unless it supports an in-scope product through remote data processing. Software that runs locally is in scope, which LexGO says includes browser extensions and locally installed web apps. The guidance annex itself would not load as text in our run, so we have not read those passages first-hand.

How it plays out for app teams

What you shipOur reading
Native iOS or Android appIn scope: it runs on the user's device and you place it on the market.
Backend built only for that app and needed for its functionsIn scope as a remote data processing solution of the app (Article 3(2)).
Web app used only in a browser, nothing installedGenerally outside the CRA, per the guidance as summarised by LexGO.
PWA that users install to the home screenUnclear. The summary names "locally installed web apps" as in scope, but we have not seen how the guidance treats a PWA installed from a browser. Treat it as at risk.
Marketing websiteOutside, if it does not support a product's functionality (recital 12).

The last-but-one row is our own caution, not a finding. If you offer an install button, assume the installed build may count as a product.

Why this is not a loophole to build on

What we would do

  1. Decide the delivery model on product grounds, not on regulatory ones.
  2. If any build is installed on a device, run it through a scope check and plan for the CRA now. Reporting of actively exploited vulnerabilities has applied since 11 September 2026; most other obligations apply from 11 December 2027.
  3. List which backend services each installable app needs to work. Those are the ones most likely to count with it.
  4. For a web-only product, write down why you concluded it is out of scope, and check NIS2 and the GDPR separately.
  5. Keep the basics regardless: an SBOM, a security contact and a way to ship fixes. The security work is the same, the CRA mostly makes you write it down.

Not sure which of your apps and services are in scope? Answer six questions and get a reasoned result.

Does the CRA apply to my app?

Sources

This is an analysis based on a non-binding Commission guidance, a secondary summary of it and the text of the regulation. Facts about the guidance are as reported by those sources. It is not legal advice. Related: Does the CRA apply to mobile apps? · CRA timeline for app teams