> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/legacy-documentation/ew-dos-technology-components-2023/decentralized-data-hub-ddhub/ddhub-client-gateway.md).

# DDHub Client Gateway

The DDHub Client Gateway is an integration gateway SDK that is intended to run on-premises or on the cloud environment of participants. It provides an interface for participant systems to interact with other systems in the shared interacting with a data exchange solution - namely, the DDHub Message Broker.

The Client Gateway is available in Github at <https://github.com/energywebfoundation/ddhub-client-gateway> or in the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/energywebdevhubgmbh1670375546257.ewf-data-exchange-client-gateway?tab=Overview).

The gateway application is authenticated, authorized, and encrypted (messages) using self-sovereign identities (DIDs) and verifiable credentials rather than a centrally trusted and managed approaches seen in legacy solutions.

The client container is an integral part of the DDHub in achieving its decentralized characteristics as it assumes the power of the identity that it currently holds/represents.

<figure><img src="/files/qjzdADMnppM1AKERGAbb" alt=""><figcaption></figcaption></figure>

* DDHub Client GW UI: the main interface for admins to manage their DDHub Client GWs
* DDHub Client GW API: exposes RESTful and Web Socket APIs for integration
* DDHub Client GW Scheduler: contains scheduler jobs for caching data including but not limited to channels, topics, and decryption keys
* DDHUB Client Gateway Storage: a postgres DB used to store configuration data.
* Key Vault - store private keys and other secrets
* DDhub Message Broker: The component that routes messages between Client gateways (using API to control NATS messaging).
* SSI Toolkit: Libraries and components that implement identity and access management functionalities.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.energyweb.org/legacy-documentation/ew-dos-technology-components-2023/decentralized-data-hub-ddhub/ddhub-client-gateway.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.