Photon (photon.codes) approaches iMessage from a different direction to most of the category. The pitch is not "send more messages to your list" — it is "put your agent where people already are", with iMessage as one channel alongside WhatsApp, Telegram, Slack and Discord behind a single SDK.
How to read this page
Photon is not in our provider comparison — we have not run a production line with them. What follows is from their public pages, checked August 2026.
The pricing, which they publish
| Tier | Price | The essential detail |
|---|---|---|
| Free | $0 | Runs on your own Mac using your own iCloud account as the agent's number. Up to 10 users. |
| Pro | $25/month | Same model, up to 100 users, faster support. |
| Business | $250/line/month | Dedicated iMessage lines, group messaging, cold outreach capped around 50 new contacts a day. |
| Enterprise | Custom | You own the numbers, lowest throttling. |
The jump from $25 to $250 is the important line on that table, and it is the same line every provider has — it is the point where you stop using your own Apple identity and start renting managed infrastructure. Below it you are the phone farm. Above it, somebody else is.
Read the free tier carefully
Free and Pro run through your Mac and your iCloud account. That is genuinely free and genuinely useful for prototyping — and it means the account carrying your business messages is a personal Apple ID, with all the exposure that implies if it gets restricted. Fine for a prototype. Think hard before a customer-facing product depends on it.
What is distinctive
- An open-source, TypeScript-first SDK. One codebase deploying to iMessage, WhatsApp, Telegram, Slack and Discord. If you are building an agent that should not be locked to one channel, that is a real architectural argument.
- iMessage mini apps. They claim the first API for delivering interactive UI inside an iMessage thread rather than a link out to a web page. Genuinely novel if it holds up in practice.
- Newer iOS message features — polls and background customisation among them — exposed through the API rather than left to the Messages app.
- A published cold-outreach cap on the Business tier, around 50 new contacts a day. Stating a limit rather than implying unlimited sending is a good sign, and it lines up with what a safe warm-up actually looks like.
Who it fits
| Situation | Verdict |
|---|---|
| Building an AI agent that lives in a chat thread | Strong fit — the agent playbook is here |
| Multi-channel from day one | Strong fit — the SDK is the reason to choose it |
| Prototyping, and $0 matters | Strong fit, with the personal-Apple-ID caveat above |
| A small business wanting an inbox and reminders | Wrong shape — look at Miss Blue |
| Enterprise procurement demanding a SOC 2 report | Ask. Linq leads on that |
What to verify
Before building on it
- Sign up for the free tier and send a real message today — the barrier is deliberately low.
- Read the SDK's repository: last commit, open issues, release cadence.
- Confirm what "unlimited daily messages" means alongside the throttling language on the same page.
- Ask whether Business-tier numbers are portable if you leave.
- Ask directly about the compliance posture if you will need one.
- Compare the real monthly cost against the rest of the market at your volume.
The category's default is to hide pricing behind a form. Photon does not, and that alone makes it a useful benchmark when you are trying to work out whether a quote you have been given is reasonable.