OpalSpan

See where your team's capacity actually went.

By Ready IT ApS

Choosing a plan answers one question: how much capacity is available? Running a support team creates another: what did we actually use, and over which period?

OpalSpan's Usage & Analytics gives you a selected-interval view of AI credits and resources, with per-unit AI credit breakdowns. Recorded device and active Automation capacity history adds another perspective—but only for the time it was actually recorded.

Scripted shared Design System illustration, not customer usage or a bill. Seven fictional days total 252 AI credits: Alex 126, Sam 84, Jordan 42. The native table and capacity coverage are shown. The illustrative recording boundary is 8 October at 09:00; actual production recording began 12 October at 17:43:56 Copenhagen. No backfill or spending change.

Choose a period that answers a real question

Use the calendar range picker or its 7-day, 30-day and This month presets. Interactive charts group the selected interval, and per-unit AI credit tables help you look beyond one headline total. Original result links preserve the interval they refer to. Future dates cannot be selected.

For a team lead, a practical question might be: which recorded units contributed to this week's AI usage? The view helps you inspect that question without treating every conversation, reconnection or task as another work session. AI usage and the work-session rule remain distinct.

A chart describes recorded use. It is not a new tariff, a purchase approval or a recommendation to increase the budget.

Keep the capacity timeline honest

Device and active Automation capacity recording began on 12 October 2026 at 17:43:56 Europe/Copenhagen. It was not backfilled. Earlier September or October capacity peaks cannot be reconstructed from this feature, and the first recording day is partial.

The capacity history reports simultaneous daily peaks and weekly or monthly maxima with recording coverage. Coverage matters as much as the number: a partially recorded interval is not evidence that no devices or Automations were present during its missing hours.

Do not add separate device or Automation peaks and call the result a simultaneous peak. Read the metric and its interval as presented, then check the coverage before drawing a staffing or capacity conclusion.

Review use before changing the allowance

Imagine a fictional support team reviewing a week before deciding whether its current plan still fits. The lead selects the interval, inspects AI credit breakdowns and checks the capacity recording coverage. Missing history remains missing; a graph does not turn it into a full month's evidence.

That review can inform a decision. It does not prove return on investment, change an accepted order or authorize additional spending. The applicable plan, explicit budgets and purchases still determine those boundaries.

Start with Mech in the browser; your own external assistant can use OpalSpan Agent CLI with the same user permissions. Windows and Linux are supported; macOS is a technical preview, in active development.

Compare the allowances for your team.