> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/start-here/install/local.md).

# Local

Start a Pinot cluster on your local machine.

## Outcome

Start a multi-component Pinot cluster directly on your machine without containers.

## Prerequisites

* JDK 25 or later (required for building and running Pinot services)
* Apache Maven 3.6+ (only if building from source)

{% hint style="info" %}
**Note:** The SPI and Java/JDBC client modules (`pinot-spi`, `pinot-java-client`, `pinot-jdbc-client`) remain compatible with Java 11 for external JVM consumers.
{% endhint %}

## Steps

### 1. Download or build Apache Pinot

{% tabs %}
{% tab title="Download release" %}

```bash
export PINOT_VERSION=1.5.1

wget https://downloads.apache.org/pinot/apache-pinot-${PINOT_VERSION}/apache-pinot-${PINOT_VERSION}-bin.tar.gz
```

See the [Version reference](/start-here/pinot-versions.md) page for the current stable release.

Extract and enter the directory:

```bash
tar -zxvf apache-pinot-${PINOT_VERSION}-bin.tar.gz
cd apache-pinot-${PINOT_VERSION}-bin
```

{% endtab %}

{% tab title="Build from source" %}
{% hint style="info" %}
**Prerequisite:** Install [Apache Maven](https://maven.apache.org/install.html) 3.6 or higher.
{% endhint %}

```bash
git clone https://github.com/apache/pinot.git
cd pinot
mvn install package -DskipTests -Pbin-dist
cd build
```

{% endtab %}

{% tab title="Homebrew" %}

```bash
brew install pinot
```

{% endtab %}
{% endtabs %}

### 2. Start ZooKeeper

```bash
./bin/pinot-admin.sh StartZookeeper \
  -zkPort 2181
```

### 3. Start Pinot Controller

```bash
export JAVA_OPTS="-Xms4G -Xmx8G"
./bin/pinot-admin.sh StartController \
    -zkAddress localhost:2181 \
    -controllerPort 9000
```

### 4. Start Pinot Broker

```bash
export JAVA_OPTS="-Xms4G -Xmx4G"
./bin/pinot-admin.sh StartBroker \
    -zkAddress localhost:2181
```

### 5. Start Pinot Server

```bash
export JAVA_OPTS="-Xms4G -Xmx16G"
./bin/pinot-admin.sh StartServer \
    -zkAddress localhost:2181
```

### 6. Start Pinot Minion (optional)

```bash
export JAVA_OPTS="-Xms4G -Xmx4G"
./bin/pinot-admin.sh StartMinion \
    -zkAddress localhost:2181
```

### 7. Start Kafka (optional)

Only needed if you plan to ingest real-time streaming data.

```bash
./bin/pinot-admin.sh StartKafka \
  -zkAddress=localhost:2181/kafka \
  -port 19092
```

## Verify

Check that the Controller is healthy:

```bash
curl localhost:9000/health
```

The response should return `OK`. You can also open the Pinot Query Console at <http://localhost:9000>.

## Next step

Your cluster is running. Continue to [First table and schema](/start-here/first-table-and-schema.md) to load data.


---

# 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.pinot.apache.org/start-here/install/local.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.