REST API
Customer-authorised application events and actions through a documented API boundary.
Planned / not connectedOMNICONNECT
Meet your environment.
Where it already is.
A vendor-neutral connection strategy, not a claim of universal support. Each integration needs to be implemented, validated and explicitly authorised.
Product preview
Designed around evidence.
Capabilities in development.
Webhooks
Signed inbound events with replay protection, source validation and delivery visibility.
Planned / not connectedSyslog
Traditional infrastructure telemetry through a customer-managed collection route.
Planned / not connectedOpenTelemetry
Application context and correlated observability signals, with appropriate data minimisation.
Planned / not connectedMCP gateway
An AI tool boundary designed to verify identity, scope and downstream authorisation.
Planned / not connectedOmniGuard SDK
Developer instrumentation and policy integration. Wrappers alone are not a non-bypassable boundary.
Planned / not connectedEndpoint collector
An operating-system-specific collector with signed delivery and narrowly scoped privileges.
Planned / not connectedIdentity connectors
Authentication, membership and permission evidence from supported identity sources.
Planned / not connectedCloud audit sources
Resource inventory and control-plane events from explicitly authorised cloud environments.
Planned / not connectedNo matches. Try “AI”, “logs”, “cloud” or “API”.
No partner relationship, certification or currently working connector is implied by this roadmap.
Integration means more than ingestion.
Visibility
What evidence can the source actually provide? What is missing, delayed or incomplete?
Planned capabilityAuthorisation
What scope is needed? Can read-only collection be separated from response permissions?
Planned capabilityVerification
Can the system confirm an action succeeded, expired or was reversed? Unsupported actions must remain unavailable.
Planned capability