# IMQServiceOptions.local property · @imqueue/rpc

Source: https://imqueue.org/api/rpc/latest/rpc.imqserviceoptions.local/
Published: 2026-11-12
Author: @imqueue maintainers (https://github.com/imqueue)
Package: @imqueue/rpc 3.11.0 — generated reference, not hand-written

Serve this service in process as well: a client in the same process calls it directly, with no trip through the queue.

**Signature:**

```typescript
local?: boolean;
```

## Default Value

false

## Remarks

The queue is still served, so a client in another process, a delayed call and `publish()` work as before, and turning this off again changes nothing a caller sees. An in-process call copies its request and its answer through JSON exactly as the queue does, so dates, class instances and `undefined` arrive as they would have; see [wireCopy()](https://imqueue.org/api/rpc/latest/rpc.wirecopy/).

A service served in process belongs to the process that hosts it: it installs no signal handlers and does not drain (the host's shutdown decides when it is destroyed), its queue installs none either, and it starts no metrics server. It cannot be combined with [IMQServiceOptions.multiProcess](https://imqueue.org/api/rpc/latest/rpc.imqserviceoptions.multiprocess/).