Type-safe RPC over
Bluetooth Low Energy

message EchoRequest  { string message = 1; }
message EchoResponse { string message = 1; }

let client = BlerpcClient()
try await client.connect(device: devices[0])
let res = try await client.echo(message: "hello")
print(res.message)  // "hello"

val client = BlerpcClient(context)
client.connect(devices[0])
val res = client.echo(message = "hello")
println(res.message)  // "hello"

final client = BlerpcClient();
await client.connect(devices[0]);
final res = await client.echo(message: 'hello');
print(res.message);  // "hello"

const client = new BlerpcClient()
await client.connect(devices[0])
const res = await client.echo({ message: 'hello' })
console.log(res.message)  // "hello"

client = BlerpcClient()
await client.connect(devices[0])
resp = await client.echo(message="hello")
print(resp.message)  # "hello"

blerpc_EchoResponse resp;
int ret = blerpc_echo("hello", &resp);
if (ret == 0)
    printk("%s\n", resp.message);  // "hello"

Features

Architecture

How It Works

bleRPC provides a layered protocol stack on top of BLE GATT:

1. Command Layer — Wraps Protocol Buffers payloads with command metadata (name, type, data length).
2. Encryption Layer (optional) — Encrypts the serialized command with AES-128-GCM after a 4-step key exchange.
3. Container Layer — Fragments payloads into MTU-sized containers for BLE transmission, with reassembly on the receiving side.

All communication uses a single GATT Characteristic: the Central writes requests via Write Without Response and receives responses via Notify.

Read the full protocol specification →

Benchmarks

Real-world throughput

Measured against an nRF54L15 DK peripheral with E2E encryption enabled (AES-128-GCM), MTU 247 — flash-read throughput.

Ecosystem

Supported Platforms

Central (Client)

Peripheral (Server)

Protocol Libraries