License vs Location
These are two separate concepts that often get conflated. Both matter for understanding how BlueSender deployments work.
| Concept | Purpose | Constraint |
|---|---|---|
| License | Controls how many Macs can run BlueSender | maxSeats devices per license key |
| Location | The CRM tenant a Mac connects to | 1 Mac per locationId |
A user with a 3-seat license can run BlueSender on 3 Macs, but each Mac must connect to a different CRM location. If two Macs connect to the same location, the second one takes over and the first is disconnected.
Implications
- Licensing is independent of CRM tenancy. A license is issued to an end-user (or an upstream tool like Stripe / Zapier on their behalf — see License keys) and tracks how many Macs are activated against it.
- Location is independent of license seats. A
locationIdbinds a single Mac to a single CRM tenant. Multiple Macs running on the same license can serve multiple locations in parallel. - You cannot scale read/write throughput on one location by adding Macs. The "1 Mac per location" rule means a busy CRM tenant is served by exactly one Mac at a time. Mac-side queueing absorbs bursts up to the automation-queue cap (see Mac automation-queue limit).
Related
- License keys — how licenses are issued and managed.
- Device pairing — how a Mac claims a seat on a license.
- Locations — how
locationIdbinds a Mac to a CRM tenant.