Skip to content
imessageapi

Review / Self-hosted bridge

AirMessage review

The other open-source Mac bridge — Android and web clients, Apache-2.0.

AirMessage is the main alternative to BlueBubbles and works on the same principle: a server process on a Mac signed into your Apple Account relays messages to Android and web clients. It is Apache-2.0 licensed and actively developed. What it is not is an automation platform — it was built so a person could read and answer their own iMessages from an Android phone, and it exposes no webhook API for a program to build against.

What it is good at

  • Apache-2.0 licensed and openly developed — you can read exactly what it does.
  • No cost beyond hardware you may already own.
  • Clients for Android and the web, so the relay is usable from anything.
  • Full message fidelity, because the sending path is the real Messages app.

Where it will bite you

  • **No webhook or automation API.** It is a personal relay, not infrastructure — if you want a program to react to inbound messages, BlueBubbles is the better-shaped project.
  • Requires an always-on Mac and a personal Apple Account, which is your single point of failure and your terms-of-service exposure.
  • Sends from your personal number, with no business-line separation.
  • **The project's own site was serving an expired TLS certificate when checked in August 2026** — a small thing, but not a reassuring one for software that holds your Apple Account.
  • A smaller community and thinner ecosystem than BlueBubbles.
  • macOS updates break bridges routinely. Budget for maintenance.

Tracking links with AirMessage

UTM note

As with any self-hosted bridge there is no vendor-side delivery data, so tagged links plus your own analytics are the only attribution you will get.

Whatever you send with, build the URL from one helper so tagging is consistent across every job and campaign. Open the UTM builder to generate one now.

Still weighing options?

The comparison table puts all five side by side.