Deploying a data space is often described as a technical exercise. In reality, it is the moment where infrastructure, governance, identity, and value exchange come together into an ecosystem.
Ocean Enterprise provides the components needed to make this possible. But understanding the stack is only the first step. The real challenge lies in assembling these components into a coherent, functional environment.
This guide walks through that process, clearly, practically, and with a focus on what matters when moving from concept to deployment, following the steps from the webinar.
https://www.youtube.com/watch?v=fIlwwGpTOGA
Understanding the Ocean Enterprise stack
Before deployment begins, it is important to understand what you are building. Ocean Enterprise is a combination of interconnected components, each with a specific role:
- Marketplace — the interface where users publish and access data assets
- Node — the core engine responsible for asset handling, encryption, and transactions
- SSI Stack — the identity layer enabling decentralized credentials and verification
- Policy Server and Proxy — the components that enforce access rules
- Blockchain and IPFS — the infrastructure ensuring transparency and decentralized storage.
Together, these elements form a system where data can be shared securely, accessed conditionally, and monetized transparently.
Key Decisions Before Deployment
A successful deployment starts with clarity. Before configuring anything, a few fundamental questions need to be answered: What infrastructure will support your data space?
You will need to select:
- A blockchain network (for example, Ethereum Sepolia)
- A token or currency for transactions (such as EuroC)
- An IPFS provider for storing asset metadata.
These choices directly impact performance, cost, and scalability.
How will value be created and distributed?
Ocean Enterprise allows flexible fee structures. A typical setup may include:
- A fixed fee per asset consumption
- A percentage-based marketplace fee
- A provider-level pricing model.
Will identity and verification be enforced?
Enabling Self-Sovereign Identity (SSI) introduces a layer of trust:
- Participants hold their own credentials
- Access is granted based on verifiable claims
- Policies become enforceable in real time.
Architecture Overview
Ocean Enterprise deployments are designed to be modular and distributed.
A common setup includes multiple virtual machines, each responsible for a specific component:
- Marketplace
- Node
- Policy Server and Proxy
- SSI Stack
These components are typically accessed through a reverse proxy, which acts as a secure gateway between the system and external users.
This separation improves both security and scalability, while making the system easier to manage and extend.
Step 1: Deploying the SSI Stack
The SSI stack includes:
- A wallet for storing credentials
- A verifier for validating them
- A policy agent (OPA server) for applying rules.
Once deployed, this layer enables the system to:
- Request credentials from users
- Verify those credentials securely
- Integrate identity into access decisions.
At this stage, your data space becomes capable of recognizing participants as verified entities.
Step 2: Setting Up the Policy Layer
With identity in place, the next step is governance.
The Policy Server evaluates access requests, while the Policy Server Proxy ensures communication between components.
Together, they:
- Validate incoming requests
- Apply predefined rules
- Determine whether access should be granted or denied.
These rules can include checks for:
- Credential validity
- Signature authenticity
- Revocation status.
This layer transforms your system from a simple data exchange platform into a controlled environment where access is conditional and auditable.
Step 3: Deploying the Ocean Node
The Node is where the system becomes operational. It connects all the underlying services and enables:
- Asset registration and indexing
- Secure data access
- Payment processing
- Compute-to-data execution.
To function correctly, the Node requires:
- A blockchain RPC provider for reading network data
- An IPFS gateway for accessing stored metadata
- An Elasticsearch instance for indexing assets.
Configuration at this stage includes:
- Blockchain endpoints
- Storage settings
- Fee structures
- Policy server integration.
This is also where optional compute environments can be enabled, allowing algorithms to run directly on data without exposing it, a key capability for privacy-preserving analytics.
Step 4: Deploying the Marketplace
The Marketplace is the layer users interact with. It connects everything behind the scenes and provides:
- Asset discovery
- Publishing workflows
- Transaction handling
- Integration with SSI verification.
Configuration includes:
- Node connections
- Blockchain settings
- IPFS integration
- Fee definitions
- Identity and policy endpoints.
Once deployed, the Marketplace turns the system into something tangible, an environment where users can actively participate.
Step 5: Testing the System
A successful deployment is validated through real interactions.
Two key flows should be tested:
Publishing an Asset
A user creates an asset, defines pricing, and attaches access policies. The asset is then registered and indexed.
Consuming an Asset
Another user attempts to access the asset:
- The system requests credentials
- The user provides them via their SSI wallet
- The policy server evaluates the request
- Access is granted or denied.
Even when errors occur, the goal is to confirm that the entire flow, from identity to policy enforcement, functions correctly.
Practical Considerations
During deployment, several operational aspects should not be overlooked:
- Blockchain access: Using a reliable RPC provider is essential for performance
- Storage accessibility: IPFS gateways must be correctly configured and publicly reachable
- Transaction fees: Node accounts must maintain sufficient balance for operations
- Security: Environment files and private keys must be handled with care.
These details often determine whether a deployment works smoothly or becomes difficult to maintain.
Deploying Ocean Enterprise is about building a system where data remains under control, access is governed by rules and value is exchanged transparently.
About Ocean Enterprise Collective
The Ocean Enterprise Collective e.V. (OEC) is a non-profit association committed to providing next generation data exchange software that is available to everyone and owned by no one.
The primary focus of OEC is designing, developing and maintaining Ocean Enterprise (OE), a free open-source enterprise-ready data ecosystem software solution that enables organizations to securely manage and monetize proprietary AI & data products and services in a trusted and compliant environment.
OEC members span numerous countries and represent various industries including agriculture, healthcare, aerospace, and manufacturing. We invite you to join us in actively shaping the future of data sharing, AI compliance, and decentralized marketplaces.
Get in touch with the Ocean Enterprise Collective team: info@oceanenterprise.io
