mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-02 00:05:35 +01:00
37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
---
|
|
title: Ecosystem
|
|
description: The Ocean Protocol network consists of various components. Learn about all of them here.
|
|
---
|
|
|
|
## Keeper-contracts
|
|
|
|
See also [Set Up a Keeper](/setup/keeper/)
|
|
|
|
- [💧 keeper-contracts](https://github.com/oceanprotocol/keeper-contracts)
|
|
|
|
## Aquarius
|
|
|
|
Aquarius provides an off-chain database store for metadata about data assets. Every marketplace must run an instance of Aquarius.
|
|
|
|
- [🐋 aquarius](https://github.com/oceanprotocol/aquarius)
|
|
|
|
## Brizo
|
|
|
|
Brizo is the technical component executed by Publishers allowing them to provide extended data services. Brizo, as part of the Publisher ecosystem, includes the credentials to interact with the infrastructure (initially cloud, but could be on-premise).
|
|
|
|
- [brizo](https://github.com/oceanprotocol/brizo)
|
|
|
|
## Pleuston
|
|
|
|
An example marketplace front-end for consumers to explore, download, and publish data assets within the Ocean Protocol network. Implemented using React and squid-js.
|
|
|
|
- [🦄 pleuston](https://github.com/oceanprotocol/pleuston)
|
|
|
|
## Squid
|
|
|
|
Client libraries used by applications to interact with Ocean nodes, including Keepers, Aquarius nodes, Brizo nodes, etc.
|
|
|
|
- [🦑 squid-js](https://github.com/oceanprotocol/squid-js)
|
|
- [🦑 squid-py](https://github.com/oceanprotocol/squid-py)
|
|
- [🦑 squid-java](https://github.com/oceanprotocol/squid-java)
|