> 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/want-to-explore/readme-1.md).

# Development on Hyperswitch

At Juspay, we believe payment infrastructure should be transparent, adaptable, and under merchants' control—not confined by vendor restrictions. That's why we've made the bold move to open-source our Payment Orchestrator.​

This modular, composable platform allows you to deploy on-premise for full access or select only the components you need.

To run Hyperswitch locally, follow our Docker setup guide. Alternatively, explore our cloud deployment guides for additional options. ​

## Local Setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Unified Local Setup using Docker (Recommended)</strong></mark></td><td>Simplified local setup of all components, using a single command with the help of docker.</td><td></td><td><a href="/self-hosting/want-to-explore/readme-1/unified-local-setup-using-docker.md">Run Hyperswitch Locally Using Docker</a></td><td></td></tr><tr><td><mark style="color:blue;"><strong>Development Environment Setup</strong></mark></td><td>Local setup of development environment to build with Hyperswitch</td><td></td><td><a href="/self-hosting/want-to-explore/readme-1/local-setup-using-individual-components.md">Advanced Development Env Setup</a></td><td></td></tr></tbody></table>

## Cloud Setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Deploy Hyperswitch on AWS</strong></mark></td><td>Deploy Hyperswitch on AWS either as an independent stack or as individual components.</td><td></td><td><a href="/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws.md">Deploy on AWS</a></td><td></td></tr><tr><td><mark style="color:blue;"><strong>Deploy Hyperswitch on Kubernetes</strong></mark></td><td>Install Hyperswitch on GCP or Azure using our Helm charts.</td><td></td><td><a href="/self-hosting/want-to-explore/readme.md">Quickstart</a></td><td></td></tr></tbody></table>

{% hint style="success" %}
Want to try without deploying? Use our dashboard on [sandbox](https://app.hyperswitch.io/).
{% endhint %}

### Learning Resources

In case you are completely new to payments - You can comeback to setup after reading the [Payment 101 Blog](https://github.com/juspay/hyperswitch/wiki/Payments-101-for-a-Developer), For more learning resources visit [Hyperswitch Blogs.](https://hyperswitch.io/blogs)

{% hint style="info" %}
**Have Questions?**\
Join our [Slack Community](https://join.slack.com/t/hyperswitch-io/shared_invite/zt-2jqxmpsbm-WXUENx022HjNEy~Ark7Orw) to ask questions, share feedback, and collaborate.\
Prefer direct support? Use our [Contact Us](https://hyperswitch.io/contact-us) page to reach out.
{% endhint %}


---

# 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/want-to-explore/readme-1.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.