Boundry Email
LiveTransactional email with delivery events, signed webhooks, and regional message records.
Explore EmailAutomate your product inside one regional boundary.
Zapier-style workflow automation and transactional email, built around one fixed region per project. Sydney, Australia is live today.
npm i boundry-sdk
Integrate regional email and automations today
Use your framework, language, or existing service. The regional boundary stays consistent underneath.
Boundry Email
Send regional email from your app
Transactional email through an API you already know, with the delivery record kept next to the message.
- A message record for every send
- Delivery events and signed webhooks
- Sending domain verification
- Processed in the Sydney region
- Idempotent sends
N
Northbank Billingbilling@northbank.com.au
Your September invoice is ready. Payment of $240.00 was received and applied to your account.
M
Maya Chenmaya@northbank.com.au
Thanks, received. Can you confirm the receipt went to accounts as well?
Delivered from Sydney at 9:42:18. The message record, delivery event and webhook receipt are attached to msg_01.
NorthbankAn illustrative Australian fintech sending receipts and statements.
Every receipt leaves through one Sydney project, so support can open the exact message when a customer asks.
Choose your setup. Fix your boundary.
Pick the region, choose how you want to connect, then bring the exact install code into your application.
1. Choose your setup
Select the region your project lives in and the language your app uses.
2. Connect your app
Copy the prompt or run the install command to connect your app.
Generated for Sydney and Node.js.
Integrate Boundry into this Node.js project in the Sydney region using the instructions at https://boundry.dev/llms.txtOne boundary. Two workloads.
Boundry Automations
PreviewMulti-step workflows with triggers, filters, delays, Slack, HTTP, and inspectable run history.
Explore AutomationsRegional lifecycleProject-scoped flow
invoice.paidReceived just nowProjectNorthbank
RegionSydney
WorkloadYour application
StageNorthbank subscription
Native inbound is deployment-gated.
The regional automation infrastructure.
Connect product activity, preserve the run context, require approval where it matters, and inspect every outcome in one place.
Connected across every framework and channel
Trigger workflows from the frameworks and channels your product already uses. Email events, webhooks and Slack all arrive inside one fixed regional project, with the delivery record kept beside every run.
Full context, every run
Every run carries the trigger payload, project settings and encrypted credentials, so the next step never rebuilds state or guesses what happened before.
Slack in the loop
When a workflow refunds, notifies a customer or calls an external API, it can post the outcome and its evidence to Slack in the same run.
Ready in one command
Install the SDK, create a Sydney project and connect your first trigger from the terminal. Everything the workflow does stays inspectable inside that region.
Verify a domain today. Send with evidence tomorrow.
Regional transactional email through an API you already know, with the delivery record kept next to the message.
Send from the stack you already run
One call sends the message from Sydney. The message record, delivery events and signed webhooks land in the same project, so evidence never has to be reconstructed.
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);Regional email streamAU · Sydney
TimeRecipientSubjectState
maya@northbank.com.auVerification receivedDelivered
ops@acme.com.auWorkflow completedOpened
security@harbour.ioEvidence readyDelivered
team@flindev.com.auRegional eventRetrying
legal@northbank.com.auRecord createdDelivered
Messagemsg_03 · Evidence ready
Recipientsecurity@harbour.io
Regionap-southeast-2 · Sydney
Webhookemail.delivered · signature verified
Verified sending domains
Connect the domain to the project that will send from it, then watch each DNS record verify inside the same regional workspace.
Signed delivery webhooks
Every delivery event is signed with the endpoint's secret and sent to the systems that need it, with the message record one click away.
Retention controls
Configure evidence windows per project when automated retention controls are available. Message records stay in the region either way.
Automated retention controls are planned.
Built for regulated environments.
Read the evidence before you commit. The boundary is documented, and so is where it ends. Sydney is live today; more locations will follow.
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. Boundry's regional plane writes configured application objects to storage selected for that deployment.
- 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.
Frequently asked questions.
What is Boundry?
Workflow automation and transactional email for developers. Each project is fixed to one region at creation. Sydney (AWS ap-southeast-2) is the only live region today.
Where is my data processed?
Boundry runs project message operations and configured application storage in the selected regional plane. Public requests transit Cloudflare, Clerk handles account identity centrally, and recipient mailbox providers are outside Boundry's boundary after delivery.
Can I move a project to another region later?
No. The region is part of the project's identity. A new region is a new project.
Is inbound email available?
Native inbound is implemented but deployment-gated and not generally available.
Is Automations generally available?
Automations is a product preview. You can build, test and run workflows today in the Sydney region.
Which SDKs are there?
JavaScript/TypeScript (`boundry-sdk` on npm), Python (`boundry-sdk` on PyPI), Go (`github.com/flindev/boundry-go`) and PHP/Laravel (`boundry/sdk`). Ruby uses the REST API directly.
How does billing work?
A free sandbox, then monthly plans priced in USD. Paid checkout is not yet self-serve.
Can an AI agent integrate Boundry for me?
Yes. Point it at https://boundry.dev/llms.txt. The API is described at /openapi.json and an agent skill lives at /skills/boundry/SKILL.md.
One boundary underneath.
Whether you are sending transactional email or running a workflow, Boundry is the regional layer that keeps the work where you chose to run it.
npm i boundry-sdk