Skip to content

53,600 AI-swarm attacks. Every one stopped in the kernel. 0 bytes leaked.See the evidence

Technology partners

Build a Solomon OmniMesh connector.

Solomon OmniMesh connects the security tools customers already run, with 35 native connectors in the catalog today. If your product is not one of them yet, let’s build it together.

What a connector does

Your signals, in every investigation.

A connector is more than a log forwarder: it makes your product part of how Solomon investigates and responds.

01 · Pull

Out-of-band ingestion

The connector reads from your product's own API, so nothing sits in the path of the tool. Customer credentials are kept per tenant in Vault and never logged.

02 · Normalize

One record format

Your events are normalized to OCSF and land in the same per-tenant pipeline as every other source, including the Solomon eBPF Client's own telemetry.

03 · Investigate

Part of every investigation

Solomon SOC agents correlate your signals with identity, cloud and endpoint data, and follow one user, host or IP across all of them.

04 · Act

Actions, with a person in charge

Where your API allows it, agents can propose actions in your product. Anything with blast radius waits for a human approval.

Categories

Where connectors plug in.

The catalog is organized by the job a tool does in the SOC.

  • Identity & Access
  • Endpoint & Fleet
  • Cloud & Infrastructure
  • Network & Perimeter
  • Threat Intel & Vulnerability
  • ITSM & Collaboration
  • SIEM & Log Platforms
How Solomon OmniMesh works

How it works

From first call to catalog.

  1. Step 1

    Tell us about your product

    What it sees, how its API authenticates, and which actions it exposes.

  2. Step 2

    Scope the connector together

    We agree on the data to pull, its OCSF mapping and any remediation actions.

  3. Step 3

    Ship it in the catalog

    Once built, it appears in the integrations catalog and the portal's guided setup, like every other connector.