Pricing @ Arpia Platform
Arpia Credits
At ARPIA, we believe in adding measurable value to your organization. To achieve this, we have designed a credit consumption system that is transparent and focused on pricing based on value generation.
Credits are consumed based on items and value units. The following sections explain these items and their credit costs.
Credit Groups
| Group | Description |
|---|---|
| Value Units (VUs) | Arpia Platform Value Units based on features used in your workarea(s). |
| Credit Usage | Credit value for VUs, Hours, or Units of Measure for resources used. |
| Core LLMs | Arpia LLM Core Models available for users to integrate into projects. |
| Storage | Storage capacity assigned per workarea. |
👍 Credit Hard Limit
Hard limits are available per workarea. You can set a VUs hard limit, and the platform will prevent the creation of additional VU-generating items once the limit is reached.
Arpia Value Units (VUs)
If your account is billed using Value Units (VUs), this section applies.
Value Units are the default billing method. They ensure you are charged only when measurable value is generated by the platform.
You can analyze usage details in the Workarea Usage Page, including where value is generated and its associated costs.
VUs are calculated based on the resources and features used in workareas.
Workshop & Platform VUs
| Item | Description | VUs |
|---|---|---|
| Work Area Users | Average count of users belonging to the workarea. Users billed in other workareas are not double charged. | 20.00 |
| AI Worker / AI Operator | Average count of active workshop projects using AI Workers or AI Operators. Multiple objects in one project count as one. | 200.00 |
| Workshop Projects | Average count of active workshop projects. | 50.00 |
DataApps VUs
| Item | Description | VUs |
|---|---|---|
| AI Assistant | Average count of AI Assistant agents used. Workflow steps do not affect cost. | 50.00 |
| Dashboards | Average count of dashboard screens. Dashlets, charts, pivots do not add extra VUs. | 15.00 |
| Page Layout | Average count of page layout screens. Sub-items do not affect cost. | 10.00 |
| Custom Code | Average count of custom code screens. | 15.00 |
| Calendar Screen | Average count of calendar screens. | 10.00 |
| Map Screen | Average count of map screens. | 100.00 |
| Data Edit | Average count of data edit tables. | 5.00 |
| Profile Security | Average count of this feature used. | 50.00 |
| Public App | Average count of this feature used. | 100.00 |
If a feature is not listed above, its cost is 0 VUs.
👍 VUs Billing Process & Hard Limits
- The platform calculates daily usage per feature.
- VUs are averaged monthly.
- Credits are applied based on the monthly average.
- Increases or decreases in usage are reflected immediately in billing.
VUs Credit Price
| Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
|---|---|---|---|---|
| Value Units (VUs) | Monthly | 1 | VU | 1 |
Hard limits can be configured to control fixed billing exposure.
Computing Hours @ Arpia Cloud
If your plan is billed using Usage Computing Credits, the following applies:
| Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
|---|---|---|---|---|
| Computing Hours (Only when not using VUs) | Monthly | 1 | Hour | 0.90 |
Computing hours do not apply if your account is billed by Value Units.
GPU, Storage, AI LLM & Other Components
GPU Droplets
| Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
|---|---|---|---|---|
| AI Dedicated GPU Hours | Usage | 1 | Hour | GPU Type Based |
LLMs Core Models @ Arpia Cloud
Arpia provides core LLM models from major providers.
- If customers configure their own models (BYM), no token charges apply.
- If no token is provided, Arpia uses shared tokens billed per usage.
📊 Model Classification for Enterprise
Enterprise models are divided into:
- 🟢 Base Models (Included)
- 🔴 Frontier Models (Pay-Per-Use)
🟢 ARPIA Base LLM Models (Included)
Included within Enterprise contracted tokens.
| Model | Tokens | Cost (Credits/1M) |
|---|---|---|
| openai/gpt-4o-mini | 1M | 0.75 |
| openai/o1-mini | 1M | 5 |
| openai/o3-mini | 1M | 5 |
| openai/gpt-4o | 1M | 5 |
| openai/gpt-5-nano | 1M | 5 |
| anthropic/claude-haiku-4-5 | 1M | 5 |
| cerebras/gpt-oss-120b | 1M | 1 |
| cerebras/llama3.1-8b | 1M | 1 |
| cerebras/llama-3.3-70b | 1M | 1 |
| groq/llama-3.3-70b-versatile | 1M | 1 |
| groq/llama-3.1-8b-instant | 1M | 0.75 |
| groq/gpt-oss-120b | 1M | 1 |
| google/gemini-2.0-flash-001 | 1M | 0.75 |
| google/gemini-2.5-flash-preview-05-20 | 1M | 0.75 |
| mistralai/codestral-2501 | 1M | 0.75 |
| mistralai/mistral-nemo | 1M | 0.75 |
| mistralai/pixtral-large-2411 | 1M | 4 |
| grok/grok-4-1-fast-reasoning | 1M | 0.75 |
| grok/grok-4-1-fast-non-reasoning | 1M | 0.75 |
🔴 ARPIA Frontier LLM Models (Pay-Per-Use)
Not included in any plan. Always billed separately.
| Model | Tokens | Cost (Credits/1M) | Billing |
|---|---|---|---|
| openai/gpt-5-mini | 1M | 10 | Per Consumption |
| openai/gpt-5 | 1M | 25 | Per Consumption |
| openai/gpt-5.2 | 1M | 25 | Per Consumption |
| openai/o1 | 1M | 37.5 | Per Consumption |
| anthropic/claude-sonnet-4.6 | 1M | 17.5 | Per Consumption |
| anthropic/claude-sonnet-4.5 | 1M | 17.5 | Per Consumption |
| anthropic/claude-opus-4.6 | 1M | 25 | Per Consumption |
| anthropic/claude-opus-4.5 | 1M | 25 | Per Consumption |
| google/gemini-2.5-pro-preview | 1M | 10 | Per Consumption |
| google/gemini-3-pro-preview | 1M | 12 | Per Consumption |
Version Clarification
- Claude Opus 4.6 supersedes Opus 4.5 at the same pricing tier.
- Claude Sonnet 4.6 supersedes Sonnet 4.5 at the same pricing tier.
- Legacy versions may remain available temporarily for compatibility.
🎯 Usage Recommendations
- Use Base Models for 80–90% of operations.
- Reserve Frontier Models for advanced reasoning.
- Monitor usage in the dashboard.
- Configure alerts for Frontier consumption.
📘 BYM (Bring Your Model)
When users configure their own LLM models:
- No token charge applies.
- Only Computing Hours or VUs are billed.
Storage @ Arpia Cloud
Shared Storage
| Resource Type | Billing | Quantity | UoM | Cost |
|---|---|---|---|---|
| SingleStore | Monthly Daily Avg | 10 | GB | 5 |
| MySQL/MariaDB | Monthly Daily Avg | 10 | GB | 2.5 |
| Object Storage | Monthly Daily Avg | 10 | GB | 1 |
Dedicated Storage
| Resource Type | Billing | UoM | Cost |
|---|---|---|---|
| SingleStore Node (32GB 8vCPU) | Monthly | Node | 750 |
| MySQL/MariaDB Node (32GB 8vCPU) | Monthly | Node | 250 |
| Object Storage Node (8GB 4vCPU) | Monthly | Node | 150 |
For HA setups, add +1 node per existing node.
Credit Billing Policy & Terms
- Credit Rollover: Annual plans only.
- No Refunds: Except in case of system error.
- Invoices are generated on the 5th of each month based on previous month's usage.
- Payment via Stripe.
- 2+ overdue invoices may cause service interruption.
- Prepaid balances are automatically deducted from recurring usage.
Account Billing & Usage Support
For assistance, contact billing support via the Support Chat on the ARPIA Web Platform.
Updated 2 days ago
