Regional email should mean the email is regional.

Putting a database in Sydney is not enough. Boundry gives every project one permanent region for its message processing, then tells you exactly what sits outside it.

npm i boundry-sdk

Create a Sydney project

Email · Live
Sydney · ap-southeast-2
Region permanent · not a routing preference

Regional email streamAU · SydneyIllustrative data

TimeRecipientSubjectState

09:42:18maya@northbank.com.auPassword resetDelivered

09:41:07ops@acme.com.auReceipt 8ZPOpened

09:39:52security@harbour.ioEvidence readyDelivered

09:37:21team@flindev.com.auStatement attachedRetrying

09:34:11legal@northbank.com.auRecord createdDelivered

Message: msg_03 · Evidence ready
Recipient: security@harbour.io
Region: ap-southeast-2 · Sydney
Webhook: email.delivered · signature verified

The region belongs to the project.

Most regional products start with a global system and bolt a location onto it later. Boundry starts with the boundary. Choose Sydney once, then send through the regional API without teaching your team a new email workflow.

Cloudflare handles public request transit. Clerk handles account identity centrally. Recipient mailbox providers sit outside Boundry after delivery. We put those facts on the page because regional should not rely on fine print.

Choose Sydney once.

The region is part of the project’s identity. It cannot quietly drift because somebody changed a routing preference. A project stays in its selected jurisdiction; if you need another one, create another project.

Send the email.

Use the API or SMTP for password resets, receipts, and product notifications. The regional project is the constraint under the send, not extra ceremony for the engineering team.

Read the quickstart

Show your work.

When a reviewer asks where the email carrying a passport scan went, “hosted in Australia” is not enough. The Sydney Region Manifest puts the product scope, subprocessors, and known exceptions in one place.

Open the Sydney Region Manifest

The same send from the language you already use.

One call sends the message from Sydney. The message record, delivery events and signed webhooks land in the same project, in TypeScript, Python, Go, Ruby, PHP, or cURL.

import Boundry from 'boundry-sdk';

const client = new Boundry({
  apiKey: process.env['BOUNDRY_API_KEY'],
});

const email = await client.emails.send({
  from: 'Acme <hello@acme.com>',
  to: 'ava@northwind.com.au',
  subject: 'Welcome to Acme',
  html: '<p>It works.</p>',
});

console.log(email.id);

From project to sent, in three calls.

The shortest path from a new Boundry project to a real transactional email request.

01
Create a project in your target region.
A project is the data boundary for its domains, API keys, messages and event history.
Terminal
```
export BOUNDRY_API_KEY="<your API key>"
```
02
Verify a sending domain.
Your From address must belong to a verified domain in this exact project.
Create a sending domain
```
{
  "name": "mail.acme.com",
  "capabilities": { "sending": true, "receiving": false }
}
```

Create an API key and send.

Keep the secret server-side; the first request returns an email ID you can inspect in the dashboard.

Node.js

import { Boundry } from "boundry-sdk";

const boundry = new Boundry({ apiKey: process.env.BOUNDRY_API_KEY });

await boundry.emails.send({
  from: "receipts@mail.acme.com",
  to: "customer@example.com",
  subject: "Receipt",
});

Questions before you send from Sydney.

Can a project’s region change later?

No. The region is part of the project’s identity and cannot change once set. If you need a different jurisdiction, create another project rather than reconfiguring this one.

What sits outside the Sydney boundary?

Cloudflare handles public request transit. Clerk handles account identity centrally. Recipient mailbox providers sit outside Boundry after delivery. Those exceptions are documented, not hidden in fine print.

How much can I send before I need a paid plan?

Sandbox includes 3,000 emails a month and 1 sending domain per project, enough to trace a real password reset or receipt end to end.

Is data retention configurable yet?

Not yet. The regional API currently stores the records a message, event, webhook and inbound implementation requires until an operator or future retention job removes them; per-project retention windows are planned, not enforced today.

Built for regulated environments.

Read the evidence before you commit. The boundary is documented, and so is where it ends. Sydney is the only live region today.

Read the Sydney manifest

Sydney · ap-southeast-2
Region fixed at creation
Subprocessors documented
Security evidence published

Region manifest: Ingress, storage, processing, delivery events, webhooks and deletion, mapped end to end for the Sydney region.
Subprocessors: Every third party in the path, and what each one sees.
Security: What is verified in code, what is observed in operation, and what is still unproven.

Put one real workflow through Sydney.

Sandbox includes 3,000 emails a month and 1 sending domain per project. Start with a password reset or receipt you can trace from your application to the regional plane.