Projects

Projects group API keys, rule sets, usage data, accounts, wallets, voucher grants, subject routes, and operational views.

Create a project

Use the project selector in the Portal header.

1. Open the selector.
2. Select Create project.
3. Enter a project name.
4. Optionally enter a description.
5. Save.

Projects have an environment that is checked against the tenant’s current Billing Grant:

• development is the default environment and uses the shared usage storage.
• release is the production environment. Starter has a release limit of 0; Launch and above may create release projects subject to the Grant snapshot. A numeric limit of -1 means unlimited.

When the active Grant sets requires_release_project_usage_storage to true, Portal provisions a project-specific Doris usage table while creating the release project and stores that table binding on the project. Payment itself does not provision tenant-level storage. Project creation is rejected if the Billing entitlement cannot be resolved or the required storage provision fails.

Common project names are environment names such as Production, Staging, or customer gateway names when each customer has an isolated workspace.

Project-scoped URLs

After a project exists, Portal pages are project-scoped:

/projects/:projectId

Project switching updates the route. Refreshing the browser reopens the same workspace instead of falling back to an in-memory selection.

Accounts, wallets, wallet ledgers, voucher grants, and usage control routes are loaded from the current project. Creating or switching projects changes the account and wallet namespace.

Where project settings live

Open Settings from the project sidebar to rename a project, inspect stable IDs, invite members, or delete a project.

Use the project ID when configuring backend integrations, support workflows, and logs.