Skip to content

Solomon is in private preview with a small group of design partners.Apply to join

Agentic security operations

Every alert, answered with evidence.

Solomon’s agents work an alert the way your best analyst would: they ask the questions, run the queries and reach a verdict you can check line by line.

Private preview. Work email required.

Interested partner? Contact usAlready a customer?

InvestigateSOL-2291
working
High severityImpossible travel · svc-deploy@northwind-lab
Verdict: Malicious0.943 of 3 evidence items agree
Recommend Revoke sessions for svc-deployapproval required

A simulated investigation. Every line links to its evidence.

The SOC today

Security operations still run on human attention.

The alert is in one console, the identity history in another, the cloud logs in a third. An analyst holds the case together in their head, then closes the tab, and the context is gone. Next week the same pattern on a different host starts from zero.

One incident scattered across four toolsSix related events sit in four separate tool timelines among unrelated noise. Solomon connects them into a single case.EndpointIdentity providerCloud auditTicket queueSOL-2291 · one case · six events · four tools
  • Context lives in people.

    When an analyst moves on, their judgment leaves with them.

  • Every alert starts cold.

    Tools remember events, not what the team concluded about them.

  • Volume decides, not risk.

    Queues are worked in arrival order because there’s no time to rank them.

The platform

Six agents. One memory.

Each Solomon agent does one job in the SOC. They read from and write to the same memory of your environment, so what Investigate learns on Monday is what Triage knows on Tuesday.

Six Solomon agents reading from and writing to one shared memoryShared memoryentitiesfacts over timeverdicts
Triage
Investigate
Hunt
Detect
Respond
Ask Solomon
Shared memory: entities, what was true about them and when, and every verdict your team has reached.

Memory

Solomon remembers how your cloud identities and resources behaved, not just what happened.

For cloud identities and resources, Solomon keeps a timeline of facts: what was true, from when, until when, and when Solomon learned it, so an investigation can ask what was true at the moment of the incident.

iam_principalsvc-deploy
15 Sep – 14 Oct 2026
Sign-ins
Role
readerpoweruser
MFA
push, enrolledreset, re-enrolled
Peers
198.51.100.23203.0.113.140
Verdicts
15 Sep14 Oct

As of 4 Oct

role
reader
mfa
push, enrolled
peer
198.51.100.23
sign-ins that day
4

Changed in the prior 7 days

  • No changes. Behaviour matches the baseline.
  • As it was.

    Ask what was true at the moment of the incident, not what’s true now.

Built to be trusted with your SOC.

  • Evidence for every conclusion

    Every verdict lists the questions asked, the queries run and the results that support it. If it can’t be checked, Solomon doesn’t claim it.

  • Approval by default

    Response actions wait for a human approval by default, and an emergency stop puts your tenant in observe-only mode. Destructive actions always show their blast radius and rollback first. Per-action autonomy levels are on the roadmap.

  • Learns from your analysts

    Correct a verdict in plain language, choose where the correction applies and for how long, and see which past cases it would have changed.

  • Works on your existing stack

    Solomon reads from the cloud services you already run, with identity, endpoint and SIEM connectors in validation. No rip and replace.

  • Multi-tenant from day one

    Each customer’s data is isolated in its own schema, and tenancy is enforced on every request. Built for MSSPs and multi-entity companies as much as single teams.

  • Customer-cloud deployment

    Running Solomon in your own cloud account is in design-partner preview, available on request.

What design partners measure.

Median time from alert to verdict
Median time from alert to verdict{{METRIC: median time from alert to verdict}}
Alerts closed without a human
Alerts closed without a human{{METRIC: share of alerts closed without a human}}
Investigation time saved
Investigation time saved{{METRIC: investigation time reduction}}
Verdicts corrected by analysts
Verdicts corrected by analysts{{METRIC: analyst-corrected verdicts per 1,000}}

Figures will come from design-partner deployments and be published with methodology.

Design partners

Shape Solomon with us.

We’re working with a small number of security teams before general availability. Partners get early access, a direct line to the engineers building Solomon, and a say in what ships next.

Apply to be a design partner

What partners get

  • Hands-on deployment support
  • Weekly working sessions with the product team
  • Early pricing for the length of the program

What we ask

  • A real alert stream to work on
  • An hour a week of feedback
  • Permission to publish anonymised results, if you agree to it

See Solomon work a case from your own alerts.

Request access and we’ll set up a working session on your stack.

Private preview. Work email required.