Usage, plans and product access
ARIA separates three ideas that are easy to confuse: the plan an organization has agreed to, the product entitlements visible in the console, and the measured provider usage generated while those products run.
Current plan structure
The current public pricing page presents five tiers:
- Free — US$0
- Standard — US$59/month (approximately TTD$400/month)
- Pro — US$179/month (approximately TTD$1,220/month)
- Enterprise — US$499/month (approximately TTD$3,400/month)
- Custom — quoted
These are the current published plan amounts in the site files. Exact included usage, add-ons, specialist products and customer-specific commercial terms should still be confirmed in the applicable service/order agreement.
See Pricing for the complete current comparison.
Product access states
The customer console resolves product access separately from the visual pricing cards. Current entitlement values are:
- Active — operational access allowed.
- Trial — temporary operational access allowed.
- Locked — product visible, operational access denied.
- Setup required — visible but not operational until setup is complete.
- Suspended — operational access disabled.
The entitlement foundation currently reads organization settings such as product_entitlement.aria_sales. See Product access & plans.
Specialist ARIA products
ARIA Sales, R.I., S.A. and Probate can be shown to a customer even when they are not included in the organization's current access. This is intentional product discovery, not accidental exposure.
Locked customers should see product explanation and upgrade/contact actions. They should not receive operational APIs or another customer's data.
Activity counts Available
Overview and Usage can show organization activity derived from application records such as customers, leads, bookings and calls. These counts are useful operational signals but are not the same thing as billable provider usage.
Metered usage Provider integration pending
The application has a usage_events foundation, but the customer-facing usage-provider integration is not yet connected end to end. Voice minutes, model consumption, phone-number usage, storage and other plan meters must not be fabricated.
The Usage page therefore keeps the metered area explicitly marked Pending/zero until a real provider pipeline supplies trustworthy data.
Billing provider status
There is not currently a connected self-service billing provider automatically writing subscription changes into product entitlements. Billing and plan changes are handled through Random Target AI while that integration is built.
The intended future flow is: subscription event → organization plan/access update → product entitlement status → customer console reflects the new access. The entitlement service is already the application-side boundary for that work.
Overages and add-ons
No paid plan should be interpreted as unlimited usage. Depending on the customer's agreement, additional charges can apply to telephone service, higher usage, custom integrations, specialist products or other scoped work.
Until metered billing is connected, an overage amount shown to a customer must come from a real agreed source — not an estimated dashboard calculation.
Usage & billing in the customer console
The customer navigation uses the label Usage & billing. The page can show:
- Account activity currently available from application records.
- Metered-usage placeholders explicitly marked Pending.
- A Product access list showing the state of each ARIA product for the organization.
A self-service invoice history, payment method manager and automatic subscription checkout are not yet part of this foundation.
Known limitations
- Provider-level metered usage is not yet connected to the customer dashboard.
- Automatic subscription-to-entitlement synchronization is not yet connected.
- There is no full self-service invoice/payment portal in the console yet.
- Approximate TTD values on the public pricing page are informational approximations; the commercial agreement controls actual billing.