Astral Implementation

Astral is implemented following Inopli’s native multi-tenant architecture, designed to support both managed security service providers (MSSPs) and end organizations within a single hierarchical structure. This architecture is based on a parent company and child companies model, enabling scalable deployment while maintaining strict logical separation of data and access.

In this model, the parent company typically represents the MSS or central security organization responsible for managing operations, governance, and visibility across multiple environments. Child companies, referred to as End Companies, represent individual customer environments or organizational units. Each child company operates as an independent security domain within the Inopli platform.

Astral is deployed as a dedicated instance for each child company. This design ensures full logical segregation of data, configurations, and access controls between environments. Users can only access data associated with the companies to which they are explicitly authorized, preventing cross-visibility and ensuring compliance with security and data isolation requirements.

The architecture does not impose limitations on the number of Astral instances that can be deployed. Organizations can onboard any number of child companies, each with its own Astral instance, without architectural constraints. Likewise, there are no fixed limits on daily data ingestion, allowing Astral to scale according to the operational and monitoring needs of each environment.

This implementation model provides flexibility for growth, supports diverse operational requirements, and aligns with the needs of both MSSPs and internal security teams. By combining hierarchical management with per-instance isolation, Astral enables scalable, secure, and controlled SIEM deployments within the Inopli ecosystem.