Bug: chore: Update readme with juspay's vision, product offering, architecture diagram, setup steps and output




diff --git a/README.md b/README.md
index 10fdb6afc76..c09176b172a 100644
--- a/README.md
+++ b/README.md
@@ -3,22 +3,11 @@
   <img src="./docs/imgs/hyperswitch-logo-light.svg#gh-light-mode-only" alt="Hyperswitch-Logo" width="40%" />
 </p>
 
-<h1 align="center">The open-source payments switch</h1>
+<h1 align="center">Open-Source Payments Orchestration</h1>
 
 <div align="center" >
-The single API to access payment ecosystems across 130+ countries</div>
-
-<p align="center">
-  <a href="#try-a-payment">Try a Payment</a> •
-  <a href="#quick-setup">Quick Setup</a> •
-  <a href="/docs/try_local_system.md">Local Setup Guide (Hyperswitch App Server)</a> •
-  <a href="https://api-reference.hyperswitch.io/introduction"> API Docs </a> 
-   <br>
-  <a href="#community-contributions">Community and Contributions</a> •
-  <a href="#bugs-and-feature-requests">Bugs and feature requests</a> •
-  <a href="#versioning">Versioning</a> •
-  <a href="#copyright-and-license">Copyright and License</a>
-</p>
+Single API to access the payments ecosystem and its features
+</div>
 
 <p align="center">
   <a href="https://github.com/juspay/hyperswitch/actions?query=workflow%3ACI+branch%3Amain">
@@ -45,28 +34,46 @@ The single API to access payment ecosystems across 130+ countries</div>
 
 <hr>
 
-Hyperswitch is a community-led, open payments switch designed to empower digital businesses by providing fast, reliable, and affordable access to the best payments infrastructure.
+## Table of Contents
 
