> 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/remote-configs/remote-config.md).

# Remote Config Introduction

## What is Remote Config?

Remote Config lets you update your service without a deployment.

Running a service requires continuous updates and improvements.

* Updating a service involves multiple steps — development, review, deployment, store upload, and more — making it difficult to respond in real time to issues discovered after release.
* Even after releasing a new version of your app, if users do not update immediately, the changes are not applied, which can result in outdated information being displayed.

{% hint style="info" %}
**With Hackle Remote Config, you can instantly modify various configuration values directly from the Dashboard without a deployment, and apply them to your service immediately.**
{% endhint %}

![2160](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-1c36ef04fb22a0607a47096262d57167747a93ae%2F22f4394-rc-kor_339bf5fa26b03875.png?alt=media)

## Who needs Remote Config?

Remote Config is not just for developers.

* Game planners, operations managers, and PMs/POs who want to quickly push a notice to users when a service issue occurs
* Marketers who want to manage holiday promotion popups without involving a developer
* Designers who want to update promotion images
* System administrators who want to test different environments without code changes or builds

Beyond these roles, many other teams can use Remote Config to apply changes to the service on their own, without going through developers.


---

# 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.hackle.io/en/remote-configs/remote-config.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.
