Australia / Healthcare / Boundry vs Mailgun
Mailgun has one of the clearer regional models in email: message data can be provisioned in the US or EU and is documented as staying in that region. For an Australian healthcare workload, the remaining gap is geographic rather than semantic—Mailgun does not offer a Sydney message region.
TL;DR
Stay with Mailgun when its mature API, US or EU regional message boundary, and current retention controls satisfy the workload. Evaluate Boundry when the same architectural question must be answered with Sydney. Mailgun is a strong comparison precisely because it demonstrates that a real message-data boundary is possible, just not currently in Australia.
Comparison checked 16 August 2026 against the linked official documentation. Provider products and policies can change.
Evidence matrix
| Dimension | Boundry | Mailgun | Why it matters |
|---|---|---|---|
| Product centre of gravity | Regional transactional email with Sydney as region 01 and the project permanently bound to that choice. | A mature programmable email platform with sending, receiving, tracking, validation, and deliverability products. | Mailgun offers broader established email infrastructure; Boundry focuses on the Australian regional constraint. |
| Message-data regions | Sydney (ap-southeast-2) is the live Boundry region. | Mailgun lets customers provision message processing in North America or Europe. Its public region list does not include Australia. | A well-defined EU boundary cannot satisfy an architecture requirement that specifically calls for Australia. |
| Regional scope | The Sydney message plane owns messages, recipients, events, queues, and provider state, with control-plane exceptions documented separately. | Mailgun says messages, event logs, suppressions, lists, statistics, routes, and IP addresses are region-bound; account information, users, billing, API keys, and domain names are replicated globally. | Mailgun distinguishes message data from global account data, giving reviewers a useful but non-uniform boundary to assess. |
| Message-content retention | Per-data-class automated pruning is not yet implemented, so Boundry does not currently promise configurable deletion periods. | Mailgun documents zero days on Free, one day on Foundation, and up to seven days on Scale and Enterprise, with three days as the default for newly created eligible domains. | Mailgun currently provides clearer, enforceable content-retention settings than Boundry. |
| Events and suppressions | Boundry's lifecycle retention enforcement remains unfinished and is disclosed as such. | Mailgun retains event data for 30 days and separately documents permanent records for hard bounces, unsubscribes, and spam complaints. | Deleting message bodies does not remove the recipient-linked operational record. |
| Subprocessor and contract surface | Boundry is building a region-specific manifest and evidence pack around a deliberately narrow communication path. | Mailgun is a Sinch service governed by Sinch's DPA and subprocessor list, which documents US and EU hosting plus support and billing providers across multiple locations. | The legal entity and shared group services belong in the vendor review, not only the Mailgun API endpoint. |
| Best fit | Australian healthcare and adjacent regulated workloads where Sydney processing is the deciding criterion. | Teams wanting a mature email API with a documented US or EU message-data region and short content retention. | Mailgun may be the better product unless the required region is Australia. |
Who each product fits
Migration path
Separate region-bound messages, events, suppressions, routes, and statistics from globally replicated account, key, billing, and domain data.
Verify the sending domain, create a scoped Boundry key, and document which Mailgun regional endpoint the service currently calls.
Move a single notification class and validate sending, webhooks, suppressions, retries, and the operational dashboard before broader cutover.
Record the old Mailgun content and event settings, Boundry's current retention limitation, and the controls still required before production approval.
FAQ
Mailgun's current public documentation lists North American and European regions. It does not list an Australian message-processing region.
Mailgun says message data does not leave its selected US or EU region. It also identifies account information, users, billing, API keys, and domain names as globally replicated data.
Mailgun documents plan-dependent message-content retention from zero to seven days. Event data is retained for 30 days, while certain suppression records can be stored permanently.
No. Mailgun is a much broader and more mature email platform. Boundry's proposition is a Sydney-first transactional path and evidence model; matching Mailgun's feature depth is not the current claim.
Primary sources
Boundry is not affiliated with Mailgun. Product names and trademarks belong to their respective owners. This comparison is informational and does not constitute legal advice.
Other providers
Sydney · Region 01
Start with one healthcare notification stream and test the migration before standardising the rest of the product.