What is the difference between LoopMessage and rustpush?

LoopMessage supports 53 of the 77 features compared here, and rustpush supports 39. LoopMessage adds contact cards, managed lines, dedicated numbers, shared numbers and line pooling. rustpush adds mentions, Live Photos, chat backgrounds, iMessage apps and live app cards.

How much do LoopMessage and rustpush cost?

LoopMessage: A free sandbox covers 5 contacts; dedicated senders start at $59.99 a month, with add-ons for a phone number, SMS/RCS fallback, WhatsApp and outbound-first. rustpush: rustpush is free source under SSPL v1; you supply Apple hardware identifiers or an always-on iPhone relay, and anyone offering it as a service must publish their service's source.

Does rustpush support contact cards?

rustpush does not list contact cards on its site or in its docs.

Does rustpush support managed lines?

rustpush does not support managed lines.

Does rustpush support dedicated numbers?

rustpush does not support dedicated numbers.

LoopMessage vs rustpush

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

LoopMessage

iMessage, SMS, RCS and WhatsApp on one number

Starting price: $59.99/month per sender (Light)
Free plan: Sandbox: $0, 5 contacts, testing only; free shared plan for schools and non-profits

Visit LoopMessage Read more

rustpush

Rust library for the iMessage, FaceTime and APNs protocols

Starting price: Free
Free plan: Free source (SSPL v1)

Visit rustpush Read more

LoopMessage supports 53 of the 77 features compared here, and rustpush supports 39.

Where LoopMessage is ahead

and 15 more in the table below.

Where rustpush is ahead

and 1 more in the table below.

Feature comparison

