How are AI-built apps doing in Germany, Austria and Switzerland?

The radar measures what is discoverable: apps in builder directories, on builder subdomains (such as *.lovable.app or *.bolt.host) and with a recognisable builder fingerprint, supplemented by certificate transparency logs and the Common Crawl index. Apps on their own domain without markers are under-represented. The correct reading is therefore “x% of the n discoverable apps with a DACH connection”, never “x% of German Lovable apps”. Attribution to DE, AT or CH happens after the scan via domain ending and legal findings; whatever cannot be attributed counts as not attributable and serves as a control group.

The scan is passive and browser-equivalent: it loads what any browser loads when opening the site, clicks nothing, fills in no form and creates no account. The user agent names us and this page, and robots.txt is respected — anyone who excludes us there is skipped.

Only shares over groups of at least 20 apps are published. No hostname, no URL, no screenshot and no finding attributable to a single site. Internally the raw data carries a hash that never leaves the database; the target list expires 90 days after the last scan.

Before every publication the field sweep runs against a control group of well-maintained professional sites — any severe hit there is a false-alarm candidate. The last sweep (24 August 2026) found five errors in platform detection; all are fixed. The false-alarm estimate per rule is stated in the quarterly report. The numbers here are shares over a sample, not proof about any individual app.

If you do not want your domain in the radar, remove it: prove control via DNS TXT, file or meta tag — we then delete all observations and the target and exclude the domain from every future run. Without DNS access, an email is enough.