Device component management
AITHANEX is a modular software, data, operations and integration platform for connected systems.
Acts as a common technology base to connect devices, data and operational flows. Its products can be used separately or combined depending on the project.
| Software product | Technical function |
|---|---|
| Things AITHA | Operational AITHANEX IoT platform for telemetry, control, rules, assets, commands and history. |
| AITHANEX Inbox | Conversational product for an omnichannel tray, bots, human support and an agent mobile app. |
| AITHANEX AI | AITHANEX Applied AI platform for analysis, assistance, classification and replies backed by authorized data. |
The platform common base centralizes permissions, history, audit, segmentation and traceability for all products.
Platform capabilities
| Area | Scope |
|---|---|
| Operational data | Telemetry, states, events, histories and alarms. |
| Event storage | Rules, flows, remote actions and operational scaling. |
| Connected sensors | Users, permissions, segmentation and traceability. |
| Integration | APIs, connectors, internal systems and external platforms. |
| Operation | Monitoring, remote control, maintenance and asset tracking. |
| Applied AI | Assistance, classification, document retrieval, reports and analysis over authorized data. |
Platform ingestion and API connectivity
The platform integrates multiple protocols and exchange mechanisms, coordinated from each product according to its function:
| Mechanism | Main product |
|---|---|
| MQTT | Things AITHA: real-time device telemetry. |
| HTTP / CoAP | Things AITHA: on-demand ingestion and resource-limited devices. |
| WebSocket | Things AITHA: real-time updates to the web interface. |
| APIs REST | All products: integration with external systems. |
| Webhooks | AITHANEX Agents, AITHANEX Inbox and AITHANEX AI: event reception and emission. |
| Digital channels | AITHANEX Inbox (channels) and Agents (automation): web, WhatsApp, Instagram, email and more. |
Common data model
The platform keeps shared entities that give coherence to all products:
| Entity | Description |
|---|---|
| User | Person with system access, role and defined permissions. |
| Tenant / Customer | Logical segmentation separating data, operation and configuration. |
| Deployment guide | Grouping of assets, devices or services by project or location. |
| Permission | Rule that defines what each user can do on which resources. |
| Historical | Log of events, actions, changes and traceability over time. |
| Automation engine | Log of access, operation and changes for full 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, escalating to human operators. |
| Supervised AI | Add AITHANEX AI when there is a verifiable goal and authorized data. |
| OEM or white label | Adapt visual identity, domain and modules to the end customer. |
| Integration empresarial | Connect ERP, CRM, email, APIs or internal systems without replacing what already works. |
Protocol integration and limits
What it can do:
- Deploy the software products separately or in combination depending on the project.
- Integrate the system’s own devices and third-party hardware with a compatible protocol.
- Connect external systems via APIs, webhooks or connectors defined per project.
- 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.
Limits:
- Devices must be able to publish data or integrate via gateway, API or compatible protocol.
- Integration with external systems requires APIs, credentials and exchange rules defined for each project.
- Each product’s capabilities depend on the deployment and agreed configuration.
Connected sensors
| Area | Scope |
|---|---|
| Users and permissions | Role-based access control for each product and system resource. |
| Segmentation | Logical isolation of data, operation and configuration per tenant. |
| Traceability | Log of actions, changes and access across the operational cycle. |
| Communication | Encryption based on deployment configuration and enabled protocols. |
| Automation engine | Operations log for tracking, support and incident investigation. |
Multi-tenant
AITHANEX supports multi-tenant operation with logical separation by customer and/or installation.
Each tenant has its own data, products, permissions and configuration. It cannot access other tenants without explicit administrative enablement.
The OEM model also lets you adapt visual identity, domain and visible modules for each end customer.
Integration requirements
| Area | Requirement |
|---|---|
| Devices | Ability to publish data or integrate via gateway, API or compatible protocol. |
| External systems | APIs, credentials and exchange rules defined per project. |
| Users | Roles, permissions and segmentation configured for each deployment. |
| Data | Minimal model of assets, events, states and metrics for traceable operation. |
Products relacionados
| Product | Technical relationship |
|---|---|
| Things AITHA | AITHANEX IoT platform for telemetry, control and connected asset management. |
| AITHANEX AI | AITHANEX AI platform for analysis, classification and assisted replies. |
| AITHANEX 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 uplink to the platform over 4G, Ethernet or Wi-Fi. |
| AURA X36 | Gateway for distributed signals, sensors and actuators. |