Regional projects
An organisation is central. Each project is a separate regional delivery workspace—its messages, domains, inbound content, logs and webhook deliveries stay together.
What is central and what is regional?
Your organisation, members, and project directory live in Boundry’s Cloudflare control plane. The moment an operation belongs to a project—sending a message, receiving mail, generating DNS records, making an API key, or delivering a webhook—it belongs to that regional Laravel data plane.
Choose the boundary first
Choose a project region during project creation. Treat that choice as permanent: it is the boundary used for sends, receiving, storage and observability. A separate region should be a separate project, even when both projects use the same application.
Use project-scoped keys
Every API key belongs to one project. A Sydney project key can only access its Sydney project, even when the same organisation owns other projects. This means your service should select a key and endpoint per workload, environment, or jurisdiction.
# Sydney production
BOUNDARY_API_URL=https://api.au.boundry.dev
# Local development
# BOUNDARY_API_URL=https://api.au.boundry.dev
Authorization: Bearer $BOUNDRY_API_KEYWhen to create another project
- You need an isolated production, staging, or customer environment.
- Your workload must store content in a different jurisdiction.
- You want independent domains, retention, webhook endpoints, or access keys.