SMS should stay inside the same boundary.
Boundry SMS is coming to Sydney. The product is being built around the whole message trail: content, phone numbers, delivery events, queues, logs, and replies.
- Product
- SMS
- Availability
- Coming not generally available
- First region
- Sydney ap-southeast-2
The message is more than the send.
A local carrier route is not a regional product by itself. The API, processing, message history, provider events, consent records, and operational logs all need a clear home.
A familiar message API.
Submit a message, receive a stable Boundry ID, and follow each recipient through queued, sent, delivered, failed, or blocked states without exposing provider identifiers as your contract.
A regional delivery trail.
Keep message content, phone numbers, delivery receipts, suppressions, and retention jobs attached to the project’s selected region instead of a global messaging account.
Conversations when replies arrive.
Dedicated numbers will turn inbound replies into project-local conversations with stable message IDs, consent handling, and a complete chronological record.
Start with the regional product that is live.
Boundry Email is available in Sydney today. SMS will open only after the sending, receiving, registration, and retention paths meet the same standard.