Project Blue vs Linq

Compare Project Blue and Linq side by side: iMessage features, channels, developer tools, pricing and compliance, checked on each provider's own site.

Project Blue

iMessage, SMS and FaceTime Audio lines inside your CRM
Starting price
$166/month per line, billed annually
Free plan
Free trial on a shared line, verified numbers only

Linq

iMessage, RCS and SMS API with flat monthly pricing
Starting price
$260/month (Pro)
Free plan
Hobby: $0, up to 20 contacts, used through the CLI

Project Blue supports 42 of the 77 features compared here, and Linq supports 63.

Feature comparison

FeatureProject BlueLinq
iMessage messaging
iMessage
Supported
Supported
Group chats
SupportedSend to groups of 2 to 32 by API. Not on trial accounts, and group sends do not sync to the CRM.
SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management
PartialGroups are created by sending to a set of numbers. No add or remove member endpoints documented.
SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo
PartialgroupName can be set when a group is created. No group photo documented.
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
PartialSend or remove the six classic tapbacks on inbound iMessages. Receiving reactions is not documented.
SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies
Not listed
Supportedreply_to with optional part_index. iMessage only.
Typing indicators
PartialSend only, iMessage only, into an existing conversation. Inbound typing events not documented.
SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts
Not listed
SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend
Not listed
PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects
Supported4 bubble and 9 screen effects through the effect field. iMessage only.
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
Not listed
SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments
SupportedImages, videos and vCards by URL.
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
SupportedAudio files sent as voice memos, plus AI text-to-speech voice memos.
SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards
SupportedVCF files through mediaAttachmentUrl.
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
SupportedSet, read and share a line's Share Name and Photo card by API.
SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls
PartialFaceTime Audio only, outbound and inbound, on FaceTime-enabled accounts. Not on trials.
Not supportedDocs say the API does not place or answer calls.
Delivery status
PartialMessages carry a status field such as delivered. Webhooks cover only inbound and outbound messages.
Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check
Supported
Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedNo iPhone, Mac or SIM needed. Lines are set up remotely, usually within one business day.
Supported
Dedicated numbers
SupportedA dedicated line per rep, never shared. New lines are requested by API and provisioned by the team.
SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers
PartialTrial accounts only: a shared line that can reach verified numbers.
SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number
SupportedExisting numbers can be ported to Project Blue's carrier partner.
Not listed
Line pooling
SupportedSends without lineId are load balanced across your lines.
SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback
SupportedFalls back to SMS from the same line when iMessage is unavailable.
Supported
RCS fallback
Not listedHomepage describes fallback from iMessage to WhatsApp to SMS. RCS fallback is not described.
SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging
SupportedLines are sold as outbound-ready. Guidelines rule out mass outbound iMessage.
SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number
SupportedDialer and FaceTime Audio calls from the same number as the messaging line.
PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS
Supported
Supported
RCS
PartialRCS for rich media was rolled out in 2026. The API lists RCS as inbound only.
Supported
WhatsApp
PartialHomepage lists WhatsApp as a fallback step. No WhatsApp option in the API, and llms.txt says it is not a WhatsApp API.
BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram
Not supportedNot offered
Not supportedNot offered
Slack
PartialSlack notifications for inbound replies. Not a messaging channel.
Not supported
Email
Not supportedDeveloper page says it is not a general email API.
Not supportedNot offered. iMessage can be sent to Apple ID email handles.
Phone calls
SupportedCloud dialer with inbound, outbound, routing, recording and voicemail, plus a browser calling SDK.
PartialAPI does not place or answer calls; it forwards inbound calls. Calling lives in the Linq Blue app.
Apple Messages for Business
Not supportedNot offered
Not listedAI context page mentions it, but no product page or docs were found.
Unified channel API
PartialOne send endpoint covers iMessage and SMS. Calls and FaceTime use separate endpoints.
PartialiMessage, RCS and SMS share one API. WhatsApp is a separate API with its own keys and SDKs.
Developer tools
REST API
SupportedREST API with Bearer keys and an OpenAPI spec.
Supported
TypeScript SDK
Partial@tryprojectblue/dialer is a browser SDK for phone calls only. No messaging SDK.
Supported@linqapp/sdk
Python SDK
Not listed
Supportedlinq-python
Other SDKs
Not listed
SupportedOfficial Go SDK.
CLI
Not listed
Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks
SupportedInbound and outbound message events and inbound FaceTime call events.
Supported
Signed webhooks
Not listedWebhook docs do not mention signatures.
SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server
SupportedRemote MCP server with OAuth 2.1, plus an optional Claude Code plugin.
Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source
PartialThe dialer SDK is MIT licensed on npm. The platform is closed.
PartialSDKs, CLI and adapters are Apache-2.0 or MIT on GitHub. The messaging platform is closed.
Self-hosting
Not listedHosted service on Project Blue lines. Self-hosting is not mentioned.
Not supportedLinq describes itself as fully managed, in contrast to self-hosted options.
Local testing
Not listedTrial accounts send real messages to verified numbers; docs say they are not a simulator.
Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers
Not listed
Not listed
Event replay
Not supportedDocs say webhooks have no retries and failed deliveries are not replayed.
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
SupportedGoHighLevel conversation provider with workflow actions and triggers. llms.txt also lists Zapier.
SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations
SupportedHubSpot and Close CRM. Salesforce is 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
Not listed
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
PartialReps reply in the CRM inbox and can join group threads. No agent handoff controls documented.
Not listed
Audit logs
Not listed
SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API
SupportedList and get messages, inbound and outbound, with filters.
Supported
Plans and compliance
Free plan
PartialFree trial on a shared line to verified numbers. Some endpoints are off on trial.
SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing
Supported$166/month per line billed annually, or $199/month per line on a 12-month plan.
SupportedPro from $260/mo. Enterprise is custom.
No per-message fees
SupportedFlat per-line pricing with unlimited texting under fair use.
Supported
Uptime SLA
Not listedSite cites a 99.9% uptime record and a public status page. No contractual SLA found.
SupportedContractual SLAs on the Enterprise plan; marketing cites 99.95%
Isolated infrastructure
PartialEach rep gets a dedicated line that is never shared. Other infrastructure is not described.
SupportedDedicated lines across 4 data centers on paid plans; Hobby uses a shared line
SOC 2 Type II
Not listed
SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR
PartialPrivacy policy lists GDPR and UK GDPR rights. No DPA found.
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

Project Blue

Flat per-line pricing: $166 a month per line billed annually or $199 a month per line on a 12-month plan, with a free trial on a shared line.

Pricing model: flat per line

Source

Linq

Hobby is free with up to 20 contacts through the CLI, Pro starts at $260 a month with a 7-day free trial, and Enterprise is custom.

Pricing model: flat monthly, no per-message fees

Source

Which should you choose?

Choose Project Blue if you need FaceTime calls, bring your own number, Slack and human handoff.

Choose Linq if you need mentions, threaded replies, read receipts and edit and unsend.

Frequently asked questions