Track production unit consumption

A production unit (PU) is the accounting unit Maleus uses to measure agent activity. Anything that runs the agent on your behalf consumes PUs: a guided version going through Design, Specifications and Development, a workshop session, a cloud agent run.

PUs are billed against a workspace allocation. Each project either draws from the shared pool or has its own dedicated cap.

Where to look

There are two pages.

The usage card

The project page header is the Project usage breakdown card. Two sections:

• PU consumption, with rows for Versions, Workshops, and Others (residual activity that doesn't fit the first two).
• Time spent, the same rows expressed in active agent time.

The same times, version by version, sit on each card in Versions. Create a new version explains how to read them.

The right column of the page splits the same data by Versions, Workshops, and Agents (cloud agent runs). Each row expands to a per-user contribution breakdown, so you can see who consumed what.

The platform overview

The workspace-level page adds:

• A Projects tab listing every project with a status badge, a progress bar against its limit, and a View usage shortcut.
• A Monthly tab with a 12-month consumption chart.
• A Recent Activity column on the left.
• An Export button in the top right.

Set a PU limit per project

Admins can cap how much a single project can consume.

1. On the project page, find the Project PU limit card.
2. Click Change. The Set PU Limit dialog opens.
3. Pick a strategy.
   • Use Shared Pool: no dedicated limit, draws from the workspace allocation.
   • Set Custom Limit: assign a dedicated PU budget for this project.
4. If you picked Custom Limit, enter a value in the Limit (PUs) field.
5. Click Save Changes.

Why monitor PUs

Consumption helps you spot patterns: a workshop that ran longer than expected, a cloud agent run that looped, a version where the spec step dragged on. Watch the per-user breakdown when you need to triage a spike.