Australia / Healthcare / Boundry vs Postmark
Postmark is a focused transactional email service with unusually plain retention documentation. For an Australian healthcare review, the decisive issue is equally plain: Postmark documents its primary data and servers outside Chicago and on AWS, not an Australian processing region.
TL;DR
Stay with Postmark when proven transactional-email operations, its established product, and adjustable 7-to-365-day activity retention are more important than Australian residency. Evaluate Boundry when the workload needs a Sydney regional message plane and procurement needs an Australian data-path answer. Boundry is earlier and does not yet offer Postmark's configurable retention controls.
Comparison checked 16 August 2026 against the linked official documentation. Provider products and policies can change.
Evidence matrix
| Dimension | Boundry | Postmark | Why it matters |
|---|---|---|---|
| Product centre of gravity | Regional transactional email with a project permanently attached to its selected region. | A mature, specialised transactional email platform organised around message streams, delivery, and support tooling. | Postmark is the stronger established email operator; Boundry is designed around a jurisdiction boundary that Postmark does not offer in Australia. |
| Australian processing region | Sydney (ap-southeast-2) is the live Boundry region. | Postmark documents primary data and servers at Deft outside Chicago and on AWS. Its public documentation does not offer an Australian processing region. | An Australian customer must assess overseas processing rather than treating provider quality as a location guarantee. |
| Message retention | Per-data-class automated pruning is not yet implemented, so Boundry does not currently promise configurable deletion periods. | Postmark stores message content, events, and metadata for 45 days by default. Its paid Retention Add-on supports 7 to 365 days; aggregated statistics are stored indefinitely. | Postmark currently offers the more mature retention control, but even its minimum setting still stores message activity outside Australia for seven days. |
| Operational access | Boundry's target Region Manifest will disclose support access and every known exception; production evidence is still being completed. | Postmark says selected staff can access servers and may view messages with account-owner permission or during a terms-of-use compliance review. | Healthcare reviewers need to include authorised human access, not only database geography, in the processing map. |
| Subprocessor surface | Boundry publishes its regional architecture and is building a customer-readable Region Manifest for infrastructure, support, retention, and exceptions. | Postmark lists Deft and AWS for infrastructure and Zendesk for support communications that may contain customer personal data. | The support path can matter even when it is not part of routine email delivery. |
| Contractual position | Boundry offers regional architecture, not automatic healthcare compliance; customers must assess their workload and applicable obligations. | Postmark publishes a DPA and cross-border safeguards, but that contract does not turn its US-centred infrastructure into Australian residency. | A DPA governs processing; it does not change where the documented processing occurs. |
| Best fit | Australian workloads where the location of message content, recipients, events, and operational evidence affects procurement. | Teams that value a mature transactional-only product and can accept the documented US data path. | The decision is primarily jurisdiction versus product maturity, not a generic feature score. |
Who each product fits
Migration path
Inventory servers, message streams, templates, inbound routes, suppressions, webhooks, metadata, and the current retention setting.
Create a Boundry project, verify the sending domain, issue a scoped API key, and record the regional endpoint in the architecture review.
Move a low-risk healthcare notification, then compare delivery events, bounce handling, retries, and support workflows before expanding.
Update the DPA, data-flow diagram, subprocessor record, retention statement, and incident-support runbook to match the new path.
FAQ
Postmark's public security documentation describes primary data and servers at a data centre outside Chicago and on AWS. It does not document an Australian processing region. Recheck its official documentation before procurement.
Postmark documents 45 days by default. Its paid Retention Add-on can set activity retention from 7 to 365 days, while aggregated statistics are kept indefinitely.
Not inherently. It can be a strong transactional-email product when its location, retention, access, and contractual terms are acceptable for the workload. The issue is whether those facts satisfy the specific Australian healthcare requirement.
No. Postmark is the more established email product and currently has configurable retention controls that Boundry has not finished. Boundry's relevant distinction is its Sydney regional architecture.
Primary sources
Boundry is not affiliated with Postmark. 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.