beeperbox vs Linq

beeperbox supports 27 of the 77 features compared here, and Linq supports 63.

Feature comparison

Feature	beeperbox	Linq
iMessage messaging
iMessage	PartialLists iMessage, but Beeper connects iMessage only on a Mac, so the Linux container cannot	Supported
Group chats	PartialReads and sends to any connected chat, groups included; iMessage reach needs a Mac	SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management	Not listed	SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo	Not listed	SupportedSet display_name and group_chat_icon on group chats.
Mentions	Not listed	SupportedGroup chats only. Notifies iMessage recipients even in a muted chat.
Tapbacks	Partialreact_to_message adds an emoji reaction; reading reactions is not documented	SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies	Partialsend_message takes reply_to_message_id; per-network rendering is not documented	Supportedreply_to with optional part_index. iMessage only.
Typing indicators	Not listed	SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts	Not listedDocs say Beeper exposes no mark-as-read; read state is not in the message schema	SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend	PartialEdit and delete only through the raw Beeper Desktop API, not the MCP tools	PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects	Not listed	Supported11 screen and 4 bubble effects.
Animated text effects	Not listed	Supportedtext_decorations animations: big, small, shake, nod, explode, ripple, bloom, jitter.
Stickers	Not listed	SupportedPeel emoji or images onto messages, send stickers, or place them inline in text.
Formatted text	Partialsend_message accepts Markdown; how each network renders it is not documented	SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments	PartialDownload inbound files over MCP; sending files needs the raw Beeper API upload	SupportedUp to 10MB by URL, 100MB with pre-upload.
Live Photos	Not listed	Not listed
Rich link previews	Not listed	Supportedlink parts render as rich previews on iMessage and RCS.
Voice messages	PartialInbound voice notes are flagged and downloadable; sending them is not documented	SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards	Not listed	SupportedSend .vcf files as media parts.
Polls	Not listed	SupportedCreate, add options, vote and read tallies, with poll webhooks. Not as a chat's first message.
Chat backgrounds	Not listed	SupportedColor, animated or photo backgrounds, in direct and group chats.
Location sharing	Not listed	SupportedRequest, read and stop Find My shares. Live location is a $79/mo add-on on Pro.
iMessage apps	Not listed	SupportedPro plan. Cards from your own Messages extension, or Linq-hosted cards (Experiences).
Live app cards	Not listed	SupportedUpdate App Card replaces a delivered iMessage app or Experience card in place.
Sender name and photo	Not listed	SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls	Not listed	Not supportedDocs say the API does not place or answer calls.
Delivery status	PartialSend returns status sent; docs say to read the chat back to confirm delivery	Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check	Not listed	Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway	Not listed	Not listed
Numbers and delivery
Managed lines	Not supportedYou run Beeper Desktop on your own host with your own accounts	Supported
Dedicated numbers	Not supportedNot offered; it uses the accounts in your Beeper login	SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers	Not supportedNot offered	SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number	SupportedUses the networks already connected to your Beeper account	Not listed
Line pooling	Not supportedSingle-tenant by design: one container per Beeper account	SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback	Not listed	Supported
RCS fallback	Not listed	SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging	Partialsend_message needs an existing chat_id; no MCP tool starts a new chat	SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number	Not listed	PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS	PartialOnly through Beeper's Google Messages network; no numbers are provided	Supported
RCS	Not listedGoogle Messages is listed as a network; RCS is not mentioned	Supported
WhatsApp	SupportedThrough the WhatsApp network in your Beeper account	BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram	SupportedThrough the Telegram network in your Beeper account	Not supportedNot offered
Slack	SupportedThrough the Slack network in your Beeper account	Not supported
Email	Not supportedNot offered	Not supportedNot offered. iMessage can be sent to Apple ID email handles.
Phone calls	Not supported	PartialAPI does not place or answer calls; it forwards inbound calls. Calling lives in the Linq Blue app.
Apple Messages for Business	Not supported	Not listedAI context page mentions it, but no product page or docs were found.
Unified channel API	SupportedOne normalized Chat and Message schema across every network	PartialiMessage, RCS and SMS share one API. WhatsApp is a separate API with its own keys and SDKs.
Developer tools
REST API	SupportedRaw Beeper Desktop HTTP API on port 23373, plus MCP over HTTP JSON-RPC	Supported
TypeScript SDK	Not supportedNo SDK; the npm package is the MCP server itself	Supported@linqapp/sdk
Python SDK	Not supportedNo SDK; MCP and raw HTTP only	Supportedlinq-python
Other SDKs	Not supported	SupportedOfficial Go SDK.
CLI	Not supportednpx beeperbox only starts the MCP server	Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks	Not supportedPolling only through poll_messages; docs say the raw API is request and response only	Supported
Signed webhooks	Not supportedNo webhooks	SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server	Supported12 tools over HTTP or stdio, in Docker or with npx	Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source	SupportedApache-2.0	PartialSDKs, CLI and adapters are Apache-2.0 or MIT on GitHub. The messaging platform is closed.
Self-hosting	SupportedDocker image for amd64 and arm64 Linux, or npx against a local Beeper Desktop	Not supportedLinq describes itself as fully managed, in contrast to self-hosted options.
Local testing	Not listed	Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers	Not listed	Not listed
Event replay	PartialRestart-safe poll cursor; more than 100 messages per chat between polls can be missed	PartialRetries for 30 minutes; after that, re-fetch chats or ask Linq for a manual replay.
OpenTelemetry	Not listed	PartialW3C trace IDs on every response and webhook for OTel backends. No export of Linq spans by default.
No-code integrations	Not listed	SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations	Not listed	SupportedVia Linq Blue: GoHighLevel, HubSpot and Salesforce.
Built for AI agents
Agent framework	Not listedTool layer only; the author's separate bareagent project provides the agent loop	PartialNo own framework. Maintains a Vercel Chat SDK adapter and OpenClaw and Hermes plugins.
Agent framework integrations	PartialWiring guides for MCP clients and the author's bareagent; no framework adapters	SupportedLinq-maintained Vercel Chat SDK adapter, plus OpenClaw and Hermes Agent plugins.
Streaming replies	Not listed	Not supportedDocs say the Chat SDK adapter buffers streams into one final message.
Agent group chats	Not listed	Not listed
Human handoff	Not listed	Not listed
Audit logs	Not listed	SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API	Supportedread_chat and search_messages; live sync covers about 20 recent chats	Supported
Plans and compliance
Free plan	SupportedFree Apache-2.0 software; needs a Beeper account	SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing	SupportedFree software	SupportedPro from $260/mo. Enterprise is custom.
No per-message fees	Supported	Supported
Uptime SLA	Not supportedApache-2.0 software provided without warranty; uptime is up to you	SupportedContractual SLAs on the Enterprise plan; marketing cites 99.95%
Isolated infrastructure	SupportedOne container per Beeper account on your own host	SupportedDedicated lines across 4 data centers on paid plans; Hobby uses a shared line
SOC 2 Type II	Not listedSelf-hosted; compliance depends on the operator	SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR	Not listed	SupportedDPA covers GDPR and UK GDPR, with Standard Contractual Clauses.

Checked on each provider's own site and docs on 2026-10-25. “Not listed” means the provider does not mention it.

Pricing

Which should you choose?

Choose beeperbox if you need bring your own number, Telegram, Slack and self-hosting.

Choose Linq if you need group management, group name and photo, mentions and typing indicators.

Frequently asked questions

• Photon vs beeperbox

• Photon vs Linq
• Blooio vs Linq
• Sendblue vs Linq
• Zernio vs Linq
• LoopMessage vs Linq
• Blue Reacher vs Linq
• Chert vs Linq
• Miss Blue vs Linq
• Bland vs Linq
• BlueBubbles vs Linq