> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure.md).

# Deployment Guides

Learn how to deploy Ocean Enterprise in your environment.

This chapter explains how to install and configure the components of the Ocean Enterprise software stack. All components run in Docker containers on a Linux operating system. Deploying the OE components requires solid familiarity with Linux, Docker Engine, and Docker Compose. 

As described in the [Dataspace Configuration Options](/~/revisions/IKmS06jx6d2zQh2vmKN9/developers/architecture-1.md) chapter, the OE Stack supports two deployment modes - with SSI-based access control enabled or disabled. Because the required components and installation order vary by configuration, consult the dedicated chapter on the installation sequence for each configuration.   

Each deployment subchapter is structured into four parts: 

* *Prerequisites*: lists the hardware, software, and other requirements for running the component\ <mark style="color:$info;background-color:$info;">**Note**</mark><mark style="color:$info;background-color:$info;">: The hardware specifications provided represent the minimum configuration identified during our testing. Actual requirements vary based on workload characteristics such as the number of concurrent requests and expected response times. We recommend starting with an estimated configuration based on your anticipated workload, monitoring system performance over time, and adjusting resources accordingly.</mark>
* *Deployment Steps*: describes the tasks required to perform to install and configure the component.
* *Post installation steps*: tasks that must be completed for the component to function properly
* *Environment Variables*: explains the purpose and usage of each environment variable needed by the component

This chapter includes the following information:

* [Deployment Modes](/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure/deployment-modes.md)
* [OE Node Installation and Configuration](/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure/oe-node-installation-and-configuration.md)
* [Marketplace Installation and Configuration](/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure/marketplace-installation-and-configuration.md)
* [Policy Server and Policy Server Proxy Installation and Configuration](/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure/policy-server-and-policy-server-proxy-installation-and-configuration.md)
* [SSI Stack Installation and Configuration](/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure/ssi-stack-installation-and-configuration.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/infrastructure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.