Supported services
Find product connection coverage, service-specific enrollment, and the Status general-availability requirement.
Connector supports scoped information exchange between Infra and Guard, plus service-specific links for Infra hosted capacity and Guard edge protection. Each connection type has its own approval and readiness checks.
Product connections
The product matrix distinguishes available connections from release requirements:
| Product | Connector availability | Connection purpose |
|---|---|---|
| Infra | Supported | Share selected infrastructure inventory and operational state; receive mapped security summaries |
| Guard | Supported | Associate assets with Infra resources; share selected security summaries |
| Custom integrations | Supported through the Connector API | Read approved context, publish external summaries, and receive signed events |
| Status | Support begins at Status general availability | Setup is unavailable before general availability |
Existing Status integrations retain their own setup and permissions.
Service connections
These links connect a product installation to a Solarius-operated service:
| Connection | Deployment | Canonical setup |
|---|---|---|
| Infra to hosted capacity | Self-hosted Infra to Solarius-hosted resources | Infra Connector |
| Guard to the DDoS edge | Self-hosted Guard to the Solarius edge | Guard DDoS Connector |
Approving an Infra–Guard product connection does not approve either service connection. Existing edge protection or hosted-capacity delegation also does not grant cross-product information exchange.
Local Infra fleet operations do not require a hosted-capacity Connector. Guard scanners, endpoint controls, and local investigations do not depend on its DDoS Connector. Feed synchronization and remote security operations center collaboration use their own service connections.
External destinations
Customer-owned applications use custom integration connections and the Connector API for shared inventory, external context, and signed events. Each application has its own registration, workers, and approved grants.
Product-specific notifications and security information and event management exports retain their native integration workflows. Their credentials and retries are separate from a Connector subscription.
For more information about external destinations, see Guard notifications and SIEM integrations and Solarius connected applications.