> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/hyperswitch-open-source/readme-1/unified-local-setup-using-docker/run-additional-services.md).

# Run Additional Services

The default behaviour for docker compose only runs the following services:

1. hyperswitch server
2. hyperswitch control center
3. hyperswitch web sdk
4. postgres
5. redis (standalone)

You can run the **scheduler, data and monitoring services** by specifying suitable profile names to the above Docker Compose command. To understand more about the hyperswitch architecture and the components involved, check out the [architecture document](https://github.com/juspay/hyperswitch/blob/main/docs/architecture.md).

* To run the scheduler components (consumer and producer), you can specify `--profile scheduler`:

  ```bash
  docker compose --profile scheduler up -d
  ```
* To run the monitoring services (Grafana, Promtail, Loki, Prometheus and Tempo), you can specify `--profile monitoring`:

  ```bash
  docker compose --profile monitoring up -d
  ```

  You can then access Grafana at `http://localhost:3000` and view application logs using the "Explore" tab, select Loki as the data source, and select the container to query logs from.
* To run the data services (Clickhouse, Kafka and Opensearch) you can specify the `olap` profile

  ```bash
  docker compose --profile olap up -d
  ```

  You can read more about using the data services [here](https://github.com/juspay/hyperswitch/blob/main/crates/analytics/docs/README.md)
* You can also specify multiple profile names by specifying the `--profile` flag multiple times. To run both the scheduler components and monitoring services, the Docker Compose command would be:

  ```bash
  docker compose --profile scheduler --profile monitoring up -d
  ```

Once the services have been confirmed to be up and running, you can proceed with [trying out our APIs](#try-out-our-apis).


---

# 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.hyperswitch.io/self-hosting/hyperswitch-open-source/readme-1/unified-local-setup-using-docker/run-additional-services.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.