Feature	LoopMessage	rustpush
iMessage messaging
iMessage	Supported	SupportedRegisters as an Apple device and talks to Apple's servers directly; read from source, no docs
Group chats	SupportedSend and receive in iMessage groups; not available in the sandbox.	SupportedConversations carry a participant list and optional group name
Group management	SupportedCreate groups (needs the Init conversations add-on) and add or remove members.	SupportedChangeParticipants messages add or remove members
Group name and photo	SupportedSet group name (32 characters max) and photo with PATCH.	SupportedRename and IconChange messages set a group's name and photo
Mentions	Not listed	SupportedMention message parts
Tapbacks	SupportedSix tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.	SupportedSix classic tapbacks plus emoji; sticker tapbacks are receive only
Threaded replies	Supportedreply_to_id on send; inbound webhooks carry a thread object.	Supportedreply_guid and reply_part on messages
Typing indicators	SupportedUp to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.	SupportedTyping message type
Read receipts	PartialYou can mark chats read; no read event is documented for your outbound messages.	SupportedRead and Delivered message types
Edit and unsend	SupportedEdit within 15 minutes, unsend within 2 minutes of sending.	SupportedEdit and Unsend message types
Message effects	Supported13 bubble and screen effects via the effect field.	Supportedeffect field on messages
Animated text effects	SupportedMarkup for shake, nod, explode, ripple, bloom and jitter.	SupportedBig, small, shake, nod, explode, ripple, bloom and jitter
Stickers	PartialInbound messages can have type sticker; sending stickers is not documented.	PartialSticker tapbacks are received; the code marks sending them as unsupported
Formatted text	SupportedBold, italic, underline, strikethrough and text sizes in iMessage.	SupportedBold, italic, underline and strikethrough
Attachments	SupportedUp to 10 public HTTPS file URLs per message.	SupportedInline data or MMCS (iCloud) file transfer
Live Photos	Not listed	PartialReceived attachments carry a Live Photo flag; uploads always set it to false
Rich link previews	SupportedLinks get rich previews by default; preview: false sends plain text.	SupportedLinkMeta with LPLinkMetadata rich link data
Voice messages	SupportedSend audio files as voice messages; inbound audio is transcribed.	Supportedvoice flag on messages
Contact cards	Supportedcontact_file adds a vCard to the message.	Not listed
Polls	Not listedA helpdesk article lists polls among features, but no poll API is documented.	Not listed
Chat backgrounds	Not listed	SupportedSetTranscriptBackground sets or removes a chat background
Location sharing	PartialInbound messages can have type location; sending a location is not documented.	PartialFind My clients read friends' and items' locations; OpenBubbles says sharing live location is unsupported
iMessage apps	Not listed	SupportedExtension app balloons with template layouts
Live app cards	Not listed	SupportedUpdateExtension messages update a sent app balloon
Sender name and photo	Not listedDocs suggest sending a vCard so recipients see your name and photo.	SupportedShare Name and Photo, including contact posters
FaceTime calls	Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.	SupportedCreate, ring, join and leave FaceTime sessions
Delivery status	Supportedmessage_delivered and message_failed webhooks, plus a status lookup by ID.	SupportedDelivered and Read receipts plus error messages
iMessage availability check	PartialThrough LoopLookup, a separate LoopMessage service.	SupportedIDS lookups validate targets before sending
Focus and Notify Anyway	Not listed	SupportedNotifyAnyways messages; StatusKit shares and receives Focus status
Numbers and delivery
Managed lines	SupportedDedicated senders run on hardware LoopMessage rents to you.	Not supportedA library; you register your own Apple ID and device identity
Dedicated numbers	SupportedPhone number option is +$15/mo per dedicated sender; email senders also offered.	Not supportedNot offered
Shared numbers	SupportedShared senders for AI assistant use from $20/mo; free sandbox for testing.	Not supported
Bring your own number	PartialYou can port a US number in; your own Apple IDs are not accepted.	SupportedYour own Apple ID; a phone number registers through an iPhone running a relay app
Line pooling	SupportedSender pools balance new contacts across senders and match replies to the right one.	Not listed
SMS fallback	SupportedPaid add-on, +$15/mo per dedicated sender; included on shared plans.	Not listed
RCS fallback	SupportedSame add-on uses RCS instead of SMS when the device supports it.	Not listed
Outbound-first messaging	PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.	SupportedSend to any handle after an IDS key lookup
Calls on the iMessage number	PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.	PartialFaceTime on the same Apple ID; no phone calls
Other channels
SMS	SupportedSet channel to sms; needs the SMS/RCS add-on.	PartialSMS message type, sent through text forwarding from a registered iPhone
RCS	SupportedSet channel to rcs; needs the SMS/RCS add-on.	Not listed
WhatsApp	SupportedAdd-on, +$10/mo, on the same phone number and API.	Not supportedNot offered
Telegram	Not supportedPlanned on the roadmap, not available yet.	Not supported
Slack	Not listed	Not supported
Email	Not listed	Not supported
Phone calls	PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.	Not supportedNot offered; FaceTime only
Apple Messages for Business	Not supportedNot offered; the helpdesk contrasts LoopMessage with it.	Not supportedNot offered
Unified channel API	SupportediMessage, SMS, RCS and WhatsApp on one number and one API.	PartialiMessage and forwarded SMS share one message type; no other channels
Developer tools
REST API	Supported	Not supportedRust library only; no HTTP API
TypeScript SDK	PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.	Not listedRust crate only
Python SDK	PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.	Not listed
Other SDKs	PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.	PartialThe library itself is a Rust crate; no other language bindings found
CLI	Not listed	Not listed
Webhooks	SupportedRetried up to 30 times over several hours.	Not supportedLibrary only; your code receives messages directly, no webhooks
Signed webhooks	PartialYou set an authorization header and verify it; no HMAC signature.	Not supportedNo webhooks
MCP server	PartialDocumentation-only MCP server; no access to your account or messages.	Not listed
Open source	PartialOnly the n8n node is MIT on GitHub; the platform is closed.	PartialSource under SSPL v1; the Mac validation-data module is a closed-source stub
Self-hosting	Not listed	SupportedRuns inside your own application
Local testing	Not listedThe sandbox needs a real iPhone or Mac to message it.	Not listed
Custom channel providers	Not listed	Not listed
Event replay	PartialWebhook history API to fetch past events; no replay call.	Not listed
OpenTelemetry	Not listed	Not listed
No-code integrations	Supportedn8n, Zapier, Pipedream, HighLevel and LeadConnector.	Not listed
CRM integrations	SupportedHighLevel CRM and LeadConnector; no HubSpot or Salesforce found.	Not listed
Built for AI agents
Agent framework	Not listed	Not listed
Agent framework integrations	Not listed	Not listed
Streaming replies	Not listed	Not listed
Agent group chats	Not listed	Not listed
Human handoff	PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.	Not listed
Audit logs	PartialMessage, webhook and API request history kept; no account audit log found.	Not listed
Message history API	SupportedPaginated history per contact, filterable by date, direction and type.	SupportedMessages in iCloud sync for chats, messages and attachments
Plans and compliance
Free plan	SupportedSandbox with 5 contacts; free shared plan for schools and non-profits.	SupportedFree source under SSPL v1
Public pricing	Supported	Not listedNo prices or commercial license terms published
No per-message fees	SupportedUnlimited messages; plans cap unique active contacts per day.	SupportedNo fees; free source
Uptime SLA	Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.	Not supportedSSPL disclaims all warranty
Isolated infrastructure	SupportedA dedicated sender's number and server are allocated to you alone.	SupportedRuns in your own process and infrastructure
SOC 2 Type II	Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.	Not listedSelf-hosted; compliance is up to the operator
GDPR	SupportedHelpdesk says data is stored following GDPR.	Not listed