-Here are the components of Hyperswitch that deliver the whole solution:
+1. [Introduction](#introduction)
+2. [Architectural Overview](#architectural-overview) 
+3. [Try Hyperswitch](#try-hyperswitch)  
+4. [Support, Feature requests & Bugs](#support-feature-requests)  
+5. [Our Vision](#our-vision)  
+6. [Versioning](#versioning)  
+7. [Copyright and License](#copyright-and-license)
 
-* [Hyperswitch Backend](https://github.com/juspay/hyperswitch): Powering Payment Processing
+<a href="#introduction">
+  <h2 id="introduction">Introduction</h2>
+</a>
+Juspay, founded in 2012, is a global leader in payment orchestration and checkout solutions, trusted by 400+ leading enterprises and brands worldwide. Hyperswitch is Juspay's new generation of composable, commercial open-source payments platform for merchant and brands. It is an enterprise-grade, transparent and modular payments platform designed to provide digital businesses access to the best payments infrastructure.
 
-* [SDK (Frontend)](https://github.com/juspay/hyperswitch-web): Simplifying Integration and Powering the UI
+Here are the key components of Hyperswitch that deliver the whole solution:
 
-* [Control Centre](https://github.com/juspay/hyperswitch-control-center): Managing Operations with Ease
+* [Hyperswitch Backend](https://github.com/juspay/hyperswitch): Hyperswitch backend enables seamless payment processing with comprehensive support for various payment flows - authorization, authentication, void and capture workflows along with robust management of post-payment processes like refunds and chargeback handling. Additionally, Hyperswitch supports non-payment use cases by enabling connections with external FRM or authentication providers as part of the payment flow. The backend optimizes payment routing with customizable workflows, including success rate-based routing, rule-based routing, volume distribution, fallback handling, and intelligent retry mechanisms for failed payments based on specific error codes.
 
-Jump in and contribute to these repositories to help improve and expand Hyperswitch!
+* [SDK (Frontend)](https://github.com/juspay/hyperswitch-web): The SDK, available for web, [Android, and iOS](https://github.com/juspay/hyperswitch-client-core), unifies the payment experience across various methods such as cards, wallets, BNPL, bank transfers, and more, while supporting the diverse payment flows of underlying PSPs. When paired with the locker, it surfaces the user's saved payment methods.    
 
-<img src="./docs/imgs/switch.png" />
+* [Control Center](https://github.com/juspay/hyperswitch-control-center): The Control Center enables users to manage the entire payments stack without any coding. It allows the creation of workflows for routing, payment retries, and defining conditions to invoke 3DS, fraud risk management (FRM), and surcharge modules. The Control Center provides access to transaction, refund, and chargeback operations across all integrated PSPs, transaction-level logs for initial debugging, and detailed analytics and insights into payment performance.
+
+Read more at [Hyperswitch docs](https://docs.hyperswitch.io/).
+
+<a href="#architectural-overview">
+  <h2 id="architectural-overview">Architectural Overview</h2>
+</a>
+<img src="./docs/imgs/features.png" />
+<img src="./docs/imgs/non-functional-features.png" />
 
+<img src="./docs/imgs/hyperswitch-architecture-v1.png" />
 
-<a href="#Quick Setup">
-  <h2 id="quick-setup">⚡️ Quick Setup</h2>
+<a href="#try-hyperswitch">
+  <h2 id="try-hyperswitch">Try Hyperswitch</h2>
 </a>
 
-### Docker Compose
+### 1. Local Setup
 
-You can run Hyperswitch on your system using Docker Compose after cloning this repository:
+You can run Hyperswitch on your system using Docker compose after cloning this repository. 
 
 ```shell
 git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch
@@ -74,23 +81,49 @@ cd hyperswitch
 docker compose up -d
 ```
 
-This will start the app server, web client/SDK and control center.
-
-Check out the [local setup guide][local-setup-guide] for a more comprehensive
-setup, which includes the [scheduler and monitoring services][docker-compose-scheduler-monitoring].
+Check out the [local setup guide][local-setup-guide] for a more details on setting up the entire stack or component wise. This takes 15-mins and gives the following output 
+```shell
+[+] Running 2/2
+✔ hyperswitch-control-center Pulled 2.9s
+✔ hyperswitch-server Pulled 3.0s
+[+] Running 6/0
+
+✔ Container hyperswitch-pg-1 Created 0.0s
+✔ Container hyperswitch-redis-standalone-1 Created 0.0s
+✔ Container hyperswitch-migration_runner-1 Created 0.0s
+✔ Container hyperswitch-hyperswitch-server-1 Created 0.0s
+✔ Container hyperswitch-hyperswitch-web-1 Created 0.0s
+✔ Container hyperswitch-hyperswitch-control-center-1 Created 0.0s
+
+Attaching to hyperswitch-control-center-1, hyperswitch-server-1, hyperswitch-web-1, migration_runner-1, pg-1, redis-standalone-1
+```
 
-### One-click deployment on AWS cloud
+### 2. Deployment on cloud
 
-The fastest and easiest way to try Hyperswitch is via our CDK scripts
+The fastest and easiest way to try Hyperswitch on AWS is via our CDK scripts
 
 1. Click on the following button for a quick standalone deployment on AWS, suitable for prototyping.
    No code or setup is required in your system and the deployment is covered within the AWS free-tier setup.
 
-   <a href="https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=HyperswitchBootstarp&templateURL=https://hyperswitch-synth.s3.eu-central-1.amazonaws.com/hs-starter-config.yaml"><img src="./docs/imgs/aws_button.png" height="35"></a>
+   <a href="https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=HyperswitchBootstarp&templateURL=https://hyperswitch-synth.s3.eu-central-1.amazonaws.com/hs-starter-config.yaml"><img src="https://github.com/juspay/hyperswitch/blob/main/docs/imgs/aws_button.png?raw=true" height="35"></a>
 
 2. Sign-in to your AWS console.
 
-3. Follow the instructions provided on the console to successfully deploy Hyperswitch
+3. Follow the instructions provided on the console to successfully deploy Hyperswitch. This takes 30-45mins and gives the following output 
+
+| Service| Host|
+|----------------------------------------------|----------------------------------------------|
+| App server running on                        | `http://hyperswitch-<host-id.region>.elb.amazonaws.com` |
+| HyperloaderJS Hosted at                      | `http://<cloudfront.host-id>/0.103.1/v0/HyperLoader.js` |
+| Control center server running on             | `http://hyperswitch-control-center-<host-id.region>.elb.amazonaws.com`, Login with Email: `test@gmail.com` |
+| Hyperswitch Demo Store running on            | `http://hyperswitch-sdk-demo-<host-id.region>.elb.amazonaws.com` |
+| Logs server running on                       | `http://hyperswitch-logs-<host-id.region>.elb.amazonaws.com`, Login with username: `admin`, password: `admin` |
+
+We support deployment on GCP and Azure via Helm charts which takes 30-45mins. You can read more at [Hyperswitch docs](https://docs.hyperswitch.io/hyperswitch-open-source/deploy-on-kubernetes-using-helm). 
+
+### 3. Hosted Sandbox
+
+You can experience the product by signing up for our [hosted sandbox](https://app.hyperswitch.io/). The signup process accepts any email ID and provides access to the entire Control Center. You can set up connectors, define workflows for routing and retries, and even try payments from the dashboard.
 
 [docs-link-for-enterprise]: https://docs.hyperswitch.io/hyperswitch-cloud/quickstart
 [docs-link-for-developers]: https://docs.hyperswitch.io/hyperswitch-open-source/overview
@@ -101,43 +134,31 @@ The fastest and easiest way to try Hyperswitch is via our CDK scripts
 [local-setup-guide]: /docs/try_local_system.md
 [docker-compose-scheduler-monitoring]: /docs/try_local_system.md#running-additional-services
 
-<a href="https://app.hyperswitch.io/">
-  <h2 id="try-a-payment">⚡️ Try a Payment</h2>
-</a>
-
-To quickly experience the ease of Hyperswitch, sign up on the [Hyperswitch Control Center](https://app.hyperswitch.io/) and try a payment. Once you've completed your first transaction, you’ve successfully made your first payment with Hyperswitch!
 
-<a href="#community-contributions">
-  <h2 id="community-contributions">✅ Community & Contributions</h2>
+<a href="support-feature-requests">
+  <h2 id="support-feature-requests">Support, Feature requests & Bugs</h2>
 </a>
 
-The community and core team are available in [GitHub Discussions](https://github.com/juspay/hyperswitch/discussions), where you can ask for support, discuss roadmap, and share ideas.
+For any support, join the conversation in [Slack](https://join.slack.com/t/hyperswitch-io/shared_invite/zt-2jqxmpsbm-WXUENx022HjNEy~Ark7Orw)
 
-Our [Contribution Guide](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md) describes how to contribute to the codebase and Docs.
+For new product features, enhancements, roadmap discussions, or to share queries and ideas, visit our [GitHub Discussions](https://github.com/juspay/hyperswitch/discussions)
 
-Join our Conversation in [Slack](https://join.slack.com/t/hyperswitch-io/shared_invite/zt-2jqxmpsbm-WXUENx022HjNEy~Ark7Orw), [Discord](https://discord.gg/wJZ7DVW8mm), [Twitter](https://x.com/hyperswitchio)
+For reporting a bug, please read the issue guidelines and search for [existing and closed issues]. If your problem or idea is not addressed yet, please [open a new issue].
 
+[existing and closed issues]: https://github.com/juspay/hyperswitch/issues
+[open a new issue]: https://github.com/juspay/hyperswitch/issues/new/choose
 
-<a href="#Join-us-in-building-Hyperswitch">
-  <h2 id="join-us-in-building-hyperswitch">💪 Join us in building Hyperswitch</h2>
+<a href="our-vision">
+  <h2 id="our-vision">Our Vision</h2>
 </a>
 
-### 🤝 Our Belief
+> Linux for Payments
 
-> Payments should be open, fast, reliable and affordable to serve
-> the billions of people at scale.
+Payments are evolving rapidly worldwide, with hundreds of processors, fraud detection systems, authentication modules, and new payment methods and flows emerging. Businesses building or managing their own payment stacks often face similar challenges, struggle with comparable issues, and find it hard to innovate at the desired pace.
 
-Globally payment diversity has been growing at a rapid pace.
-There are hundreds of payment processors and new payment methods like BNPL,
-RTP etc.
-Businesses need to embrace this diversity to increase conversion, reduce cost
-and improve control.
-But integrating and maintaining multiple processors needs a lot of dev effort.
-Why should devs across companies repeat the same work?
-Why can't it be unified and reused? Hence, Hyperswitch was born to create that
-reusable core and let companies build and customise it as per their specific requirements.
+Hyperswitch serves as a well-architected designed reference platform, built on best-in-class design principles, empowering businesses to own and customize their payment stack. It provides a reusable core payments stack that can be tailored to specific requirements while relying on the Hyperswitch team for enhancements, support, and continuous innovation.
 
-### ✨ Our Values
+### Our Values
 
 1. Embrace Payments Diversity: It will drive innovation in the ecosystem in
    multiple ways.
@@ -150,33 +171,24 @@ reusable core and let companies build and customise it as per their specific req
 
 This project is being created and maintained by [Juspay](https://juspay.io)
 
-<a href="#Bugs and feature requests">
-  <h2 id="bugs-and-feature-requests">🐞 Bugs and feature requests</h2>
-</a>
-
-Please read the issue guidelines and search for [existing and closed issues].
-If your problem or idea is not addressed yet, please [open a new issue].
-
-[existing and closed issues]: https://github.com/juspay/hyperswitch/issues
-[open a new issue]: https://github.com/juspay/hyperswitch/issues/new/choose
-
-<a href="#Versioning">
-  <h2 id="versioning">🔖 Versioning</h2>
+<a href="#versioning">
+  <h2 id="versioning">Versioning</h2>
 </a>
 
 Check the [CHANGELOG.md](./CHANGELOG.md) file for details.
 
-<a href="#©Copyright and License">
-  <h2 id="copyright-and-license">©️ Copyright and License</h2>
+<a href="#copyright-and-license">
+  <h2 id="copyright-and-license">Copyright and License</h2>
 </a>
 
 This product is licensed under the [Apache 2.0 License](LICENSE).
 
-<a href="#Thanks to all contributors">
-  <h2 id="Thanks to all contributors">✨ Thanks to all contributors</h2>
+
+<a href="team-behind-hyperswitch">
+  <h2 id="team-behind-hyperswitch">Team behind Hyperswitch</h2>
 </a>
 
-Thank you for your support in hyperswitch's growth. Keep up the great work! 🥂
+The core team of 150+ engineers building Hyperswitch. Keep up the great work! 🥂
 
 <a href="https://github.com/juspay/hyperswitch/graphs/contributors">
   <img src="https://contributors-img.web.app/image?repo=juspay/hyperswitch" alt="Contributors"/>

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [X] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Update readme with vision, product offering, architecture diagram, setup steps and output

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->


## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [ ] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
