Regional architecture
Boundry separates global account access from regional communication data. The Boundry app on Cloudflare is the control plane; every project operation runs directly in its selected Laravel region.
What stays central
The control plane inside boundry.dev handles dashboard sessions, organisations, project names, regions, roles and the project directory. It has no email content, recipients, message subjects, raw inbound MIME, attachments, webhook payloads or raw API keys.
What stays regional
Regional Laravel API A project request goes directly to its region, such as api.au.boundry.dev.
Regional data and work Domains, key hashes, messages, inbound content, event logs, queues and workers remain with the project.
Regional AWS services SES, inbound storage and encryption resources are configured for that same region.
How the dashboard reaches a project
When you open a project, the Cloudflare control plane checks your membership and issues a short-lived, project-scoped token. Your browser holds it in memory and calls the selected regional API directly. Laravel verifies the token’s signature, audience, project, region, scope and expiry locally—without a control-plane lookup.
Creating a project
Project setup is client-led. The control plane creates the directory record and returns a one-time admission token. The dashboard sends that token directly to the selected regional API, which creates the project namespace. This avoids giving the Boundry app privileged access to any regional environment.
Direct means direct. Customer applications and the dashboard never post a message to a global Boundry endpoint for forwarding. Use the API hostname for the project’s selected region.