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

---

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.

Every 1 VU = 1 USD (American Dollars).

---

Workshop & Platform VUs

---

DataApps VUs

If a feature is not listed above, its cost is 0 VUs.

---

⚠️ Notice — AI Solutions & Token Consumption

Value Units cover platform orchestration only for AI-driven features (AI Worker / AI Operator, AI Assistant). Token Consumption generated by these solutions when using a Shared LLM Model is billed separately under LLMs Core Models @ Arpia Cloud, at the selected model's published rate per 1 Million Tokens.

• Shared LLM Models (no BYM): billed per the Base / Frontier model rates (Credits per 1 Million Tokens).
• BYM (Bring Your Model): no ARPIA token charge — only VUs (or Computing Hours) apply.

Token Consumption scales with the size and complexity of each interaction and the model selected. Monitor consumption in the usage dashboard and configure alerts for both Base and Frontier models.

🔒 Data retention: Prompts and completions sent to shared LLM providers are handled per our Privacy Policy — LLMs & AI Tools, including provider zero-/short-term retention and BYoM terms.

---

👍 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

Hard limits can be configured to control fixed billing exposure.

---

👍 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.

---

Computing Hours @ Arpia Cloud

If your plan is billed using Usage Computing Credits, the following applies:

❗

Computing hours do not apply if your account is billed by Value Units.

---

GPU, Storage, AI LLM & Other Components

---

GPU Droplets

---

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 model is provided, ARPIA uses Shared LLM Models billed per Token Consumption.

Token Consumption

Each Shared LLM Model is priced per 1 Million Tokens, the platform's standard Billing Unit. Token Consumption reflects the total volume of tokens processed during an interaction with the model. Consumption is accumulated across the billing period and charged according to the selected model's published rate. This applies only to Shared LLM Models; BYM configurations are not subject to token charges.

---

📊 Model Classification for Enterprise

Enterprise models are divided into:

• 🟢 Base Models
• 🔴 Frontier Models

⚠️

Both Base and Frontier models are billed Pay-Per-Use by default. Enterprise customers with a contracted agreement should refer to their signed terms, which may include provisions differing from this document.

---

🟢 ARPIA Base LLM Models (Pay-Per-Use)

Billed per Token Consumption unless otherwise specified in a signed contract.

⚠️

Qwen/Qwen2.5-VL-72B-Instruct: no Input/Output split available in the current pricing source — pending update.

---

🔴 ARPIA Frontier LLM Models (Pay-Per-Use)

Always billed separately, per consumption. Not eligible for inclusion under any plan.

---

🎯 Usage Recommendations

1. Use Base Models for 80–90% of operations.
2. Reserve Frontier Models for advanced reasoning.
3. Monitor usage in the dashboard.
4. Configure alerts for both Base and 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

---

Dedicated Storage

For HA setups, add +1 node per existing node.

---

Credit Billing Policy & Terms

1. Credit Rollover: Annual plans only.
2. No Refunds: Except in case of system error.
3. Invoices are generated on the 5th of each month based on previous month's usage.
4. Payment via Stripe.
5. 2+ overdue invoices may cause service interruption.
6. 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.