Feature

LoopMessage

rustpush

iMessage messaging

iMessage

Registers as an Apple device and talks to Apple's servers directly; read from source, no docs

Group chats

Send and receive in iMessage groups; not available in the sandbox.

Conversations carry a participant list and optional group name

Group management

Create groups (needs the Init conversations add-on) and add or remove members.

ChangeParticipants messages add or remove members

Group name and photo

Set group name (32 characters max) and photo with PATCH.

Rename and IconChange messages set a group's name and photo

Mentions

Not listed

Mention message parts

Tapbacks

Six tapbacks or any emoji; inbound reactions arrive as message_reaction webhooks.

Six classic tapbacks plus emoji; sticker tapbacks are receive only

Threaded replies

reply_to_id on send; inbound webhooks carry a thread object.

reply_guid and reply_part on messages

Typing indicators

Up to 60 seconds; fails if the chat had no two-way activity in the last 5 minutes.

Typing message type

Read receipts

PartialYou can mark chats read; no read event is documented for your outbound messages.

Read and Delivered message types

Edit and unsend

Edit within 15 minutes, unsend within 2 minutes of sending.

Edit and Unsend message types

Message effects

13 bubble and screen effects via the effect field.

effect field on messages

Animated text effects

Markup for shake, nod, explode, ripple, bloom and jitter.

Big, small, shake, nod, explode, ripple, bloom and jitter

Stickers

PartialInbound messages can have type sticker; sending stickers is not documented.

PartialSticker tapbacks are received; the code marks sending them as unsupported

Formatted text

Bold, italic, underline, strikethrough and text sizes in iMessage.

Bold, italic, underline and strikethrough

Attachments

Up to 10 public HTTPS file URLs per message.

Inline data or MMCS (iCloud) file transfer

Live Photos

Not listed

PartialReceived attachments carry a Live Photo flag; uploads always set it to false

Rich link previews

Links get rich previews by default; preview: false sends plain text.

LinkMeta with LPLinkMetadata rich link data

Voice messages

Send audio files as voice messages; inbound audio is transcribed.

voice flag on messages

Contact cards

contact_file adds a vCard to the message.

Not listed

Polls

Not listedA helpdesk article lists polls among features, but no poll API is documented.

Not listed

Chat backgrounds

Not listed

SetTranscriptBackground sets or removes a chat background

Location sharing

PartialInbound messages can have type location; sending a location is not documented.

PartialFind My clients read friends' and items' locations; OpenBubbles says sharing live location is unsupported

iMessage apps

Not listed

Extension app balloons with template layouts

Live app cards

Not listed

UpdateExtension messages update a sent app balloon

Sender name and photo

Not listedDocs suggest sending a vCard so recipients see your name and photo.

Share Name and Photo, including contact posters

FaceTime calls

Not supportedFaceTime API is in progress on the roadmap; today only an inbound FaceTime call webhook.

Create, ring, join and leave FaceTime sessions

Delivery status

message_delivered and message_failed webhooks, plus a status lookup by ID.

Delivered and Read receipts plus error messages

iMessage availability check

PartialThrough LoopLookup, a separate LoopMessage service.

IDS lookups validate targets before sending

Focus and Notify Anyway

Not listed

NotifyAnyways messages; StatusKit shares and receives Focus status

Numbers and delivery

Managed lines

Dedicated senders run on hardware LoopMessage rents to you.

Not supportedA library; you register your own Apple ID and device identity

Dedicated numbers

Phone number option is +$15/mo per dedicated sender; email senders also offered.

Not supportedNot offered

Shared numbers

Shared senders for AI assistant use from $20/mo; free sandbox for testing.

Not supported

Bring your own number

PartialYou can port a US number in; your own Apple IDs are not accepted.

Your own Apple ID; a phone number registers through an iPhone running a relay app

Line pooling

Sender pools balance new contacts across senders and match replies to the right one.

Not listed

SMS fallback

Paid add-on, +$15/mo per dedicated sender; included on shared plans.

Not listed

