Connectors define how enterprise signals reach the Systemiq platform and become available for modeling.

Middleware is used where credentials, transformation logic, enterprise network boundaries, or local execution requirements sit between source systems and the hosted platform.

Typical sources

• APIs
• Files
• Business tools
• Event streams

When direct connectors are enough

• The source system can be reached from the hosted platform boundary.
• Credentials and access controls can be handled without customer-side runtime logic.
• Payloads can be consumed with limited preprocessing before modeling.

Middleware role

• Credential brokering and controlled access to enterprise systems.
• Payload normalization before data enters the hosted platform.
• Protocol translation or enterprise-specific extraction logic.
• Enterprise-side execution where local or on-prem components are required.
• Controlled movement of source signals before they enter the platform model.

Design boundary

• Connectors and middleware move signals into Systemiq.
• Systemiq then owns the modeling, persistence, and query surfaces built on top of those signals.
• This is why ingestion should be explained separately from the operational model itself.