Yes; Simpl can connect “non-dataspace” actors (e.g., open data platforms, databases, initiatives, service providers) to a data space, typically by having them onboarding as participants via the Simpl agents. Practically, this means they can publish/discover metadata, apply trust/policy controls, and interoperate with other participants without needing to “become a data space” themselves.

Simpl-Live moves from feasibility to execution through structured implementation phases that validate assumptions, align scope and dependencies, and progressively deploy Simpl-Open components. There is no single standard plan applied to all data spaces; each integration is tailored to its maturity, technical architecture, and roadmap constraints.

For example, the Simpl-Live implementation phase of EOSC starts in February 2026, and requires tight coordination and early agreement on federation roles and responsibilities, which makes its alignment more complex than in other cases.

Partially. The studies primarily focused on the analysing  fit-gap, requirements and integration roadmaps based on existent documentation of the data spaces. Desirability/viability elements were captured indirectly through stakeholder priorities and constraints (adoption drivers, sovereignty concerns, cost sensitivity, readiness). A recurring conclusion was that interoperability and federation drive desirability, while operational cost, complexity, and missing roadmap items can threaten viability unless implementation support (planned during the Simpl-Live Implementations) and clear governance/operating models are in place.

GDDS scope was to assess how Simpl-Open could be integrated into GDDS (in a Common European Data Space context) by analysing the current GDDS readiness, identifying gaps, and proposing a feasibile integration approach and roadmap. A known constraint was that GDDS had limited architecture/process documentation during the Feasibility Study analysis, so parts of the analysis relied on workshops, preparatory materials, and explicitly documented assumptions/limitations.

It means plugging Simpl’s modules when feasible to support the creation of the common european data spaces, so participants can: 

1. Identify and trust each other
2. Publish and find data/services
3. Enforce usage rules/policies
4. Share (data, applications, infrastructure) resources securely while preserving full control over these resources.

Simpl-Open is the middleware SW used as technical enabler of a data space; it is designed to support standard business processes of a data space (e.g. Setting up a Governance Authority, Setting up the data space rules, Onboarding Data Space Participants, Onboarding End Users, Resource Publication / Discovery / Consumption, Contract Negotiation, Logging, Monitoring, Reporting, Auditing, Cross data space federation etc.). With Simpl-Open, any association of two or more organizationa can create a data space by integrating it with their existing infrastructure.

The data space operator needs to define the governance, management and operation rules to be configured in Simpl-Open to allow the data space to function as desired. Simpl-Open provides extensive documentation guiding the data space operators in what is required to configure the data space processes in line with the data space rules. Examples of elements to be provided / defined by the entity operating / governing the data space: metadata schema; ontology; onboarding templates; contract templates; terms and conditions for joining the data space; identity attributes etc. 

Simpl-Open is the open-source technical enabler of a data space / initiative. The business model, costs, revenues, capital flow management are all attributes of the data space / initiative adopting Simpl-Open. 

Based on the working cadence and the end-of-contract target we discussed, the expectation is finalisation by end of February 2026, assuming reviews close on time. Work is still ongoing and there is no concrete dates on when the report may be publicly available.

N/A - we are not in position to answer.

Possible example: At a generic level, Simpl could to be governed through a European governance structure (rulebook + accountable governance body), where a mix of variants of known EU entities frameworks could be responsible (EU entity, MS-driven EDIC, association, regulatory rulebook, expert group). For now, Simpl is governed by the European Comission and managed by DG Connect.

N/A - we are not in position to answer.

Possible example: By standardising the technical foundations of data spaces: common ways to identify actors, publish/discover resources, apply policies, and support federation across multiple data spaces. Cross-domain becomes feasible when different domains rely on the same interoperable baseline “rules + mechanisms + Technology”, even if their domain semantics differ.

N/A - we are not in position to answer.

Possible example: SME's can create associations and establish their own data space based on their own rules, as Simpl-Open is a configurable open-source product. SMEs should absolutely be strongly represented and empowered. In addition, the “hybrid” governance is not a bureaucracy; it’s a mean to ensure consistent trust, compliance, and interoperability while allowing decentralised operations.

It has been considered, as this comes up often as an adoption barrier, but not yet planned.

Simpl-Open is primarily designed to enable a data space of multiple participating organizations with a central governance authority, which can be established by the participants themsleves. Additionally, Simpl-Open enables federation of multiple data spaces, allowing participants in one data space (based on well defined federation rules) to be automatically recognized / trusted in the other data spaces and operate in that data space within the boundaries set through federation configurations. 

End users who own data are managed internally by their respective organisations. This internal governance process is outside the scope of Simpl-Open.

Simpl-Open provides interoperability, identity and trust, catalogue, policy/contract enforcement, monitoring, and billing/invoicing mechanisms that enable organisations to share resources (data, applications, infrastructure) in a controlled and auditable way. It does not replace internal organisational user management.

The specific feasibility studies will most likely not be shared publicly but with the relevant stakeholders only. However, a Consolidated  Feasibility Study Report is expected to be developed and shared on the Simpl Website. This Consolidated Report will contain a summary of the results of each specific feasibility study, and common aspects, such as: [1] common requirements from Simpl-Live selected data spaces; requirements to be considered for Simpl-Open further developments; conclusions and recommendations.

Near-real-time use cases typically require specialised data pipelines and operational constraints (latency, reliability, streaming), Simpl-Open can support (near) real-time data sharing through by adding relevant extensions to the data plane of its EDC component. Simpl’s role is usually to provide the trust, identity, policy enforcement, catalog/federation and accountability layer around those exchanges; while the real-time data plane may remain UseCase-specific. In other words: Simpl can enable who can access what, under which rules, across which federated parties, even when the transport is real-time.