WorkArea Usage & Billing Dashboard
WorkArea Usage
The WorkArea Usage page gives you a real-time view of your credit consumption across all billable resources in your WorkArea — datastores, AI tokens, and Value Units (VUs). It is the operational complement to the Pricing @ Arpia Platform reference, translating the billing model into your actual usage data.
Credit usages are calculated through the end of the previous day. The current day's consumption is not yet reflected in any figure on this page.
Accessing the Page
- Log in to your Arpia AI Platform account.
- Navigate to WorkArea Usage in the main menu.
The WorkArea Usage dashboard is then displayed:
Selecting a Billing Period
Use the month selector at the top of the page to change the period displayed. You can view the current month plus the previous three months.
Understanding the Dashboard
Credit Usage by Arpia Platform Products
The top table itemizes every billable resource consumed in the selected period. Each row maps to a billing category defined in the Pricing @ Arpia Platform page.
| Column | Description |
|---|---|
| Item | The platform product identifier (e.g., SS-DATASTORES, MYSQL-DATASTORES, AI-LLM-TOKENS, ARPIA-VALUE-UNITS) |
| Description | Plain-language description of what is being measured and the calculation period |
| Shift | The billing shift or tier applicable to the item |
| Usage | Actual consumption in the item's native unit (GB, tokens, VUs, etc.) |
| Credits | Credits charged for that item during the period |
The table footer shows two summary rows:
- Work Area Total Credits — total credits consumed across all items for the period.
- Credits / Day — the daily average burn rate, useful for projecting end-of-month spend.
1 Credit = 1 USD. See Pricing @ Arpia Platform for the full rate schedule.
Storage items (SS-DATASTORES, MYSQL-DATASTORES)
SS-DATASTORES, MYSQL-DATASTORES)These reflect daily average storage consumption billed monthly. Rates are:
- SingleStore: 5 credits per 10 GB/month
- MySQL/MariaDB: 2.5 credits per 10 GB/month
AI token item (AI-LLM-TOKENS)
AI-LLM-TOKENS)This line covers LLM token consumption against Arpia-provided shared models. Token costs vary by model and whether it is a Base (included) or Frontier (pay-per-use) model. If you use BYM (Bring Your Model), no token charges appear here — only VUs or computing hours apply.
See the Arpia Provided AI Models Usage sub-table below for a per-model breakdown.
Value Units item (ARPIA-VALUE-UNITS)
ARPIA-VALUE-UNITS)This line covers all VU-generating platform features. VUs are calculated as a daily average, billed monthly. The VU sub-tables below break this down by source.
Value Units [VUs] Usage Charts
Two charts visualize VU consumption in detail.
Value Units [VUs] Usage (bar chart) — Daily stacked bars for the selected period, broken down by VU source type:
| Category | What it represents |
|---|---|
addon | Add-on features enabled in the WorkArea |
user | WorkArea Users (35 VUs/user/month average) |
workshop | Active Workshop Projects (25 VUs/project/month average) |
app | DataApp features such as AI Assistants (50 VUs each) and Map Screens (50 VUs each) |
Actual [VUs] Count Usage (donut chart) — Proportional breakdown of total VUs for the period across the same four categories. Use this to identify which category is driving the bulk of your VU cost.
VU Sub-Tables
Four sub-tables provide granular breakdowns of VU consumption by source. All sub-tables show VUs consumed and credits charged for the selected period.
App [VUs] Usage
Lists VU consumption and credits per app session or AI App instance.
Workshop [VUs] Usage
Lists VU consumption and credits per active Workshop Project. Note that multiple AI objects within one project count as a single VU-generating unit.
Users [VUs] Usage
Lists VU consumption and credits per WorkArea user. Users already billed in another WorkArea are not double-charged.
Arpia Provided AI Models Usage
Lists token consumption and credits charged per AI model used through Arpia's shared LLM gateway. Columns shown are Model, Tokens, and Credits.
This table is particularly important for cost governance. Frontier models (e.g., anthropic/claude-opus-4-6, anthropic/claude-sonnet-4-6) are always billed separately at pay-per-use rates and are not included in any plan. Base models are included within contracted token allocations.
Recommendation: Reserve Frontier models for tasks that genuinely require advanced reasoning. Route 80–90% of operations through Base models to control token costs. Configure alerts when Frontier consumption approaches budget thresholds (alerts feature coming soon).
Editing Your WorkArea Name
You can rename your WorkArea directly from this page.
- Click Edit WorkArea Name in the top-right corner.
- In the modal, update the name in the Change WorkArea Name field.
- Click Save to apply, or Close to cancel.
Managing Alerts
Coming soon. Usage alerts and notification configuration will be available in a future release. Once available, you will be able to define credit spending thresholds and receive notifications via email or SMS when those thresholds are approached. This is particularly recommended for WorkAreas using Frontier LLM models.
In the meantime, use the Credits / Day footer metric and the monthly selector to manually monitor burn rate trends across periods.
Related Pages
- Pricing @ Arpia Platform — Full rate schedule for VUs, storage, LLM tokens, and GPU.
- Arpia AI Platform — Monthly Billing & Invoicing Process — How invoices are generated and payment is processed.