# Infrastructure There are many ways in which the components can be deployed, from simple configurations used for development and testing to complex configurations, used for production systems. All the Ocean Protocol components ([Provider](/developers/old-infrastructure/provider.md), [Aquarius](/developers/old-infrastructure/aquarius.md), [Subgraph](/developers/old-infrastructure/subgraph.md)) are designed to run in Docker containers, on a Linux operating system. For simple configurations, we rely on Docker Engine and Docker Compose products to deploy and run the components, while for complex configurations we use Kubernetes. The guides included in this section will present both deployment options. Please note that deploying the Ocean components requires a good understanding of: * Linux operating system * Docker Engine * Docker Compose or Kubernetes (depending on the configuration chosen for the component deployment) Please note that Ocean Marketplace is not a core component of the stack but rather an example of what can be achieved with the technology, in this section we included a guide on how to deploy it. All components need to be deployed on a server, so we included a guide about how to install and configure a server will all the necessary tools. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.oceanprotocol.com/infrastructure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.