Every few months someone works out that a Mac mini in a closet can send iMessages for free, and writes it up as though the hosted providers are selling water by the river. The maths is real. The conclusion usually is not — because the thing you are comparing is not send cost, it is total risk.
What the bridge actually costs
- A Mac that stays powered, awake, unlocked, and online — permanently.
- An Apple Account signed into it. Automating a consumer account conflicts with Apple's terms, and enforcement means losing that account, not a warning email.
- Your personal or shop number as the sender, with no separation between business and personal threads.
- Maintenance every time macOS updates and the automation permissions reset.
- No SMS fallback, so every Android customer is unreachable through that path.
Price the outage, not the message
The right question is not 'what does a message cost'. It is 'what happens to my business on the Tuesday this stops working and I am with a customer'. If that answer is bad, the free option is not free.
When self-hosting is genuinely the right call
- You are messaging yourself or your own team, not customers.
- You are prototyping to find out whether the channel works at all.
- You have a hard requirement that no third party ever holds message content, and you have the ops maturity to back that up.
When to pay for hosted
- The messages go to customers.
- Someone other than you needs to be able to fix it.
- You need SMS fallback to reach a mixed list — see blue vs green.
- You need delivery status you can trust for support and reconciliation.
- You want a business number that is separate from your personal one.
For nearly every small business sending customer messages, that second list decides it. Prototype on BlueBubbles or the AppleScript route if you like the learning. Ship on a hosted API.
Next step
Generate a tagged link for whatever you send next with the UTM builder, see what this looks like in your industry, or compare the services that can send it on the providers page.