Projects

Platform › Customers › Projects lists the projects of one tenant, with each project’s quota totalled across its clusters. A project groups a tenant’s API keys and budgets, and on each cluster it uses it runs in its own namespace with its own quota, carved out of the tenant’s capacity envelope there.

Who can open it

Platform administrators only. Tenant admins see their projects’ keys and budgets on Keys and budgets.

What a project is on a cluster

Setting a project’s quota on a cluster creates the project’s namespace there. Olympusx AI provisions it within about 30 seconds and keeps it as declared:

• the namespace, labelled with its tenant and project;
• a resource quota from the project’s quota, and default limits so pods without requests are admitted;
• network policies that deny all traffic by default, then allow DNS, traffic within the namespace, and traffic to and from the platform’s own namespace. There is no internet egress.
• two roles, edit and view, neither of which can change the quota, the limits, the network policies or the roles. They are bound to people only when your installation names a group template for tenant groups. See Network and hardening.

A project with no quota on a cluster has no namespace there. Its models then run in the platform’s shared serving namespace.

What you see

1. The header, Projects, with “Each project gets a share of its tenant’s capacity on a cluster: CPU, memory, storage and GPUs by type.”
2. The tenant picker. The page shows one tenant’s projects.
3. The Projects table, with Search projects and Create project.

Column	What it shows
Project	The name, linking to the project’s page.
Environment	For example prod or staging.
CPU, Memory, Storage, Pods	The quota, totalled across the project’s clusters. No limit when any one cluster leaves it unlimited, or when the project has no quota anywhere.
GPUs	The sum of GPUs across clusters, or None.
Clusters	How many clusters carry a quota for the project.
Actions	Edit quota, and in the menu Delete project.

A tenant without projects shows No projects yet with Create project.

Create a project

1. Choose the tenant in the picker, then select Create project. The Create a project dialog opens.
2. Name and environment. Enter the Project name and the Environment, for example prod or staging. Both are required. Select Next.
3. Cluster quota (optional). Choose a cluster the tenant holds capacity on and give the project its share: CPU cores, Memory (GiB), Storage (GiB), Pods and GPUs. The step shows the tenant’s envelope on that cluster. Or choose No quota (skip) and set it later. If the tenant holds capacity on no cluster, the step says No cluster access: skip it and grant the tenant capacity on Tenants first. Select Next.
4. Review. Check the details, then select Create project.

Creating a project that already exists in the tenant returns the existing one. If the project was created and its quota was refused, the dialog offers Retry the quota, which sends the quota alone, or Open the project without a quota.

Edit a project’s quota

1. Select Edit quota on the project’s row. Quota for project opens.
2. Choose the cluster. The dialog shows the tenant’s envelope there: “Tenant envelope on this cluster: CPU cores n · memory n · storage n.”
3. Set CPU cores, Memory (GiB), Storage (GiB), Pods, and GPUs by flavor.
4. Select Save.

A quota of 0 sets no quota on that dimension: the project is then limited only by what its tenant can still use on the cluster. The quotas of all the tenant’s projects on a cluster must fit the tenant’s envelope there.

To clear a project’s quota on one cluster, select Clear quota on this cluster in the dialog and confirm Clear quota. The project keeps running, within whatever its tenant can still use there.

Refusal	Why
Exceeds the tenant’s capacity	The projects’ quotas on this cluster would add up to more than the tenant’s envelope. The message names the dimensions.
No cluster access	The tenant holds no capacity on that cluster.
Negative value	Every value must be 0 or more.
Unknown GPU flavor	The flavor is not in the catalog.

Delete a project

1. Open the row’s menu and select Delete project.
2. Type the project’s name to confirm, then select Delete project.

Its API keys stop working at once, its quotas and its project and key budgets and rate limits are removed, and its namespaces are removed from the clusters. Its usage history is kept.

Deletion is refused:

• while models are still deployed in the project. The message names them: undeploy them first;
• for the tenant’s only project. A tenant needs at least one: create another first.

A project’s page

Select a project. The header shows its name, its tenant, Created and Project ID.

Tab	What it shows
Overview	Namespaces and quota: on each cluster, the namespace, the quota and the current use read from the cluster. Then Members of the tenant: everyone listed can reach every project their role allows.
Deployments	Models deployed into this project’s namespaces. A model deployed without a project runs in the shared namespace and is not listed here.
Budgets and spend	Usage this month metered to the project through the gateway, with cost, and the token budgets on the project and its keys. Its keys are listed by name, never with their secret.
Activity	Audit entries about this project, newest first: its creation, keys issued and revoked, budgets set or removed, models undeployed. The tenant’s whole trail is on Audit.

Usage no API key made, such as embedding documents for knowledge, chatting with an assistant in the console and the Playground without a key, is recorded against the tenant’s first project.

Limits

Limit	Value
Projects per tenant	At least 1
Namespaces per project	One per cluster it holds quota on
Namespace provisioning	Reconciled every 30 seconds
Quota values	0 or more; 0 means no limit beyond the tenant’s own

Related

• Tenants for the capacity envelope a project’s quota comes out of
• Keys and budgets
• Tenants, projects and people