> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/development-guide/hackle-proxy.md).

# Hackle Proxy (Deprecated)

This document provides instructions for installing and using Hackle Proxy.

{% hint style="success" %}
If you are using a development platform supported by the SDK, using the SDK is recommended.
{% endhint %}

## 1. Overview

Hackle Proxy is a standalone service for centrally calling the Hackle service. You can use the features provided by the Hackle SDK through the Proxy REST API.

![1690](/files/iOcyNHOVScApaK5T1In4)

## 2. When should I use Hackle Proxy?

If your development platform is not supported by the Hackle SDK, you can integrate using Hackle Proxy. If an SDK is available for your development platform, using that SDK is recommended. In special cases such as PHP, it may be used alongside an SDK.

You can find the list of development platforms supported by the SDK in the [SDK documentation](/en/development-guide/sdk.md).

## 3. Best Practices

These are best practices for situations that generally need to be considered, though they may vary by circumstance.

### 3.1 How many Proxy instances should I deploy?

Generally, the Proxy is implemented to scale from low-spec hardware. For a stable configuration, it is recommended to deploy at least 2 instances.

### 3.2 Using a Load Balancer

It is recommended to use a load balancer for traffic routing to enable stable scaling of Proxy instances. If you use AWS, you can use AWS Elastic Load Balancer to stably scale Proxy instances as internal traffic increases.


---

# 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.hackle.io/en/development-guide/hackle-proxy.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.