> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet/build-and-deploy.md). # Deploy Effortlessly deploy and configure eSignet with comprehensive guides, architecture insights, and mock environments. Effortlessly deploy and configure eSignet with comprehensive guides, architecture insights, and mock environments. The eSignet solution is designed to be: [**Easily deployed and tested locally**](https://github.com/mosip/documentation/blob/esignet/docs/build-and-deploy/local-deployment.md) using a Docker Compose–based setup for each module, allowing services to be brought up seamlessly on your machine. [**Deployed on-premise**](/home/esignet/build-and-deploy/deployment-guide.md), with full flexibility to configure eSignet as per your organization’s use cases and requirements. The latest stable codebase is available under the master branch of the eSignet repository. All feature development or bug fixes are typically carried out on dedicated feature or development branches. {% hint style="info" %} Note: For deployment and testing, it is recommended to use either the master branch or the official released tags. {% 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.esignet.io/home/esignet/build-and-deploy.md?ask=&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.