Component architecture
AITHANEX is a modular software, data, operations, and integration platform for connected systems.
It connects devices, data, and workflows through products used separately or together.
| Software product | Technical function |
|---|---|
| Things AITHA | Operational IoT platform for telemetry, control, rules, assets, commands, and history. |
| AITHA Inbox | Conversational product for omnichannel inboxes, bots, human support, and a mobile agent app. |
| AITHANEX AI | Applied AI platform for analysis, assistance, classification, and replies supported by authorized data. |
The platform’s common foundation centralizes permissions, history, auditing, segmentation, and traceability for every product.
Platform capabilities
| Area | Scope |
|---|---|
| Operational data | Telemetry, states, events, history, and alarms. |
| Automation | Rules, workflows, remote actions, and operational escalation. |
| Security | Users, permissions, segmentation, and traceability. |
| Integration | APIs, connectors, internal systems, and external platforms. |
| Operations | Monitoring, remote control, maintenance, and asset tracking. |
| Applied AI | Assistance, classification, document search, reporting, and analysis of authorized data. |
Ingestion protocols and APIs
The platform integrates multiple protocols and exchange mechanisms, coordinated by each product according to its function:
| Mechanism | Main product |
|---|---|
| MQTT | Things AITHA: real-time device telemetry. |
| HTTP / CoAP | Things AITHA: request-based ingestion and resource-constrained devices. |
| WebSocket | Things AITHA: real-time updates to the web interface. |
| REST APIs | All products: integration with external systems. |
| Webhooks | AITHANEX Agents, AITHANEX Inbox and AITHANEX AI: receiving and sending events. |
| Digital channels | AITHANEX Inbox (channels) and Agents (automation): web, WhatsApp, Instagram, email, and others. |
Common data model
The platform maintains shared entities that provide consistency across all products:
| Entity | Description |
|---|---|
| User | Person with system access and defined role and permissions. |
| Tenant / Customer | Logical segmentation separating data, operations, and configuration. |
| Installation | Grouping of assets, devices, or services by project or location. |
| Permission | Rule defining what each user can do with each resource. |
| History | Record of events, actions, changes, and traceability over time. |
| Audit | Record of access, operations, and changes for complete traceability. |
Common technical scenarios
| Scenario | Use |
|---|---|
| Telemetry and control | Connect devices to Things AITHA to receive data and execute actions. |
| Omnichannel support | Centralize conversations in Inbox and automate with Agents, routing to human operators. |
| Supervised AI | Add AITHANEX AI when there is a verifiable objective and authorized data. |
| OEM or white label | Adapt visual identity, domain, and modules for the end customer. |
| Business integration | Connect ERP, CRM, email, APIs, or internal systems without replacing what already works. |
Integrations and limitations
Capabilities:
- Deploy software products separately or in combination according to the project.
- Integrate system devices and third-party hardware with a compatible protocol.
- Connect external systems through APIs, webhooks, or project-defined connectors.
- Operate in OEM or white-label mode by adapting visual identity and domain.
- Separate customers and projects into independent tenants with isolated data and permissions.
Limitations:
- Devices must be able to publish data or integrate through a gateway, API, or compatible protocol.
- Integration with external systems requires APIs, credentials, and exchange rules defined per project.
- Each product’s capabilities depend on the agreed deployment and configuration.
Security
| Area | Scope |
|---|---|
| Users and permissions | Role-based access control for each product and system resource. |
| Segmentation | Logical isolation of data, operations, and configuration by tenant. |
| Traceability | Record of actions, changes, and access throughout the operational lifecycle. |
| Communication | Encryption according to deployment configuration and enabled protocols. |
| Audit | Operations log for monitoring, support, and incident investigation. |
Multi-tenant
AITHANEX supports multi-tenant operation with logical separation by customer and/or installation.
Each tenant has separate data, products, permissions, and configuration. Cross-tenant access requires explicit system administration.
OEM mode also supports adapting the visual identity, domain, and visible modules for each end customer.
Integration requirements
| Area | Requirement |
|---|---|
| Devices | Ability to publish data or integrate through a gateway, API, or compatible protocol. |
| External systems | APIs, credentials, and exchange rules defined by project. |
| Users | Roles, permissions, and segmentation configured for each deployment. |
| Data | Minimum asset, event, state, and metric model for traceable operations. |
Related products
| Product | Technical relationship |
|---|---|
| Things AITHA | IoT platform for telemetry, control, and connected asset management. |
| AITHANEX AI | AI platform for analysis, classification, and assisted replies. |
| AITHA Inbox | Omnichannel conversational management with bots and human support. |
| AITHA IoT Core | Hardware and software core for connected products. |
| Router AITHA IoT LoRa | Dedicated LoRa link to the platform over 4G, Ethernet, or Wi-Fi. |
| AURA X36 | Gateway for distributed signals, sensors, and actuators. |