OpenMessage vs Linq

OpenMessage supports 20 of the 77 features compared here, and Linq supports 63.

Feature comparison

Feature	OpenMessage	Linq
iMessage messaging
iMessage	Not supportedNo iMessage support; it only imports iMessage history	Supported
Group chats	Not supportedNo iMessage support	SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management	Not supported	SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo	Not supported	SupportedSet display_name and group_chat_icon on group chats.
Mentions	Not supported	SupportedGroup chats only. Notifies iMessage recipients even in a muted chat.
Tapbacks	Not supported	SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies	Not supported	Supportedreply_to with optional part_index. iMessage only.
Typing indicators	Not supported	SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts	Not supported	SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend	Not supported	PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects	Not supported	Supported11 screen and 4 bubble effects.
Animated text effects	Not supported	Supportedtext_decorations animations: big, small, shake, nod, explode, ripple, bloom, jitter.
Stickers	Not supported	SupportedPeel emoji or images onto messages, send stickers, or place them inline in text.
Formatted text	Not supported	SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments	Not supported	SupportedUp to 10MB by URL, 100MB with pre-upload.
Live Photos	Not supported	Not listed
Rich link previews	Not supported	Supportedlink parts render as rich previews on iMessage and RCS.
Voice messages	Not supported	SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards	Not supported	SupportedSend .vcf files as media parts.
Polls	Not supported	SupportedCreate, add options, vote and read tallies, with poll webhooks. Not as a chat's first message.
Chat backgrounds	Not supported	SupportedColor, animated or photo backgrounds, in direct and group chats.
Location sharing	Not supported	SupportedRequest, read and stop Find My shares. Live location is a $79/mo add-on on Pro.
iMessage apps	Not supported	SupportedPro plan. Cards from your own Messages extension, or Linq-hosted cards (Experiences).
Live app cards	Not supported	SupportedUpdate App Card replaces a delivered iMessage app or Experience card in place.
Sender name and photo	Not supported	SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls	Not supported	Not supportedDocs say the API does not place or answer calls.
Delivery status	Not supported	Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check	Not supported	Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway	Not supported	Not listed
Numbers and delivery
Managed lines	Not supportedRuns on your own machine with your own phone and accounts	Supported
Dedicated numbers	Not supportedNot offered; it uses your own phone number	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	SupportedPairs with your Android phone's Google Messages and your WhatsApp and Signal	Not listed
Line pooling	Not listed	SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback	Not supportedNo iMessage support	Supported
RCS fallback	Not supported	SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging	Supportedsend_message texts a phone number directly over SMS/RCS, WhatsApp or Signal	SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number	Not supportedNo iMessage support	PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS	SupportedSMS, with media, through a paired Android phone running Google Messages	Supported
RCS	SupportedRCS through a paired Android phone running Google Messages	Supported
WhatsApp	SupportedLinks as a WhatsApp companion device on your machine	BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram	Not supportedNot offered	Not supportedNot offered
Slack	Not supported	Not supported
Email	Not supported	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 local inbox and one set of MCP tools across SMS/RCS, WhatsApp and Signal	PartialiMessage, RCS and SMS share one API. WhatsApp is a separate API with its own keys and SDKs.
Developer tools
REST API	PartialLoopback-only local HTTP API behind the web UI, described in the agent runbook	Supported
TypeScript SDK	Not supportedNo SDK; MCP, CLI and local web UI only	Supported@linqapp/sdk
Python SDK	Not supported	Supportedlinq-python
Other SDKs	Not supported	SupportedOfficial Go SDK.
CLI	Supportedopenmessage pair, serve, read, thread, send, send-group and import	Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks	Not listed	Supported
Signed webhooks	Not listed	SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server	SupportedLocal MCP over stdio, Streamable HTTP or SSE	Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source	SupportedLICENSE file is the Unlicense; README and site say MIT	PartialSDKs, CLI and adapters are Apache-2.0 or MIT on GitHub. The messaging platform is closed.
Self-hosting	SupportedRuns only on your own machine; no hosted service	Not supportedLinq describes itself as fully managed, in contrast to self-hosted options.
Local testing	PartialDemo mode seeds fake SMS and WhatsApp threads with live sync turned off	Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers	Not listed	Not listed
Event replay	PartialStartup backfill pulls SMS/RCS history from the phone after downtime; no webhooks	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 listed	PartialNo own framework. Maintains a Vercel Chat SDK adapter and OpenClaw and Hermes plugins.
Agent framework integrations	PartialClaude Code plugin and MCP setup; no agent 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	Supporteddraft_message saves a draft for a person to review and send in the app	Not listed
Audit logs	Not listed	SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API	SupportedFull local history with search, per conversation and per person	Supported
Plans and compliance
Free plan	SupportedFree and open source	SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing	SupportedSite lists the price as free	SupportedPro from $260/mo. Enterprise is custom.
No per-message fees	SupportedFree software; carrier charges on your own phone plan still apply	Supported
Uptime SLA	Not supportedUnlicense software provided as is, without warranty	SupportedContractual SLAs on the Enterprise plan; marketing cites 99.95%
Isolated infrastructure	SupportedMessages, contacts and sessions stay on your machine	SupportedDedicated lines across 4 data centers on paid plans; Hobby uses a shared line
SOC 2 Type II	Not listedLocal software; compliance depends on the user	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 OpenMessage if you need bring your own number, self-hosting, local testing and human handoff.

Choose Linq if you need iMessage, group chats, group management and group name and photo.

Frequently asked questions

• Photon vs OpenMessage

• 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