RCS fallback

Same add-on uses RCS instead of SMS when the device supports it.

Not listed

Outbound-first messaging

PartialInit conversations add-on (+$30/mo), warm-up and recent opt-in required; no cold messaging.

Send to any handle after an IDS key lookup

Calls on the iMessage number

PartialInbound cell calls to the sender number are forwarded (add-on); no outbound calls.

PartialFaceTime on the same Apple ID; no phone calls

Other channels

SMS

Set channel to sms; needs the SMS/RCS add-on.

PartialSMS message type, sent through text forwarding from a registered iPhone

RCS

Set channel to rcs; needs the SMS/RCS add-on.

Not listed

Add-on, +$10/mo, on the same phone number and API.

Not supportedNot offered

Not supportedPlanned on the roadmap, not available yet.

Not supported

Slack

Not listed

Not supported

Not listed

Not supported

Phone calls

PartialInbound cell calls are forwarded to a number you choose (add-on); no call API.

Not supportedNot offered; FaceTime only

Apple Messages for Business

Not supportedNot offered; the helpdesk contrasts LoopMessage with it.

Not supportedNot offered

Unified channel API

iMessage, SMS, RCS and WhatsApp on one number and one API.

PartialiMessage and forwarded SMS share one message type; no other channels

Developer tools

REST API

Not supportedRust library only; no HTTP API

TypeScript SDK

PartialNo own SDK; Twilio's SDKs work through the Twilio-compatible API.

Not listedRust crate only

Python SDK

PartialNo own SDK; docs show Twilio's Python SDK pointed at the Twilio-compatible API.

Not listed

Other SDKs

PartialNo own SDKs; Twilio's SDKs work through the Twilio-compatible API.

PartialThe library itself is a Rust crate; no other language bindings found

CLI

Not listed

Webhooks

Retried up to 30 times over several hours.

Not supportedLibrary only; your code receives messages directly, no webhooks

Signed webhooks

PartialYou set an authorization header and verify it; no HMAC signature.

Not supportedNo webhooks

MCP server

PartialDocumentation-only MCP server; no access to your account or messages.

Not listed

Open source

PartialOnly the n8n node is MIT on GitHub; the platform is closed.

PartialSource under SSPL v1; the Mac validation-data module is a closed-source stub

Self-hosting

Not listed

Runs inside your own application

Local testing

Not listedThe sandbox needs a real iPhone or Mac to message it.

Not listed

Custom channel providers

Not listed

Event replay

PartialWebhook history API to fetch past events; no replay call.

Not listed

OpenTelemetry

Not listed

No-code integrations

n8n, Zapier, Pipedream, HighLevel and LeadConnector.

Not listed

CRM integrations

HighLevel CRM and LeadConnector; no HubSpot or Salesforce found.

Not listed

Built for AI agents

Agent framework

Not listed

Agent framework integrations

Not listed

Streaming replies

Not listed

Agent group chats

Not listed

Human handoff

PartialPeople can reply from Slack, email or the embedded inbox; no agent handoff controls.

Not listed

Audit logs

PartialMessage, webhook and API request history kept; no account audit log found.

Not listed

Message history API

Paginated history per contact, filterable by date, direction and type.

Messages in iCloud sync for chats, messages and attachments

Plans and compliance

Free plan

Sandbox with 5 contacts; free shared plan for schools and non-profits.

Free source under SSPL v1

Public pricing

Not listedNo prices or commercial license terms published

No per-message fees

Unlimited messages; plans cap unique active contacts per day.

No fees; free source

Uptime SLA

Not supportedHelpdesk says LoopMessage does not provide SLAs or contracts.

Not supportedSSPL disclaims all warranty

Isolated infrastructure

A dedicated sender's number and server are allocated to you alone.

Runs in your own process and infrastructure

SOC 2 Type II

Not supportedHelpdesk says LoopMessage has not been through a SOC 2 audit.

Not listedSelf-hosted; compliance is up to the operator

GDPR

Helpdesk says data is stored following GDPR.

Not listed

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

Pricing

LoopMessage

A free sandbox covers 5 contacts; dedicated senders start at $59.99 a month, with add-ons for a phone number, SMS/RCS fallback, WhatsApp and outbound-first.

Pricing model: flat per sender with daily contact caps, plus monthly add-ons

Source

rustpush

rustpush is free source under SSPL v1; you supply Apple hardware identifiers or an always-on iPhone relay, and anyone offering it as a service must publish their service's source.

Pricing model: free self-hosted library

Source