Limits and capacity

These are SDK defaults and bounds, not throughput guarantees. Qualify radios, storage and OS background execution on the deployment hardware. Configuration overrides are listed in configuration types.

Resource	Default or ceiling
Direct message content	256 KiB; use media or file transfer for larger payloads
Transport frame / group payload	1 MiB
Outbound pre-session queue	64 messages / 2 MiB per peer; 4,096 / 16 MiB global; 7 days
Initial TTL	8 hops; dense mode 5
Pending decryption queue	64 / 4 MiB per peer, 4,096 / 32 MiB global; 24-hour process TTL
Pending acknowledgments	1,000; 10-second timeout
Retries	10; backoff from 1 second to 300 seconds
Outbox	500 entries; 7 days
Deduplication	2,000 entries; 24 hours
Mesh forwarding	10/second, burst 30; per peer 5/second, burst 15
File chunk default	32 KiB
Media chunk	4 KiB over BLE; 256 KiB over internet
File size	100 MiB
File assembly	32 concurrent; 128 MiB buffered
Group membership	256 members
Group attachment fetch	1 MiB
Document	1 MiB; warning at 768 KiB
Document sync frame	32 KiB
Peer-named documents	1,024 per space
Interest patterns	32 per space
Username	64 bytes
Identifier	256 bytes

Capacity exhaustion must be visible to the application. Handle errors, persist business work separately and avoid retrying beyond its validity window. An SDK acknowledgment does not establish durable application acceptance. Hosted API rate limits and hosted usage quotas are separate from local mesh bounds. See HTTP API rate limits and hosted services. Local peer-to-peer traffic is never metered on any plan.

SDK setup

API by task

Types and events

Architecture