Blue Reacher vs Project Blue

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

Blue Reacher

Managed iMessage lines for B2B sales, with API and MCP
Starting price
$199/month per line at 4+ lines; $249/month for 1 to 3 lines
Free plan
Free public sandbox key; simulator only, no real sends

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

Blue Reacher supports 50 of the 77 features compared here, and Project Blue supports 42.

Feature comparison

FeatureBlue ReacherProject Blue
iMessage messaging
iMessage
SupportedOne-to-one iMessage sends and replies over REST and webhooks.
Supported
Group chats
PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.
SupportedSend to groups of 2 to 32 by API. Not on trial accounts, and group sends do not sync to the CRM.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
PartialGroups are created by sending to a set of numbers. No add or remove member endpoints documented.
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
PartialgroupName can be set when a group is created. No group photo documented.
Mentions
Not listed
Not listed
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
PartialSend or remove the six classic tapbacks on inbound iMessages. Receiving reactions is not documented.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
Not listed
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
PartialSend only, iMessage only, into an existing conversation. Inbound typing events not documented.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
Not listed
Edit and unsend
Not listed
Not listed
Message effects
Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.
Supported4 bubble and 9 screen effects through the effect field. iMessage only.
Animated text effects
Not listed
Not listed
Stickers
Not listed
Not listed
Formatted text
Not supportedDocs say there is no Markdown rendering on any channel.
Not listed
Attachments
SupportedOne file per message for now. Images and video up to 100 MB, audio and PDF up to 25 MB.
SupportedImages, videos and vCards by URL.
Live Photos
Not listed
Not listed
Rich link previews
SupportedA bare URL renders as a preview card on iMessage, built on the recipient's device.
Not listed
Voice messages
PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedAudio files sent as voice memos, plus AI text-to-speech voice memos.
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
SupportedVCF files through mediaAttachmentUrl.
Polls
Not listed
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
Not listed
Not listed
iMessage apps
Not listed
Not listed
Live app cards
Not listed
Not listed
Sender name and photo
Not listedDocs say recipients see only the number until they save your contact card.
SupportedSet, read and share a line's Share Name and Photo card by API.
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
PartialFaceTime Audio only, outbound and inbound, on FaceTime-enabled accounts. Not on trials.
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
PartialMessages carry a status field such as delivered. Webhooks cover only inbound and outbound messages.
iMessage availability check
PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.
Supported
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedEach line is an Apple ID on Apple hardware run by Blue Reacher.
SupportedNo iPhone, Mac or SIM needed. Lines are set up remotely, usually within one business day.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
SupportedA dedicated line per rep, never shared. New lines are requested by API and provisioned by the team.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
PartialTrial accounts only: a shared line that can reach verified numbers.
Bring your own number
SupportedPricing lists port-in support for an existing number.
SupportedExisting numbers can be ported to Project Blue's carrier partner.
Line pooling
SupportedOmit the line on a send and load balancing picks one; the site calls it smart routing.
SupportedSends without lineId are load balanced across your lines.
SMS fallback
Supported
SupportedFalls back to SMS from the same line when iMessage is unavailable.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
Not listedHomepage describes fallback from iMessage to WhatsApp to SMS. RCS fallback is not described.
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
SupportedLines are sold as outbound-ready. Guidelines rule out mass outbound iMessage.
Calls on the iMessage number
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
SupportedDialer and FaceTime Audio calls from the same number as the messaging line.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
Supported
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
PartialRCS for rich media was rolled out in 2026. The API lists RCS as inbound only.
WhatsApp
Not supportedNot offered
PartialHomepage lists WhatsApp as a fallback step. No WhatsApp option in the API, and llms.txt says it is not a WhatsApp API.
Telegram
Not supported
Not supportedNot offered
Slack
Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.
PartialSlack notifications for inbound replies. Not a messaging channel.
Email
Not supportedNot offered. Docs say there is no email-address sender option.
Not supportedDeveloper page says it is not a general email API.
Phone calls
PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.
SupportedCloud dialer with inbound, outbound, routing, recording and voicemail, plus a browser calling SDK.
Apple Messages for Business
Not supportedNot offered; the site describes it as a separate Apple product.
Not supportedNot offered
Unified channel API
SupportediMessage and SMS fallback share one send endpoint and message model.
PartialOne send endpoint covers iMessage and SMS. Calls and FaceTime use separate endpoints.
Developer tools
REST API
Supported
SupportedREST API with Bearer keys and an OpenAPI spec.
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Partial@tryprojectblue/dialer is a browser SDK for phone calls only. No messaging SDK.
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
Not listed
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
Not listed
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
Not listed
Webhooks
Supported
SupportedInbound and outbound message events and inbound FaceTime call events.
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
Not listedWebhook docs do not mention signatures.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
SupportedRemote MCP server with OAuth 2.1, plus an optional Claude Code plugin.
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.
PartialThe dialer SDK is MIT licensed on npm. The platform is closed.
Self-hosting
Not listed
Not listedHosted service on Project Blue lines. Self-hosting is not mentioned.
Local testing
SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.
Not listedTrial accounts send real messages to verified numbers; docs say they are not a simulator.
Custom channel providers
Not listed
Not listed
Event replay
PartialRetries for about a day; undelivered events are kept and support replays them on request.
Not supportedDocs say webhooks have no retries and failed deliveries are not replayed.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.
SupportedGoHighLevel conversation provider with workflow actions and triggers. llms.txt also lists Zapier.
CRM integrations
SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).
SupportedHubSpot and Close CRM. Salesforce is not listed.
Built for AI agents
Agent framework
PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.
Not listed
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
Not listed
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not listed
Human handoff
SupportedPause or snooze the AI assistant per contact while a person replies.
PartialReps reply in the CRM inbox and can join group threads. No agent handoff controls documented.
Audit logs
PartialDocs mention an exportable opt-out audit trail; no general activity log is documented.
Not listed
Message history API
SupportedConversation history per contact, cursor-paginated.
SupportedList and get messages, inbound and outbound, with filters.
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
PartialFree trial on a shared line to verified numbers. Some endpoints are off on trial.
Public pricing
Supported
Supported$166/month per line billed annually, or $199/month per line on a 12-month plan.
No per-message fees
Supported
SupportedFlat per-line pricing with unlimited texting under fair use.
Uptime SLA
Not listed
Not listedSite cites a 99.9% uptime record and a public status page. No contractual SLA found.
Isolated infrastructure
SupportedDedicated lines per customer, never shared; workspaces logically isolated.
PartialEach rep gets a dedicated line that is never shared. Other infrastructure is not described.
SOC 2 Type II
Not supportedTrust page says controls map to SOC 2 but the independent attestation is not complete.
Not listed
GDPR
SupportedGDPR page and a published DPA with Standard Contractual Clauses.
PartialPrivacy policy lists GDPR and UK GDPR rights. No DPA found.

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

Pricing

Blue Reacher

Lines are $249 a month each plus a $449 activation fee, $199 a month each at 4 or more lines, or $1,949 per line per year with activation waived.

Pricing model: flat per line, no per-message fees

Source

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

Which should you choose?

Choose Blue Reacher if you need threaded replies, read receipts, rich link previews and RCS fallback.

Choose Project Blue if you need sender name and photo, shared numbers, WhatsApp and Slack.

Frequently asked questions