> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/api-fundamentals/environments-capabilities.md).

# Environments Capabilities

Capabilities, Limitations, and Environment Differences

### Production Environment

The production environment is fully equipped and ready to support your operational needs, ensuring your data and traffic are handled efficiently.

* **Uptime Guarantee:** 99.9% uptime, ensuring reliable access.
* **Service Level Agreement (SLA):** Comprehensive SLA coverage included.
* **Upgrades:** Zero-downtime upgrades to minimize disruptions.
* **API Throughput:** Supports up to 1,200 concurrent requests per second with a soft limit (If you plan to send more RPS, please contact OpenLoyalty to discuss viable solutions). Beyond this threshold, application performance may decrease.
  * **Exceptions:** The `/api/admin/login_check` and `/api/token/refresh` endpoints are limited to 40 requests per minute (RPM).

{% hint style="warning" %}
The number of the maximum concurrent RPS in your environment might be lower, depending on multiple factors.

We recommend using fewer than the maximum number of concurrent RPS as this number may be affected by the objects configured in Open Loyalty (e.g. the number of achievements or campaigns triggered by the API call).
{% endhint %}

* **Regional Availability:** Services are available in the following regions:
  * `eu-west-1` (Dublin, Ireland)
  * `eu-central-1` (Frankfurt, Germany)
  * `us-east-2` (Ohio, USA)
  * `ap-southeast-1` (Singapore)
  * `ap-southeast-2` (Sydney, Australia)

{% hint style="info" %}
The region choice can affect your pricing. Please contact Open Loyalty for more information.
{% endhint %}

### Staging Environment

The staging environment is designed for proof of concept (PoC) integration and functional testing. It is not intended for performance testing due to resource constraints.

* **Uptime & SLA:** No guaranteed uptime or SLA provided.
* **Resources:** Limited resources available, with no scaling options.
* **Upgrades:** Zero-downtime upgrades are maintained.
* **Data Privacy:** Storing personally identifiable information (PII) is not recommended.
* **API Throughput:** Limited to 50 concurrent requests per second with a soft limit. Application performance may decrease beyond this limit.
  * **Exceptions:** The `/api/admin/login_check` and `/api/token/refresh` endpoints are limited to 20 RPM.
* **Regional Availability:** Services are available in the following regions **only**:
  * `eu-west-1` (Dublin, Ireland)
  * `us-east-2` (Ohio, USA)
  * `ap-southeast-2` (Sydney, Australia)

This delineation between environments ensures that you can develop and test with clarity, understanding the capabilities and limitations of each to best meet your development lifecycle needs.


---

# 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://help.openloyalty.io/technical-guide/api-fundamentals/environments-capabilities.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.