Project Blue vs Zernio

Compare Project Blue and Zernio 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

Zernio

One API for iMessage, SMS, WhatsApp, social DMs and calls
Starting price
$200/month per iMessage sender
Free plan
First 2 connected accounts free; free iMessage sandbox on a shared line

Project Blue supports 42 of the 77 features compared here, and Zernio supports 57.

Feature comparison

FeatureProject BlueZernio
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.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
PartialGroups are created by sending to a set of numbers. No add or remove member endpoints documented.
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
PartialgroupName can be set when a group is created. No group photo documented.
SupportedRename a group or change its photo, one change per call.
Mentions
Not listed
Not listed
Tapbacks
PartialSend or remove the six classic tapbacks on inbound iMessages. Receiving reactions is not documented.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
Not listed
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
PartialSend only, iMessage only, into an existing conversation. Inbound typing events not documented.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
Not listed
PartialMark a chat read inside an active two-way chat. Webhook docs list message.read for other platforms only.
Edit and unsend
Not listed
SupportedEdit text within 15 minutes; unsend within 2 minutes removes the bubble for the recipient.
Message effects
Supported4 bubble and 9 screen effects through the effect field. iMessage only.
Supported13 screen and bubble effects, such as slam, invisibleInk, confetti and fireworks.
Animated text effects
Not listed
Not listed
Stickers
Not listed
PartialInbound stickers are typed as sticker. Sending stickers is not documented.
Formatted text
Not listed
SupportedInline *bold*, _italic_, __underline__ and ~strikethrough~ markup renders as rich text.
Attachments
SupportedImages, videos and vCards by URL.
SupportedUp to 10 per message, each a public https URL of at most 256 characters.
Live Photos
Not listed
Not listed
Rich link previews
Not listed
SupportedOn by default; linkPreview: false sends links as plain text.
Voice messages
SupportedAudio files sent as voice memos, plus AI text-to-speech voice memos.
SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards
SupportedVCF files through mediaAttachmentUrl.
PartialcontactCard shares the sender's own card only.
Polls
Not listed
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
Not listed
PartialStatic location pins only. Inbound shared locations arrive without coordinates.
iMessage apps
Not listed
Not listed
Live app cards
Not listed
Not listed
Sender name and photo
SupportedSet, read and share a line's Share Name and Photo card by API.
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
PartialFaceTime Audio only, outbound and inbound, on FaceTime-enabled accounts. Not on trials.
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
PartialMessages carry a status field such as delivered. Webhooks cover only inbound and outbound messages.
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
Supported
Not listed
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.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
SupportedA dedicated line per rep, never shared. New lines are requested by API and provisioned by the team.
SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers
PartialTrial accounts only: a shared line that can reach verified numbers.
SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number
SupportedExisting numbers can be ported to Project Blue's carrier partner.
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
SupportedSends without lineId are load balanced across your lines.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
SupportedFalls back to SMS from the same line when iMessage is unavailable.
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
Not listedHomepage describes fallback from iMessage to WhatsApp to SMS. RCS fallback is not described.
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedLines are sold as outbound-ready. Guidelines rule out mass outbound iMessage.
SupportedOne new chat per 15 minutes per sender, warm-up from 2 to 50 a day, no links in openers.
Calls on the iMessage number
SupportedDialer and FaceTime Audio calls from the same number as the messaging line.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
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.
Supported
Telegram
Not supportedNot offered
Supported
Slack
PartialSlack notifications for inbound replies. Not a messaging channel.
Supported
Email
Not supportedDeveloper page says it is not a general email API.
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
SupportedCloud dialer with inbound, outbound, routing, recording and voicemail, plus a browser calling SDK.
SupportedInbound and outbound PSTN calls, SIP trunks, browser softphone, recording and transcription.
Apple Messages for Business
Not supportedNot offered
Not supportedNot offered
Unified channel API
PartialOne send endpoint covers iMessage and SMS. Calls and FaceTime use separate endpoints.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
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@zernio/node
Python SDK
Not listed
Supportedzernio-sdk
Other SDKs
Not listed
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
Not listed
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
SupportedInbound and outbound message events and inbound FaceTime call events.
Supported
Signed webhooks
Not listedWebhook docs do not mention signatures.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
SupportedRemote MCP server with OAuth 2.1, plus an optional Claude Code plugin.
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
PartialThe dialer SDK is MIT licensed on npm. The platform is closed.
PartialSDKs, CLI, n8n node and Chat SDK adapter are MIT or Apache-2.0. The platform is closed.
Self-hosting
Not listedHosted service on Project Blue lines. Self-hosting is not mentioned.
Not supportedHosted cloud service only
Local testing
Not listedTrial accounts send real messages to verified numbers; docs say they are not a simulator.
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
Not listed
Not listed
Event replay
Not supportedDocs say webhooks have no retries and failed deliveries are not replayed.
Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedGoHighLevel conversation provider with workflow actions and triggers. llms.txt also lists Zapier.
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
SupportedHubSpot and Close CRM. Salesforce is not listed.
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
Not listed
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
Not listed
PartialVercel Chat SDK adapter (iMessage not listed) and an OpenClaw skill.
Streaming replies
Not listed
PartialChat SDK adapter streams by editing on Telegram only.
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.
PartialDashboard inbox and workflow handoff nodes; no iMessage-specific handoff documented.
Audit logs
Not listed
SupportedAppend-only log of team-management actions; Enterprise adds broader audit logs.
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.
SupportedFirst 2 connected accounts free; free iMessage sandbox (5 contacts, 50 messages a day).
Public pricing
Supported$166/month per line billed annually, or $199/month per line on a 12-month plan.
Supported$200 per iMessage sender per month, plus the connected-account fee.
No per-message fees
SupportedFlat per-line pricing with unlimited texting under fair use.
PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA
Not listedSite cites a 99.9% uptime record and a public status page. No contractual SLA found.
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
PartialEach rep gets a dedicated line that is never shared. Other infrastructure is not described.
Not listed
SOC 2 Type II
Not listed
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
PartialPrivacy policy lists GDPR and UK GDPR rights. No DPA found.
SupportedGDPR documentation in the trust portal; public DPA.

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

Zernio

An iMessage sender costs $200 a month plus Zernio's per-account fee, with a free sandbox; SMS, calls and outbound messages past 10,000 a month are metered.

Pricing model: flat per sender, plus per connected account and usage meters

Source

Which should you choose?

Choose Project Blue if you need FaceTime calls, iMessage availability check, line pooling and isolated infrastructure.

Choose Zernio if you need threaded replies, read receipts, edit and unsend and stickers.

Frequently asked questions