1. GAFAM

1.1. Technical Sovereignty

  • Open Standards: (in progress)
    Rely on open standards (W3C, ISO, ETSI, etc.) in areas such as digital identity, digital wallets, education, or health data. This reduces dependency on proprietary protocols and APIs controlled by big tech.

  • Open Source:
    Invest in open-source projects that can serve as alternatives to big tech services.

1.2. Regulation & Policy

  • Antitrust regulation:
    Limit monopolistic acquisitions or abuse of dominant market positions. The EU’s Digital Markets Act (DMA) is a strong example.

  • Data Protection Laws: (in progress)
    Apply strong data protection frameworks (like GDPR) to restrict the uncontrolled use of personal data by large companies.

  • Mandatory Interoperability:
    Legally require large platforms to interoperate with competitors (e.g., WhatsApp being forced to work with other messaging apps under the DMA).

  • Government Support:
    Governments can provide funding and legal support to SMEs and startups in strategic areas such as AI, digital identity, and sovereign cloud.

1.3. Ecosystem & Market

  • Local and Regional Innovation: (in progress)
    Build services tailored to local needs (for example, digital identity or wallets adapted to European banking/education regulations).

  • International Consortia: (in progress)
    Form alliances across countries, universities, or companies to build joint ecosystems (e.g., DC4EU in the field of digital educational identity).

2. Encounter with other technology and other projects

  1. Rely on base standards → Build on widely accepted specs (W3C Verifiable Credentials, DIDs, OIDC4VC, ISO 18013-5) that will remain compatible with EUDI.

  2. Focus on domain use cases → Implement specific education & research needs (e.g. attributes, group/role management, research federation scenarios) as identified by projects like DC4EU and FIM4R.

  3. Prepare a bridge layer → Design a conversion/translation mechanism so your wallet’s credentials can be mapped to future EUDI formats if differences appear (interoperablity risk as well)

  4. Define our scope and what we can deliver specifically based on Trust structure like eduGAIN and focusing on NRENs as our targets 8combine with nr. 2)

3. Marketing 

  1. Compatibility with new rules
  2. Participation in the activities steering and show case the development (in progress)
  3. Communicate with institutes to bring them to ecosystem (in progress)

    1. Instead of traditional ads, invest in white papers, webinars, and presentations at digital-education conferences. (in progress)

    2. Participate in EU digital-identity working groups or academic tech communities — this builds long-term trust and awareness.(in progress)

    3. Contribute open-source components or SDKs, this signals transparency and encourages adoption. (question)

  4. Position ourselves as complementary to existing initiatives (eduGAIN, EUDI Wallet, DC4EU), not as a competitor.

  5. Collect user feedback and demonstrate ROI or cost-saving potential. (To DO)

  6. Provide the wallet to institutions, not directly to individual students, reduces marketing complexity (B2B2C model). (To DO)

4. Funding

  • Participating in projects and present ourself and requirements and capabilities
  • New risk: (mitigation (question))
    • If the pilots are ready who will fund the next steps (development, testing, promotion, support...) e.g SPRIND. It is also a problem for scaling.
    • If the bussiness plan is not complete , we don't know which stakeholder or player like RP or user should bring funding to that. 
      • Mitigation idea: Provide a good bussiness plan (To DO)
      • Try to be comperehnsive to reduce the cost of support

5. Environmental cost

  • Not selecting environmental consuming technology like some types of ledgers (Done)


  • No labels