Australia / Healthcare / Boundry vs Resend
Resend is an excellent general-purpose email product. Its own documentation also makes the regional trade-off unusually clear: sending region and data residency are different things.
TL;DR
Choose Resend when polished global email tooling and its available sending regions matter more than Australian residency. Evaluate Boundry when the workload needs a Sydney regional communication plane and a defensible answer for message data. Boundry is earlier and still completing retention enforcement and its customer-facing Region Manifest; this page states that limitation rather than hiding it.
Comparison checked 16 August 2026 against the linked official documentation. Provider products and policies can change.
Evidence matrix
| Dimension | Boundry | Resend | Why it matters |
|---|---|---|---|
| Product centre of gravity | Regional transactional email. The project is permanently attached to its selected region. | General transactional and marketing email with selectable sending regions. | One product begins with the jurisdiction boundary; the other begins with global email delivery. |
| Australian sending region | Sydney (ap-southeast-2) is the live Boundry region. | Resend currently lists North Virginia, Ireland, São Paulo, and Tokyo. It does not list Sydney. | The network and provider path cannot be called Australian when the provider offers no Australian sending region. |
| Message-plane data | Customer API requests and dashboard message reads go directly to the Sydney regional API; messages, recipients, events, queues, and provider state are owned by the regional plane. | Resend states that all account data, including email metadata, logs, and API records, is stored in the United States regardless of sending region. | Recipient context and operational records can remain relevant even when the clinical content stays behind a secure link. |
| Primary processing location | Sydney for the regional communication plane. Global account identity and control-plane metadata remain separately disclosed boundaries. | Resend's DPA says its primary processing operations take place in the United States and US transfer is necessary to provide the service. | A review needs the complete architecture and contractual scope, not only the domain's delivery setting. |
| Message-content storage | Per-data-class automated pruning is not yet implemented, so Boundry does not currently promise configurable deletion periods. | Resend documents a US$50/month add-on to disable message-content storage for qualifying Pro or Scale teams. Its region documentation still places account metadata, logs, and API records in the US. | Content minimisation and operational-metadata residency are separate controls and should be assessed separately. |
| Subprocessor surface | Boundry's target Region Manifest will enumerate communication data, infrastructure, support access, subprocessors, retention, and exceptions. The production evidence pack is still being completed. | Resend publishes a current subprocessor list spanning hosting, monitoring, data, support, analytics, webhooks, and internal tools, predominantly in the United States. | Healthcare security reviews assess every system that can process the workload, not only the email delivery vendor's headquarters. |
| Healthcare compliance claim | Boundry provides regional architecture, not automatic legal compliance. Customers must assess their workload and obligations. | Resend provides security and contractual material, but a sending-region selector is not an Australian healthcare compliance guarantee. | Neither product replaces legal analysis. The useful difference is the data path each can evidence. |
| Best fit | Australian healthcare, legal, identity, finance, and government-supplier workloads where the regional data path affects procurement or architecture. | Teams prioritising mature general-purpose email tooling, global reach, and the Resend ecosystem without an Australian-residency requirement. | The right choice depends on the workload and buying constraint—not a universal feature winner. |
Who each product fits
Migration path
List every template, recipient field, secure link, attachment, event, webhook, suppression, log, and retention dependency before changing providers.
Bind the Boundry project to the Australian region, verify the sending domain, and create a scoped API key.
Start with a low-risk transactional stream, map delivery events and suppressions, then verify headers, links, retries, and operational support.
Record the final architecture, contract, data classes, subprocessors, exceptions, and deletion behavior for the security reviewer.
FAQ
Not in its current public region list. Resend lists North Virginia, Ireland, São Paulo, and Tokyo. The official page should be rechecked before a procurement decision.
Resend says no. Its region documentation states that the selection controls routing and sending, while email metadata, logs, and API records remain stored in the United States.
No. Boundry is building an evidence-backed regional email boundary. Automated retention enforcement and the production Region Manifest are still being completed, and legal applicability remains the customer's responsibility.
Primary sources
Boundry is not affiliated with Resend. Product names and trademarks belong to their respective owners. This comparison is informational and does not constitute legal advice.
Sydney · Region 01
Start with one healthcare notification stream and test the migration before standardising the rest of the product.