EmilyAI · For organisations that run their own SOC
You have the SOC.What you are short ofis capacity.
EmilyAI can be licensed to run on your infrastructure and read from the SIEM you already have. She reviews the data hour by hour, writes down what she finds with the evidence, and leaves the decisions to your analysts.
In live service since April 2018Runs on your infrastructureReads your SIEMSigned updates every five minutesYour analysts decide
The same Emily, wherever she runs.
If you already run a SOC, with a SIEM you are happy with and analysts on shift, you do not need another platform. You need more hours of careful looking than your team has in a day. EmilyAI is the AI SOC analyst that has worked at the core of our own SOC since 2018, and she can be licensed to do the same job inside yours. She stays current because every Emily, wherever she runs, calls the Hive every five minutes for cryptographically signed updates, tuning and threat intelligence.
- Licensed
- To you, on your infrastructure
- Reads
- Your SIEM
- Verified by
- Your analysts, who decide what happens next
- Tuned by
- Us, through signed updates from the Hive
- Price
- Quoted after a technical briefing
Division of labour
What you supply, and what we supply
You: the SIEM and collection
Your own agents and log feeds, and a SIEM you are content with. Emily reads from it.
You: the analysts
People on shift who verify her findings and decide what to do about them.
You: reporting and wider response
Your own case management and reporting, and your SOAR if you want response orchestrated beyond her own automated actions.
We: EmilyAI
Licensed to you and running on your infrastructure.
We: onboarding and tuning
Getting her working against your data, and keeping her tuned as your estate and the threats change.
We: the Hive
Signed updates, commands and threat intelligence every five minutes, from our own honeypots and sensors, ipinsights.io, anonymised telemetry and commercial and open feeds.
Her record in our own SOC, August to October 2026
89%
Of the quarter's investigations were first raised by Emily
5,771
Dynamic blocklist updates, more than 60 a day
1,390
Abuse reports sent to the networks behind attacking machines
- Of the quarter's investigations were first raised by Emily: 56 of 63 investigations and threat advisories, in our SOC
- Dynamic blocklist updates, more than 60 a day: EmilyAI's own records of the actions it took, in our SOC
- Abuse reports sent to the networks behind attacking machines: About 15 a day, in our SOC
What changes
What you do not get on this route
Taking Emily on her own is not a lesser version of SOC365, but it is a different one, and it is better to be plain about the difference.
- Pulse is not included. Pulse is the portal our own analysts work in. On this route your team uses its own case management and reporting.
- Our analysts are not included. Your analysts verify her findings and decide. That is the point: you already have them.
- The extension modules are not included. Deception, the on-site appliance for operational technology, cloud monitoring, identity reporting and data loss prevention each depend on infrastructure we run, so they come with SOC365.
If you later decide you would rather we ran the whole thing, nothing is wasted in the move. It is the same Emily and the same Hive throughout. The EmilyAI page sets the two routes side by side.
Trust
What your security team will want to see
- _01How the update channel is securedThe security architecture and cryptographic specification of the channel between Emily and the Hive, available under a non-disclosure agreement.Under NDA
- _02What she is allowed to doHer automated defences block clear-cut attacks at the firewall and on dynamic blocklists, and report the attacking machine to its network. She never contains a machine or locks an account herself.Limits
- _03Her recordEmilyAI in Numbers reports what she and our engineers did in a quarter.Published
- _04Her working, on a real nightA technical briefing walks through an anonymised incident: what she saw, what she wrote, and what the analyst did next.Briefing
Questions
Questions from teams that run their own SOC
What do we need in place to run her?
A SIEM you are happy with, your own collection, analysts on shift to verify her findings, your own case management and reporting, and a SOAR if you want response orchestration beyond her own automated actions. We provide onboarding and tuning.
Does our data leave our network?
Emily runs on your infrastructure and reads your SIEM in place. What passes between her and the Hive is set out in the security architecture document, which your security team can read under a non-disclosure agreement before you commit to anything.
Can she act on our systems without asking?
Only in one narrow way. When an attack is clear-cut, her automated defences block it at the firewall and on dynamic blocklists and report the attacking machine. Everything that needs judgement is raised to your analysts with the evidence.
What does it cost?
We do not yet publish a price for EmilyAI on her own. It is quoted after a technical briefing, and we would rather say so than print a starting figure that means little.
We run a SOC for our own customers. Can we use her?
Talk to us. We have not published terms for service providers, and would rather agree them with you than guess at them here.
Start a conversation
See her working before you decide anything.
A thirty-minute technical briefing, using an anonymised incident from last month: what she saw, what she wrote, and what the analyst did next.