# gRPC pipeline component

> Configuration reference for the ZAPP grpcServer pipeline component.

---

LLMS index: [llms.txt](/datacenter/zapp/llms.txt)

---

Use `grpcServer` when a listener should expose telemetry directly to consumers. The component is terminal: it accepts pipeline input and serves the ZAPP gRPC service, but it does not produce downstream pipeline targets.

```yaml
components:
  grpc:
    type: grpcServer
    address: :9998
```

Important fields:

- `type` must be `grpcServer`
- `address` is the TCP listen address for the gRPC server

Accepted input types:

- `*timeseries.Model`
- `[]*zapp.Payload`

Use `grpcServer` for direct listener-to-consumer deployments. Use the ZAPP Aggregator consumer API when you need one endpoint that combines telemetry from multiple listeners.