> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws/component-wise-deployment/deploy-web-client.md).

# Deploy web client

Deploy the Hyperswitch web client on the cloud for production use

{% hint style="info" %}
This section is aimed at helping you deploy the Web client on the cloud and access it over the internet
{% endhint %}

Deploying web client consists of two main steps:

1. Deploy HyperLoader.js - this is the core logic of the web client
2. Integrate the web client SDK on your app and deploy the app

For quick prototyping, you can also try out deploying the full stack integrated demo app playground.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Production ready deployment</strong></td><td>Host the web client SDK (<strong>HyperLoader.js</strong>) on the cloud to serve your customers.</td><td></td><td></td></tr><tr><td><strong>Integrate on your app and deploy[REGULAR]</strong></td><td>Once HyperLoader.js is deployed on cloud, integrate the SDK in your web app.</td><td></td><td></td></tr><tr><td><strong>Deploy the playground (OPTIONAL)</strong></td><td>The web client comes with a full stack playground for quick prototyping. Test the deployment with a single script and get a feel of the product before you integrate it on your app.</td><td></td><td></td></tr></tbody></table>


---

# 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.hyperswitch.io/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws/component-wise-deployment/deploy-web-client.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.