---
title: "EU Digital Markets Act compliance: gatekeeper obligations and evidence"
canonical_url: "https://www.sorena.io/artifacts/eu/digital-markets-act/compliance"
source_url: "https://www.sorena.io/artifacts/eu/digital-markets-act/compliance"
author: "Sorena AI"
description: "DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "EU Digital Markets Act"
  - "DMA compliance"
  - "gatekeeper obligations"
  - "core platform service"
  - "Article 11 compliance report"
  - "Article 7 interoperability"
  - "DMA"
  - "gatekeeper compliance"
  - "Article 5"
  - "Article 6"
  - "Article 7"
  - "Article 11"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# EU Digital Markets Act compliance: gatekeeper obligations and evidence

DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk.

*Compliance Guide* *EU DMA*

## EU Digital Markets Act Compliance

A practical DMA compliance guide for designated gatekeepers and teams reviewing core platform service obligations.

Use it to scope listed core platform services, map Articles 5, 6 and 7 obligations, build Article 11 evidence, test anti-circumvention risk, and prepare interoperable access records.

The Digital Markets Act is not a general platform-compliance checklist. It applies to undertakings designated as gatekeepers and to the core platform services listed in the Commission designation decision. Compliance work should therefore start with the designation decision and then trace each listed service through the obligations in Articles 5, 6 and 7, the Article 11 compliance report, the anti-circumvention rule in Article 13, and any Commission specification or enforcement process that affects the service.

## Scope the gatekeeper and the listed core platform service first

A DMA control should be opened only after the team can name the designated undertaking, the listed core platform service, and the business-user or end-user journey affected by the control. The legal text defines core platform services to include online intermediation services, online search engines, online social networking services, video-sharing platform services, number-independent interpersonal communications services, operating systems, web browsers, virtual assistants, cloud computing services, and online advertising services provided by an undertaking that provides one of those services.

The designation analysis also matters after designation. Article 3 uses quantitative presumptions for turnover or market value, Union user reach, and durable position, but the Commission can designate under a qualitative assessment as well. The compliance record should therefore separate designation metrics from service-level obligation evidence.

