Pricing @ Arpia Platform
Arpia Credits
At ARPIA we believe in adding value into your organization, for this we have design a credit consumption system that is clear and focused in a pricing based on value generation.
Credits are consumed based on items and value units. The following page explains this items and their credit costs. The group of items are:
Group | Description |
---|---|
Value Units (VUs) | Arpia Platform Value Units are based in features used in your workarea(s). |
Credit Usage | Credit value for VUs, Hours or Unit Of Measure for resources used in your workarea(s). |
Core LLMs | Arpia LLM Core Models available for users to start using LLM models into their projects. |
Storage | The storage capacity by workarea assign to the customer. |
Credits are the currency used for usage-based billing in ARPIA Data Cloud. The type of credit is managed by
Credit Hard Limit
Hard limits are avialble per workarea so you can set a VUs hardlimit and the platform will limit the creation of more VU items once the hard limit is reached.
Arpia Value Units (VUs)
If your account is set to be billed with VUs (Value Units) then this table applies. Value Units is the default way for billing our platform value into your organization in a transparent and balanced method on charging only if value is delivered by our Platform. You may analize in the workarea usage page information on how Value is been generated where and costs for each area.
Arpia Value Units is a innovative way on measuring the value that the platform generates into the organization in a time frame. Its calculated by the resources and features used in workareas. The following table shows the VU price for each item.
Item | Description | VUs |
---|---|---|
Work Area Users | Average count of users that belongs to the workarea. Invited users charged in other workareas are not billed to avoid billing duplication. | 20.00 |
AI Worker / AI Operator | Average count of active workshop projects that have AI Workers or AI Operators in the workarea. Multiple Workers / Operators Objects in one workshop project count as one. | 200.00 |
Workshop Projects | Average count of active workshop projects in the workarea. | 50.00 |
For DataApps the Value Units area assign by type of screens or widgets used in the application, based on the following table:
Item | Description | VUs |
---|---|---|
AI Assistant | Average count of AI Assistant agents used in the workarea DataApps, The amount of Workflow steps does not affect the cost of this item. | 200.00 |
Dashboards | Average count of dashboard screens used in the workarea DataApps. This dashboard screens can have x amount of dashlets, charts, pivot tables etc, This sub items does not count on VUs. | 15.00 |
Page Layout | Average count of page layout screens used in the workarea DataApps. This page layout screens can have x amount of sub items that does not affect the value of the item. | 10.00 |
Custom Code | Average count of custom code screens in the workarea DataApps. | 15.00 |
Calendar Screen | Average count of calendar screens in the workarea DataApps. | 10.00 |
Map Screen | Average count of map screens in the workarea DataApps. | 100.00 |
Data Edit | Average count of data edit table used in the workarea DataApps. | 5.00 |
Profile Security | Average count this feature used in the workarea DataApps. | 50.00 |
Public App | Average count of this feature used in the workarea DataApps. | 100.00 |
If there is a feature not listed in this table its cost is 0 VUs.
VUs Billing Process & Hard limits
The billing process of VUs is as follows: every day the platform generates a usage of each feature and saves the VUs used for that day. For the credit consumption process the system calculates the average usage within the time frame (month) of VUs and applies credit costs. This way if you decrease or increase the features used your billing will be reflected since the day you apply the changes.
VUs Credit Price
All resources used to generate value into your organization using Arpia Platform has a value in credits. Your workarea will be charged by usage of this resources per month.
Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
---|---|---|---|---|
Value Units (VUs) | Monthly | 1 | VU | 1 |
VUs usage and billing information is well documented in your workarea usage page. Hard limits can be set for limiting VUs overflow for controlling fixed billing costs.
Computing Hours @ Arpia Cloud
If your plan is billed by Usage Computing Credits then the following conversion table outlines the costs in credits for computing usage when applies.
Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
---|---|---|---|---|
Computing Hours does not apply when VUs are Used. | Monthly Charge | 1 | Hour | 0.90 |
Computing hours are calculated by usage in the platform and its components. Usage credits dashboard available for clear insights.
Computing Hour does not apply if your account is billed by Value Units. Computing credits can't be controlled and best for scenarios where customer prefer this model rather than fixed Value Units Billing.
GPU, Storage, AI LLM & Other Components
The following section describes the pricing and credit costs for components that are part of the offering of Arpia Platform Cloud Services.
GPU Droplets
When you need to use GPU and other special components for your organization value objetives, you can add them thru customer support chat or account executive and this items will be charged as follows.
Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
---|---|---|---|---|
AI Dedicated GPU Hours (AI/ML Models, Local GPU) | Usage | 1 | Hour | GPU Type Based |
LLMs Core Models @ Arpia Cloud
Arpia provides core llm models from most providers, if customer configures its own workarea models then no tokens are charged and usage is limited to the computing hours. If AI is used and no token provided Arpia uses its own global shared tokens for user simplicity and are billed by token usage.
Model | Tokens | Costs |
---|---|---|
openai/gpt-3.5-turbo | 1 Million | 1.50 |
openai/gpt-4 | 1 Million | 85.00 |
openai/gpt-4-turbo | 1 Million | 35.00 |
openai/gpt-4o | 1 Million | 15.00 |
openai/gpt-4o-mini | 1 Million | 1.50 |
openai/gpt-4.5-preview | 1 Million | 35.00 |
anthropic/claude-3-5-haiku-latest | 1 Million | 8.00 |
anthropic/claude-3-5-sonnet-latest | 1 Million | 25.00 |
lambda/llama3.3-70b-instruct-fp8 | 1 Million | 0.80 |
lambda/llama3.2-3b-instruct | 1 Million | 0.10 |
lambda/hermes3-405b | 1 Million | 2.50 |
lambda/qwen25-coder-32b-instruct | 1 Million | 0.35 |
lambda/llama3.2-11b-vision-instruct | 1 Million | 1.50 |
lambda/deepseek-llama3.3-70b | 1 Million | 1.00 |
lambda/deepseek-r1-671b | 1 Million | 5.00 |
xai/grok-2-latest | 1 Million | 20.00 |
xai/grok-2-vision-latest | 1 Million | 20.00 |
perplexity/sonar | 1 Million | 25.00 |
perplexity/sonar-pro | 1 Million | 25.00 |
perplexity/sonar-deep-research | 1 Million | 50.00 |
BYM (Bring your own model)
When users adds its own models to Arpia Work area there will be no charge done for LLM usage using that BYM Model.
Storage @ Arpia Cloud
The following conversion table outlines the costs in credits for storage usage when applies. We have two options for storage: Shared and Dedicated.
Shared Storage
This storage is multi-tenants for organizations that are not on a Tier plan. Its fully isolated but the resources are shared between tenants.
Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
---|---|---|---|---|
Data Storage (Shared/Dedicated SingleStore Cluster) | Monthly Daily Avg. Charge | 10 | GB | 5.00 |
Data Storage (Shared/Dedicated MySQL/MariaDB Cluster) | Monthly Daily Avg. Charge | 10 | GB | 2.50 |
Object Storage | Monthly Daily Avg. Charge | 10 | GB | 1.00 |
Dedicated Storage
On Tier plans our enterprise customers can opt for dedicated resources. Please use the following table for calculating your dedicated infraestructure. For HA setups please add +1 node for each existing node.
Resource Type | Billing Cycle | Quantity | UoM | Cost (Credits) |
---|---|---|---|---|
Dedicated Storage Node (SingleStore Node 32GB 8vCPU) | Monthly Charge | 1 | Node | 750 |
Dedicated Storage Node (MySQL/MariaDB Single Node 32GB 8vCPU) | Monthly Charge | 1 | Node | 250 |
Dedicated Object Storage Node 8GB 4vCPU | Monthly Charge | 1 | Node | 150 |
The storage of each node will be charged using the pricing table for Shared Storage.
For accounts in Tier Contracts you may be entitle to extra discounts in Computing and AI Computing Credits, please refer to your Account Manager.
Credit Billing Policy & Terms
To ensure clarity in billing, the following policies apply:
- Credit Rollover:
- Annual plans only. If you consume fewer credits than purchased, they roll over to the next billing period. Monthly plans do not allow rollovers.
- Credit Refunds:
- There are no refunds as credits are billed by usage of a past period. Adjustments may apply if consumption whas generated by system error.
- On the 5th of each month, the billing system generates and sends invoices of credits based on the previous month's usage.
- Customers can pay their invoices securely thru credit card powered by Stripe.
- Customers that have more than 2 invoices overdue can experience service interruption.
- If Customers have a prepaid amount it will be added to the customer account and recurring usage billing will be deducted from this prepaid balance.
Account Billing & Usage Support
For assistance, contact billing support via the Support Chat on the ARPIA Web Platform, accessible through the main menu:
Updated about 23 hours ago