Regional architecture
Boundry separates global account access from regional communication data. The Boundry app on Cloudflare is the control plane; project operations go from the browser directly to the selected Laravel region.
What stays central
Clerk processes account identity, sessions and organisations. The control plane stores project names, regions, roles and the project directory. It does not store or proxy email content, recipients, subjects, inbound MIME, attachments, webhook payloads or raw API keys.
What stays regional
Regional Laravel API A project request targets its regional hostname, such as api.au.boundry.dev.
Regional application data The regional API owns project keys, domains, messages, event logs, queues and workers.
Configured regional services Production refuses to boot without an explicit region, matching AWS region, send transport, and storage disks.
How the dashboard reaches a project
The Cloudflare control plane checks membership and issues a five-minute project token. The browser keeps it in memory and calls the regional API directly. Laravel verifies its signature, audience, project, region, scope and expiry without a control-plane database lookup.
Boundary disclosures
- Public HTTP requests pass through Cloudflare before reaching Boundry workloads.
- Clerk processes account identity and organisation membership in the control plane.
- Recipient mailbox providers are outside Boundry’s boundary after delivery.
- Native inbound is deployment-gated; retention enforcement, backup controls, telemetry inventory and support-access procedures are not yet operationally verified.
The control plane does not forward messages. Customer applications and the dashboard use the selected regional API hostname for project operations.