SIGQ Ships Incident Lake Self-Hosted For Closed-Network AI Response
The pitch answers a constraint that keeps incident records out of cloud AI: the organizations most exposed to ransomware are often the ones contractually or physically barred from sending intrusion data to an outside service.
Reporting from 1 source: ASCII.jp.
SIGQ Inc. has begun offering Incident Lake Self-Hosted, a packaged version of its AI incident commander that runs inside a customer's VPC, data center, or on-premises network. The self-developed incident-response model Otter runs in the same environment, so no inference goes to an external Public LLM API. SIGQ cites National Police Agency materials reporting 123 ransomware incidents in the first half of 2026.
The product ships as a Docker container and can be deployed alongside existing monitoring and SIEM tooling. SIGQ names ClickStack, Grafana, and Wazuh as components that can run with it, and says it integrates with monitoring infrastructure such as Zabbix.
The market argument rests on confinement. Intrusion records carry the details of the breach, unremediated vulnerabilities, and customer or patient data, and SIGQ points to finance, manufacturing OT environments, municipalities, healthcare, and critical infrastructure as settings where connection to the internet is off the table by default. The same National Police Agency materials cited by the company put about 60 percent of organizations at recovery costs of 10 million yen or more.
Synthesized by Yomimono from the 1 cited source below, including Japanese-language reporting where cited, then editorially reviewed before publishing.