Regional projects

An organisation is central. Each project is a separate regional API workspace for its project data and operations.

What is central and what is regional?

Clerk handles identity and organisation membership. The Boundry control plane stores the project directory and issues short-lived access tokens. Message operations, domains, project keys, logs and webhooks belong to the selected regional Laravel data plane.

Choose the boundary first

Choose a project region during project creation and treat it as permanent. The browser calls that regional API directly for project work. Cloudflare still handles public HTTP transit.

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. Select a key and endpoint per workload or environment.

# Sydney production
BOUNDARY_API_URL=https://api.au.boundry.dev

# Local development
# BOUNDARY_API_URL=https://api.au.boundry.dev

Authorization: Bearer $BOUNDRY_API_KEY

When to create another project

• You need an isolated production, staging, or customer environment.
• You need independent domains, webhook endpoints, or access keys.
• A future live region meets a different jurisdiction requirement.