How the ARIA platform fits together
ARIA is one organization platform with multiple AI workers and workspaces. Products can operate independently, while shared account, customer, lead, conversation, knowledge, usage and entitlement foundations let approved workflows connect without merging one customer's data with another's.
Organizations
An organization is the customer account boundary. The first customer owner can create a new organization through self-service registration. The organization's users, customers, leads, conversations, knowledge, usage, settings, product access and specialist records belong to that organization.
Random Target AI maintains its own separate internal organization for company operations.
Accounts and roles
A signed-in user belongs to an organization and holds a role. Customer roles currently include Admin, Manager and Member. A role controls what that user may do; the organization identifier controls which customer's data those permitted actions can reach.
Self-service registration creates the first customer Admin/owner. A complete self-service invite workflow for additional team members is not yet available, so additional account provisioning should be coordinated rather than creating duplicate organizations.
The ARIA product catalog
The current product catalog exposes seven named capabilities:
- ARIA Voice
- ARIA Agent
- ARIA IDE
- ARIA Sales
- ARIA R.I.
- ARIA S.A.
- ARIA Probate
The catalog describes the product identity, route, category and customer-facing explanation. Access is resolved separately through entitlements.
Product entitlements
The current foundation stores product access in organization settings using keys such as product_entitlement.aria_sales. Supported states are Active, Trial, Locked, Setup required and Suspended.
Active and Trial are the operationally accessible states. A Locked product remains discoverable in the console but does not receive operational access. See Product access & plans.
Core products
ARIA Voice
Handles customer-facing voice and text conversations on supported website and telephone channels. It can create conversation, customer, lead, booking and call records when the relevant actions are configured.
ARIA Agent
The general AI work assistant for research, writing, files, planning, analysis and supported business workflows.
ARIA IDE
The software-development workspace inside ARIA Agent. It is not a separate underlying assistant or account. Its product direction is real-time voice conversation while ARIA works with the connected software project and approved development tools.
Specialist products
ARIA Sales
Prospecting and sales-operations workspace. The current foundation has an entitlement-aware customer Sales path and separate Random Target AI internal Sales workspace.
ARIA R.I.
Resource Intelligence for bills/documents, comparisons, cost leakage, audits and reporting. Dashboard entitlement presence exists; full customer operational integration remains a separate integration task.
ARIA S.A.
Authorized security monitoring, alert triage, evidence collection and incident-support workflows. Customer product presence exists; full customer operational integration remains a separate integration task.
ARIA Probate
Probate-support workflow for case information, documents and progress. Customer product presence exists; full operational integration remains a separate task.
Shared records
Where appropriate, ARIA products use shared organization records rather than creating disconnected copies. Examples include customers, leads, conversations, calls, bookings, knowledge and usage events.
Shared does not mean every product automatically sees every field. Application logic, roles, product access and tool permissions still determine what a user or product can read or change.
Product handoffs
A connected workflow can move work through shared records. For example:
- ARIA Voice captures a prospect's contact information and need.
- The lead record is stored inside the customer's organization.
- If ARIA Sales is enabled, the sales workflow can work the organization's own lead/prospect data.
- ARIA Agent can research, draft or analyze material related to the same business work.
- If the request becomes software work, ARIA IDE can continue inside a connected project without becoming another assistant identity.
Not every possible handoff is automatically enabled. A handoff depends on the products, integrations and permissions configured for that organization.
Organization isolation
Multi-tenant safety depends on every customer-facing data path being scoped by the authenticated user's organization. The ARIA Sales repositories, for example, include organization_id in prospect, activity and prospecting-run reads and writes. That organization condition must never be removed merely because an API also has a role check.
Random Target AI internal operations
Random Target AI internal users can have an internal console mode. Standard customers do not see that switch and cannot enter internal operations through a customer Admin role. Internal access requires the Random Target AI organization plus an authorized internal role.
Internal ARIA Sales remains a separate route from customer Sales even though both can reuse shared presentation/components.
Adding future ARIA products
The purpose of the product catalog and entitlement layer is to avoid redesigning authentication and the customer console every time a new specialist AI worker is introduced. A future product can be added to the catalog, given an organization entitlement, connected to the appropriate shared records, and protected by product-specific page/API guards.