Chert vs Zernio

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

Chert

iMessage and FaceTime numbers for AI agents
Starting price
$25/month (Shared)
Free plan
24-hour trial: 10 messages and 10 FaceTime minutes on a shared line

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

Chert supports 47 of the 77 features compared here, and Zernio supports 57.

Feature comparison

FeatureChertZernio
iMessage messaging
iMessage
Supported
Supported
Group chats
Supported2 to 31 recipients; first group message must be text only.
SupportedGroups on ordered senders: reply, create, rename, photo, members. Not on the sandbox line.
Group management
SupportedCreate, add or remove participants, and leave a group.
SupportedStart a group from a sender and add or remove participants; applied asynchronously.
Group name and photo
SupportedSet a group's display name and icon.
SupportedRename a group or change its photo, one change per call.
Mentions
Not listed
Not listed
Tapbacks
SupportedSix standard tapbacks; inbound tapbacks show in message history.
SupportedSix Apple tapbacks plus custom emoji (iOS 18+). Inbound reactions arrive by webhook.
Threaded replies
Not listedHomepage mentions reply context; no reply-to field in the API docs.
SupportedreplyTo on sends; inbound messages carry the reply thread id.
Typing indicators
SupportedBest effort; group typing is not supported on every line.
PartialSend only, 1:1 chats, about 15 seconds, after a recent two-way exchange.
Read receipts
SupportedMark chats read; messages carry read_at when known.
PartialMark a chat read inside an active two-way chat. Webhook docs list message.read for other platforms only.
Edit and unsend
PartialEdit within 15 minutes; no unsend endpoint documented.
SupportedEdit text within 15 minutes; unsend within 2 minutes removes the bubble for the recipient.
Message effects
SupportedApple send effects, validated against an allowed list.
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
SupportedUpload then send; several images can go out as one grouped message.
SupportedUp to 10 per message, each a public https URL of at most 256 characters.
Live Photos
Supportedlive_photo pairs an uploaded HEIC with its MOV.
Not listed
Rich link previews
Supportedrich_link parts render as preview bubbles; falls back to a plain URL.
SupportedOn by default; linkPreview: false sends links as plain text.
Voice messages
SupportedNative voice notes on enabled lines; inbound memos arrive as attachments, no transcript.
SupportedvoiceNote: true on an audio file. Inbound voice messages come with a transcript.
Contact cards
SupportedBuilds a vCard bubble in DMs and groups.
PartialcontactCard shares the sender's own card only.
Polls
SupportedEnabled lines only; read votes by polling, no vote webhooks yet.
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
PartialOne-time location pin on enabled lines; not Live Location or Find My.
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
SupportedNative name-and-photo sharing on enabled lines (share_native).
PartialSets the name and photo on the sender's contact card, which recipients see when they save it.
FaceTime calls
SupportedInbound audio and video, outbound audio only, bridged to your LiveKit agent.
Not listedInbound FaceTime attempts show in the thread as call-typed messages. No calling documented.
Delivery status
SupportedPer-message status with delivered_at, and the channel used (iMessage or SMS).
Supportedmessage.delivered and message.failed webhooks; sends deferred for pacing show as queued.
iMessage availability check
Not listed
Not listed
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedChert-managed sender lines assigned to your tenant.
SupportedZernio orders numbers on its delivery provider's Apple-registered infrastructure.
Dedicated numbers
Supported$250/mo per line, arranged on a call; no self-serve checkout yet.
SupportedUS or UK numbers, some active instantly; email-handle senders through the API.
Shared numbers
SupportedFree 24-hour trial and $25/mo Shared plan on a shared line.
SupportedFree shared sandbox line for testing: contact writes first, 5 contacts, 50 messages a day.
Bring your own number
Not listed
PartialiMessage cannot run on a number you own. A sender held with the provider can be registered.
Line pooling
SupportedPicks and pins a sender line per recipient from your assigned lines.
Not listedOne sender per profile; docs suggest spreading contacts across senders by hand.
SMS fallback
PartialLines enabled for SMS retry only; plain-text 1:1 messages, not groups or media.
SupportedSMS or RCS from the same number when the contact is not on iMessage.
RCS fallback
Not listedHomepage says SMS or RCS fallback; API docs only describe SMS retry.
SupportedSMS or RCS from the same number; the provider picks per contact.
Outbound-first messaging
SupportedFirst send to a new recipient creates a lead and pins a line.
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
PartialHomepage offers one number for iMessage and FaceTime; docs say identities are not unified yet.
PartialOrdered numbers include call forwarding. Placing calls from the iMessage number is not documented.
Other channels
SMS
PartialOnly as an automatic retry after a failed iMessage, on enabled lines.
Supported
RCS
Not listedMentioned only as a fallback on the homepage.
Supported
WhatsApp
Not supportedNot offered
Supported
Telegram
Not supported
Supported
Slack
Not listed
Supported
Email
Not supportedNot offered
Not supportedNot offered as a channel. iMessage senders can use an email handle.
Phone calls
Not supportedNot offered; calls are FaceTime only.
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
PartialiMessage and SMS retry share one API; FaceTime uses a separate API.
SupportedSame inbox send call and webhooks for iMessage, SMS, WhatsApp, Telegram, Slack and social DMs.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Beta@trychert/sdk 0.2.0 on npm (MIT); the homepage still says SDK packages are not published.
Supported@zernio/node
Python SDK
BetaSource preview on GitHub; not released on PyPI.
Supportedzernio-sdk
Other SDKs
BetaRust, C#/.NET, C++ and Go clients are source previews on GitHub.
SupportedGo, Ruby, Java, PHP, .NET and Rust.
CLI
BetaFaceTime CLI on npm's beta tag; the SDK adds a chert-sdk CLI for sends.
SupportedZernio CLI, including iMessage inbox sends and reactions.
Webhooks
SupportedMultiple subscriptions with event filters; message.received for inbound.
Supported
Signed webhooks
SupportedHMAC-SHA256 per-subscription secret over timestamp and raw body.
SupportedHMAC-SHA256 of the raw body in X-Zernio-Signature, keyed by your secret.
MCP server
Not listed
SupportedHosted at mcp.zernio.com/mcp, with OAuth sign-in or an API key.
Open source
PartialSDKs are MIT and a FaceTime link connector is Apache-2.0; the service is closed.
PartialSDKs, CLI, n8n node and Chat SDK adapter are MIT or Apache-2.0. The platform is closed.
Self-hosting
Not listedOnly the open-source FaceTime link connector runs on your own machine.
Not supportedHosted cloud service only
Local testing
Not listedSSE stream and dev inbox avoid a public webhook, but a real phone is still needed.
Not listedThe free sandbox still needs your own phone or Apple ID.
Custom channel providers
Not listed
Not listed
Event replay
SupportedDurable event log with replay by event ID, polling and SSE.
Supported7 attempts over about 51 hours, then dead-letter; any past event can be redelivered.
OpenTelemetry
Not listed
Not listed
No-code integrations
Not listed
Partialn8n, Make and Zapier guides cover posting; Make's API call module reaches any endpoint.
CRM integrations
SupportedSalesforce managed package and HubSpot app.
SupportedHubSpot: inbox contacts and messages sync to HubSpot timelines.
Built for AI agents
Agent framework
PartialChert-managed FaceTime assistants and a LiveKit voice-agent starter; messaging is send and receive.
PartialWorkflow engine with AI and handoff nodes; the workflow docs do not list iMessage.
Agent framework integrations
PartialFaceTime calls connect to LiveKit agents; no messaging framework integrations.
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
SupportedSlack reply triage with approve-to-send drafts, plus a console reply pane.
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
PartialLast 200 messages per chat; no pagination yet.
Supported
Plans and compliance
Free plan
Partial24-hour trial with 10 messages and 10 FaceTime minutes on a shared line.
SupportedFirst 2 connected accounts free; free iMessage sandbox (5 contacts, 50 messages a day).
Public pricing
Supported
Supported$200 per iMessage sender per month, plus the connected-account fee.
No per-message fees
SupportedFlat monthly prices; paid plans have usage limits that are not spelled out.
PartialiMessage pages say no per-message fee; an outbound meter of $1 per 10,000 after 10,000 starts Oct 2026.
Uptime SLA
Not listed
Not listedSite states 99.97% uptime; no contractual SLA found.
Isolated infrastructure
SupportedDedicated $250/mo line for your project; lower plans use shared lines
Not listed
SOC 2 Type II
Not listed
SupportedSOC 2 Type II report in the trust portal, by access request.
GDPR
SupportedPrivacy policy sets out GDPR legal bases and rights.
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

Chert

A free 24-hour trial includes 10 messages and 10 FaceTime minutes on a shared line; Shared is $25 a month and a dedicated line is $250 a month, but paid checkout is paused.

Pricing model: flat monthly per line, with usage limits

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 Chert if you need Live Photos, polls, FaceTime calls and line pooling.

Choose Zernio if you need threaded replies, stickers, formatted text and bring your own number.

Frequently asked questions