Configuring a data space from the browser: why the visual interface matters more than it seems
In the European data space ecosystem, two radically different philosophies coexist. The first demands that every new capability be implemented as a code extension: want to add a new storage type, write a Java extension; want to change an access policy, modify a config file and redeploy. The second philosophy, the one our data space follows, bets that virtually all configuration and management can be done from a web interface, without touching a single line of code.
The extension problem: the developer barrier
Code extension-based solutions work well for powerful technical teams with dedicated Java developers. But in European reality, many organizations wanting to participate in a data space don't have that profile. An agricultural cooperative, a local public administration, or an industrial SME can't afford to maintain a development team just to configure their connector.
Each extension adds complexity: it requires compilation, testing, versioning, and full connector redeployment. A change that conceptually takes 5 minutes can translate into hours of engineering work and days waiting for the next deployment.
Everything from the browser: what you can do without code
Our data space offers a complete web application from which an administrator can manage virtually every aspect of the connector:
Data connectors. Create and configure data sources and sinks (databases, APIs, cloud, IoT) through forms automatically generated from each connector's schema. No manual configurations or JSON files.
Catalogs and datasets. Publish catalogs, create datasets with multilingual metadata, define multiple ODRL usage policies, and manage them visually from the interface.
Negotiations and agreements. Initiate, review, and respond to negotiations. Customize policies with permissions, prohibitions, obligations, and payments through a step-by-step visual editor.
Transfers. Monitor active transfers, view their state history, and create internal data sources from received transfers.
Pipelines. Design data flows visually by dragging nodes (sources, apps, sinks), configure parameters, and schedule automatic executions.
Identity and trust. Configure DID methods, manage TLS certificates, add trusted issuers, request and manage attestations.
Gaia-X. Enable Gaia-X compatibility, select trust frameworks, and request compliance credentials, all from an admin panel.
Clearing House and broker. Enable special operating modes (metadata broker, clearing house) with a toggle in configuration, no redeployment needed.
Smart forms: configuration that adapts
Each data connector defines a declarative configuration schema that the system automatically translates into dynamic forms. Fields show or hide based on previous user selections: choose Bearer authentication, the token field appears; choose Basic, username and password appear. If the connector supports multiple message formats (JSON, CSV, raw), the form shows format-specific options.
Additionally, the system can automatically import field definitions from the connection, eliminating the need to manually configure the data structure.
One-click connectivity testing
Before using a data source or sink in production, the administrator can test connectivity directly from the interface. The system verifies that credentials are correct, the server is reachable, and the configuration is valid—all without leaving the browser. If something fails, the error is displayed immediately with enough context to fix it.
Real-time notifications and events
The web interface is not static: it's connected to the backend through real-time events. When a new negotiation request arrives, when a pipeline finishes executing, or when an attestation is received, the administrator gets the notification instantly without refreshing the page. This transforms connector management into a fluid experience, not a cycle of reloads and waiting.
Native internationalization
The entire interface supports multiple languages natively. Connector names, field descriptions, error messages, and help texts go through an automatic translation system. When a new connector is added, a single command detects and generates pending translation keys. This ensures an administrator in Spain, Germany, or France sees the interface in their language.
Democratizing the data space
Making a data space configurable from the frontend is not a matter of convenience: it's a strategic decision about who can participate in the data economy. If participating requires a Java developer team, only large companies will play. If participating requires a browser and an administrator with basic training, the data space opens up to cooperatives, local governments, research centers, and SMEs.
Our data space demonstrates that complying with the IDS protocol, implementing decentralized identity, and managing ODRL policies doesn't have to be an engineering feat reserved for those writing Java extensions. It can be as simple as filling out a form.