- Record the exact undertaking and each core platform service listed in the designation decision, not just the corporate group or product family.
- Keep monthly active end-user, yearly active business-user, Member State, turnover, and market-value evidence separate from obligation controls.
- For product changes, state whether the change affects a listed core platform service, a service provided together with or in support of it, or a service outside the designation.
- Use the Commission gatekeepers page and case materials to confirm which services are listed before reusing a DMA control across products.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Defines gatekeepers, core platform services, designation criteria, listed-service scope, and the six-month compliance period after a service is listed.
- [European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Identifies designated gatekeepers, their listed core platform services, case references, compliance reports, acquisition notices, and consumer-profiling reports.

## Map Articles 5, 6 and 7 to concrete product controls

Articles 5, 6 and 7 are the compliance backbone. Article 5 contains direct obligations such as limits on combining or cross-using personal data without consent, anti-steering restrictions, communication and contracting rights for business users, access for end users to externally acquired content, complaint freedom, tying restrictions for identification, browser engine and payment services, and advertising transparency for advertisers and publishers.

Article 6 adds obligations that may be further specified by the Commission. The operational controls typically touch non-public business-user data, uninstall and default-choice flows, third-party app stores and software installation, ranking fairness, switching, interoperability with operating system or virtual assistant features, ad measurement access, end-user data portability, business-user data access, search-data access, FRAND access conditions, and termination terms.

Article 7 is narrower but technically demanding. It applies where a gatekeeper provides a listed number-independent interpersonal communications service and requires requested interoperability for specified basic functionalities while preserving security, including end-to-end encryption where applicable.

- Build an obligation matrix by article, paragraph, listed core platform service, affected user group, product owner, legal owner, technical owner, and evidence owner.
- For Article 5 data-use controls, retain consent-choice records, withdrawal handling, consent-reprompt limits, data-combination rules, and service-by-service processing boundaries.
- For Article 6 controls, retain implementation specs for app installation, default changes, ranking conditions, data-access APIs, portability tools, ad-measurement access, and FRAND access terms.
- For Article 7 controls, retain the reference offer, request intake records, security and privacy justifications, interface specifications, implementation status, and user-choice handling.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Sets out the gatekeeper obligations in Articles 5, 6 and 7 that the compliance matrix must map by listed core platform service.
- [European Commission - DMA legislation](https://digital-markets-act.ec.europa.eu/legislation_en?ref=sorena.io) - Commission legislation page linking the DMA, procedural implementing regulation, templates, notices, and guidelines relevant to obligation interpretation and submissions.

## Prepare Article 11 reports as service-by-service evidence files

Article 11 requires a gatekeeper to provide the Commission, within six months after designation, with a detailed and transparent report describing the measures implemented to ensure compliance with Articles 5, 6 and 7, plus a non-confidential summary. The report and summary must be updated at least annually.

The Commission template makes the evidence burden practical. For each listed core platform service and applicable obligation, it asks for a compliance statement, an exhaustive explanation of measures, supporting data and internal documents, pre-designation or post-designation status, implementation timing, product and geographic scope, technical or engineering changes, customer-journey changes, terms and remuneration changes, consultation, alternative measures considered, testing, indicators, monitoring tools, and access procedures for third parties.

A request for specification dialogue does not remove the reporting obligation for the obligations covered by that request. Teams should therefore keep the Article 11 evidence file current even when they are also discussing specifications with the Commission.

- Create one standalone annex per listed core platform service and applicable Article 5, 6 or 7 obligation.
- Attach raw-data readiness notes for metrics the Commission may request, including definitions and calculation methods.
- Keep click-by-click user journeys, screenshots, recorded demos, A/B test methods, consent rates, survey outputs, and business-user feedback where the measure changes choice screens, consent forms, warnings, defaults, or access flows.
- For the non-confidential summary, keep the same structure as the compliance report and replace confidential numbers with meaningful ranges, baselines, or aggregated values rather than empty redactions.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Article 11 establishes the compliance report, non-confidential summary, six-month post-designation submission, and annual update duties.
- [European Commission - Article 11 DMA Compliance Report Template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Commission template specifying the minimum Article 11 evidence expected for each core platform service and each applicable Article 5, 6 or 7 obligation.

## Run anti-circumvention checks before shipping product changes

Article 13 turns weak implementation into enforcement risk. It prohibits segmenting or splitting core platform services to avoid designation thresholds, requires full and effective compliance with Articles 5, 6 and 7, and bars contractual, commercial, technical, behavioural, or interface-design behaviour that undermines those obligations.

The practical test is whether the implementation preserves the right in substance. A compliant-looking flow can still be risky if it degrades service quality for users who exercise DMA rights, makes choices unduly difficult, uses non-neutral interface design, burdens business users more than the gatekeeper's own services, or relies on security, privacy or integrity restrictions that are broader than necessary.

- Review each product launch for service fragmentation, renamed service boundaries, changed domains, changed access conditions, or split metrics that could affect designation or obligation scope.
- For every restriction justified by security, privacy or integrity, document why the measure is strictly necessary and proportionate and why less restrictive options were not chosen.
- Test user and business-user journeys for neutral presentation, equal quality, friction, warnings, default settings, and degraded functionality after a DMA right is exercised.
- Escalate changes that affect data access, interoperability, app distribution, defaults, ranking, consent, or business-user communications before release.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Article 13 prohibits threshold circumvention and conduct that undermines effective compliance with Articles 5, 6 and 7.
- [European Commission - Article 11 DMA Compliance Report Template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Template asks gatekeepers to describe security, privacy and integrity measures and explain why they are strictly necessary and justified.

## Treat interoperability and access requests as compliance operations

Interoperability is not only a legal interpretation issue. Article 6(7) requires free and effective interoperability with operating system, hardware or software features accessed or controlled through a listed operating system or virtual assistant, subject to strictly necessary and proportionate integrity safeguards. Article 7 requires interoperability for listed number-independent interpersonal communications services upon request.

Commission interoperability materials show the kind of evidence expected in practice: request intake, developer-facing guidance, expected timelines, assessment criteria, feedback on proposed solutions, rejection reasoning, independent review, dispute resolution, request tracking, protection of non-public requester information, and public reporting metrics for interoperability requests.

- Maintain a request register with requester identity, requested feature, applicable article, eligibility assessment, confidentiality choice, status, decision reason, appeal or review status, and implementation milestone.
- Publish and version developer documentation, technical references, APIs, support pages, criteria, and terms used to evaluate requests.
- Separate teams and access controls so non-public information from interoperability requesters is used only to provide interoperability.
- For rejected requests, keep the unmet criteria, reasoning, next steps, Commission notification where applicable, and any internal-review or dispute-resolution record.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Articles 6(7) and 7 establish interoperability duties and the security, privacy and integrity boundaries for implementation.
- [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/interoperability-questions-and-answers_en?ref=sorena.io) - Commission Q&A describes interoperability specification decisions, request-process expectations, requester transparency, tracking, reporting, and the distinction between specification and non-compliance decisions.
- [European Commission - DMA resources for businesses](https://digital-markets-act.ec.europa.eu/questions-and-answers/resources-businesses_en?ref=sorena.io) - Commission business resources page links to gatekeeper resources for interoperability with OS features, data portability, and data access.

## Monitor enforcement exposure and compliance-function evidence

The Commission can adopt non-compliance decisions, require the gatekeeper to cease and desist, and impose fines for intentional or negligent failures to comply with Articles 5, 6 or 7, Commission-specified measures, systematic non-compliance remedies, interim measures, or binding commitments. The DMA also allows periodic penalty payments to compel compliance with specified measures, remedies, information requests, inspections, interim measures, commitments, and non-compliance decisions.

The compliance function should therefore keep management reports, risk assessments, decisions, replies from the management body, monitoring outputs, and remediation status together with the Article 11 evidence. A product team cannot close a DMA control merely by showing that a feature shipped; it must show that the measure is effective for the relevant obligation and that risks of non-compliance were escalated and addressed.

- Track findings by article, listed core platform service, owner, evidence gap, impact on business users or end users, remediation action, and management-body response.
- Keep a separate log for Commission requests, specification proceedings, non-compliance proceedings, whistleblower or business-user complaints, and commitments.
- Where a measure relies on estimates or best approximations, label the estimate, define the method, and retain the data source used.
- Do not rely on annual review alone for high-risk changes; trigger reassessment when a listed service, interface, API, ranking method, consent flow, data-sharing process, access term, or interoperability process changes.

**Who is responsible for DMA compliance evidence inside a designated gatekeeper?**

DMA evidence should have both an operational owner for the listed core platform service and an independent compliance-function owner. The Commission Article 11 template asks for the role of the head of the compliance function, reporting lines, monitoring activities, management reports on non-compliance risk, and management-body replies.

**What evidence should a DMA Article 11 compliance file contain?**

For each listed core platform service and each applicable Article 5, 6 or 7 obligation, keep the compliance statement, implementation explanation, supporting data, internal documents, pre-change baseline, implementation date, product and geographic scope, engineering changes, user-journey changes, terms or fee changes, consultation, testing, indicators, monitoring tools, feedback, and non-confidential-summary text.

**When does a DMA specification decision create enforcement risk?**

A specification decision is not itself a non-compliance decision and does not attach fines merely because it is adopted. It can still create practical enforcement risk because it specifies measures the gatekeeper is expected to implement, while separate non-compliance proceedings can lead to cease-and-desist orders and fines if the Commission later finds an infringement.

Sources for this answer:

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Articles 29, 30 and 31 support enforcement risk analysis, including non-compliance decisions, fines, and periodic penalty payments.
- [European Commission - Article 11 DMA Compliance Report Template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Template asks for compliance-function structure, management reporting, business-user and end-user feedback, monitoring systems, indicators, and summaries.
- [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/interoperability-questions-and-answers_en?ref=sorena.io) - Q&A distinguishes specification decisions from non-compliance decisions and explains that non-compliance decisions may include fines.

*Recommended next step*

*Placement: before sources*

## Build a DMA compliance record by listed core platform service

Sorena can help convert this DMA compliance guide into obligation matrices, Article 11 evidence requests, interoperability request records, anti-circumvention checks, and management-ready compliance summaries.

- [Open Research Copilot for DMA](/solutions/research-copilot.md): Ask questions tied to cited sources about gatekeeper scope, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, and enforcement exposure using the cited sources on this page.
- [Review DMA evidence](/contact.md): Check whether your DMA controls, report annexes, interoperability request records, and anti-circumvention evidence match the cited obligations.

## Primary sources

- [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/oj?ref=sorena.io) - Primary DMA legal text for gatekeeper designation, core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, Article 13 anti-circumvention, and enforcement powers.
  - Quote: "contestable and fair markets"
- [European Commission - DMA legislation](https://digital-markets-act.ec.europa.eu/legislation_en?ref=sorena.io) - Commission page for DMA legislation, procedural implementing regulation, templates, notices, guidelines, and related practical submission materials.
  - Quote: "main legislative texts"
- [European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Commission page listing designated gatekeepers, listed core platform services, case references, compliance reports, acquisitions, and consumer-profiling reports.
  - Quote: "Designated gatekeepers"
- [European Commission - Article 11 DMA Compliance Report Template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Commission template for the Article 11 compliance report, including service-by-service obligation evidence, monitoring, non-confidential summaries, and declaration expectations.
  - Quote: "Compliance Report"
- [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/interoperability-questions-and-answers_en?ref=sorena.io) - Commission Q&A on Article 6(7) interoperability specifications, request handling, tracking, reporting, and the difference between specification and non-compliance decisions.
  - Quote: "Interoperability Questions and Answers"
- [European Commission - DMA resources for businesses](https://digital-markets-act.ec.europa.eu/questions-and-answers/resources-businesses_en?ref=sorena.io) - Commission resource page linking business-user materials for interoperability with operating system features, data portability, and data access.
  - Quote: "Resources for businesses"

## Related Topic Guides

- [DMA Anti-Circumvention Design Review for Gatekeeper Product Changes](/artifacts/eu/digital-markets-act/anti-circumvention-design-review.md): Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records.
- [DMA Article 11 Compliance Report Template FAQ](/artifacts/eu/digital-markets-act/faq/compliance-report-template.md): How gatekeepers should use the DMA Article 11 compliance report template to document obligation-by-obligation measures, evidence, updates, and non-confidential summaries.
- [DMA Article 6 Business User Data Access Guide](/artifacts/eu/digital-markets-act/business-user-data-access.md): Official source guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs.
- [DMA Article 6(7) and Article 7 interoperability obligations](/artifacts/eu/digital-markets-act/article-6-7-interoperability.md): Official source guide to DMA interoperability duties: Article 6(7) operating-system feature access, Article 7 messaging interoperability, request handling, security conditions, and compliance evidence.
- [DMA Articles 5, 6 and 7 obligations mapped to CPS evidence](/artifacts/eu/digital-markets-act/core-obligations-by-obligation.md): Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts.
- [DMA compliance program and monitoring for gatekeepers](/artifacts/eu/digital-markets-act/compliance-program-and-monitoring.md): Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance.
- [DMA Core Platform Service Scoping](/artifacts/eu/digital-markets-act/core-platform-service-scoping-by-service.md): Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records.
- [DMA core platform services FAQ](/artifacts/eu/digital-markets-act/faq/core-platform-services.md): FAQ on EU Digital Markets Act core platform services: Article 2 service categories, gatekeeper designation evidence, user thresholds, service scoping, and Article 11 reporting.
- [DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence](/artifacts/eu/digital-markets-act/cps-obligation-matrix-workflow.md): Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates.
- [DMA designation intake workflow for gatekeeper notifications](/artifacts/eu/digital-markets-act/designation-intake-workflow.md): Build an official source DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness.
- [DMA enforcement, penalties, and remedies: Commission powers and evidence](/artifacts/eu/digital-markets-act/enforcement-penalties-and-remedies.md): EU Digital Markets Act enforcement guide covering Commission non-compliance decisions, DMA fine caps, periodic penalty payments, remedies, interim measures, commitments, and Article 11 evidence.
- [DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11](/artifacts/eu/digital-markets-act/gatekeeper-compliance-checklist.md): A cited EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates.
- [DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness](/artifacts/eu/digital-markets-act/gatekeeper-designation-guide.md): A cited EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting.
- [DMA gatekeeper thresholds: what counts and when to notify](/artifacts/eu/digital-markets-act/faq/gatekeeper-thresholds.md): Standalone FAQ on the EU Digital Markets Act gatekeeper thresholds, Article 3 notification timing, Form GD evidence, and active user-count methodology.
- [DMA interoperability requests: Article 7 and Commission guidance](/artifacts/eu/digital-markets-act/faq/interoperability-requests.md): How EU Digital Markets Act interoperability requests work for Article 7 messaging services, Article 6(7) operating-system access, gatekeeper evidence, requester evidence, and security safeguards.
- [DMA penalties and fines: caps, triggers, and enforcement evidence](/artifacts/eu/digital-markets-act/penalties-and-fines.md): EU Digital Markets Act penalties guide covering Article 30 fine caps, Article 31 periodic penalty payments, non-compliance decisions, remedies, and evidence records.
- [DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13](/artifacts/eu/digital-markets-act/product-change-review-workflow.md): Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff.
- [DMA Self-Preferencing Compliance Examples for Ranking and Display](/artifacts/eu/digital-markets-act/self-preferencing-compliance-examples.md): Examples and release-review controls for DMA Article 6(5) self-preferencing checks across ranking, indexing, crawling, search results, marketplaces, app stores, feeds, and virtual assistants.
- [DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules](/artifacts/eu/digital-markets-act/dma-vs-data-act.md): Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations.
- [DMA vs DSA: Digital Markets vs Services Act](/artifacts/eu/digital-markets-act/dma-vs-dsa.md): A cited-source comparison of the DMA and DSA focused on gatekeepers, core platform services, DMA obligations, Article 11 reporting, interoperability, data access, and enforcement.
- [DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement](/artifacts/eu/digital-markets-act/dma-vs-eu-competition-law.md): Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records.
- [DMA vs GDPR: gatekeeper data obligations compared](/artifacts/eu/digital-markets-act/dma-vs-gdpr.md): Compare DMA gatekeeper obligations with high-level GDPR overlap for consent, combining personal data, data access, portability, and Article 11 reporting.
- [EU Digital Markets Act Article 11 Evidence Calendar](/artifacts/eu/digital-markets-act/annual-report-evidence-calendar.md): Build an official source DMA Article 11 compliance report calendar with evidence owners, annual update checkpoints, report sections, and review gates.
- [EU Digital Markets Act checklist for gatekeeper compliance](/artifacts/eu/digital-markets-act/checklist.md): An official source DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance.
- [EU Digital Markets Act deadlines and compliance calendar](/artifacts/eu/digital-markets-act/deadlines-and-compliance-calendar.md): Track DMA notification, designation, six-month obligation start, Article 11 reporting, Article 14 concentration notices, Article 15 profiling audits, and preparation milestones using official EU sources.
- [EU Digital Markets Act FAQ: gatekeepers, DMA obligations, reports, and enforcement](/artifacts/eu/digital-markets-act/faq.md): Concise FAQ on the EU Digital Markets Act for gatekeeper designation, core platform services, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, business-user data access, compliance evidence, and enforcement.
- [EU Digital Markets Act requirements for gatekeepers](/artifacts/eu/digital-markets-act/requirements.md): DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines.
- [EU Digital Markets Act Timeline and Key Milestones: practical obligations and evidence guide](/artifacts/eu/digital-markets-act/timeline-and-key-milestones.md): Practical EU Digital Markets Act guide to Timeline and Key Milestones: scope, owners, evidence, edge cases, checklist steps, and external cited citations.
- [EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence](/artifacts/eu/digital-markets-act/applicability-test.md): Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records.
- [EU DMA Article 11 Compliance Reporting Guide](/artifacts/eu/digital-markets-act/article-11-reporting.md): Official source guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps.
- [EU DMA do's and don'ts for product teams](/artifacts/eu/digital-markets-act/dos-and-donts-for-product-teams.md): Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence.
- [What do DMA Articles 5, 6, and 7 require from gatekeepers?](/artifacts/eu/digital-markets-act/faq/articles-5-6-and-7-obligations.md): FAQ explaining how EU Digital Markets Act Articles 5, 6, and 7 group gatekeeper obligations, what product evidence they require, and how Article 11 reporting connects.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/digital-markets-act/compliance