SECURITY INTELLIGENCE. UNDER YOUR CONTROL.

See more.
Respond
smarter.

Turn your event stream into a clear picture of threats.
Logs, behavior analytics and response —
one platform, on your infrastructure.

Self-hosted Linux · Windows · macOS agents API-first
YOUR INFRASTRUCTURE. YOUR DATA. YOUR CONTROL.Scroll to explore
FROM SOURCE
TO DECISION

Syslog / RFC 3164 · 5424

FQL / SEARCH & ANALYTICS

Sigma / DETECTION

UEBA / BEHAVIOR

SOAR / RESPONSE

01 /THE COMPLETE PICTURE

Less noise.
More understanding.

From the first event to the full investigation.
FrySIEM connects logs, users and assets
so you can see the story behind every signal.

FrySIEM / WORKSPACEProduct preview
01 / 05Infrastructure health, key events and security risks in one workspace.
REAL PRODUCT. REAL VISIBILITY.
01

Collect what mattersNetworks, endpoints, clouds and applications.

02

Connect the dotsEvents, behavior and the context behind every entity.

03

Move from insight to actionInvestigations, playbooks and notifications.

02 /CAPABILITIES

Everything you need.
One connected platform.

10core capabilities.
One connected workflow.
01 / COLLECT

Every event. One stream.

Collect syslog, CEF, LEEF and JSON over UDP, TCP, TLS, RELP and HTTP. Connect native Linux, Windows and macOS agents, distributed collectors and cloud sources.

SYSLOGHTTP / OTLP JSONAGENTS
02 / NORMALIZE

Different logs.
A common language.

Parser packs, normalized fields and GeoIP / ASN enrichment turn raw messages into data you can investigate.

03 / EXPLORE

Ask the right question.
Find the exact answer.

Search with FQL, build aggregations and drill down from the big picture to the individual event.

Fry Query Language
host:fw* and severity<=3
| stats count() by src_ip
| sort -count | limit 20
04 / DETECT

Give threats
a recognizable shape.

Correlation rules, Sigma imports and MITRE ATT&CK mapping. Test detections against history and keep alert noise under control.

05 / UNDERSTAND

Spot what falls
outside the pattern.

UEBA learns how users and hosts normally behave. Anomalies, peer comparisons and risk scores bring unusual activity into focus.

06 / INVESTIGATE

Context around
every incident.

Entity 360 connects users, hosts and addresses. Assign cases, track stages and deadlines, and preserve evidence throughout the investigation.

07 / RESPOND

Response,
on your terms.

Playbooks connect enrichment, notifications and actions. Add human approval before blocking an address or changing an account.

SLACKTEAMSJIRA
08 / VISUALIZE

Data that
tells a story.

Dashboards, maps, heatmaps and a report library. See the security overview, then explore the details of each source.

09 / CONTROL

Defined access.
Clear boundaries.

Tenant isolation, role-based access and audit trails. Connect your enterprise identity provider through LDAP, OIDC or SAML.

10 / SCALE

Start with one node.
Grow with your data.

Embedded DuckDB or ClickHouse for larger volumes. A disk-backed WAL, retention policies and active-passive HA support resilient operations.

Find your deployment

03 /AI INTEGRATION

AI on your side.
Under your control.

Connect the assistant your analysts already use.
Keep an eye on the AI
your company runs.

ASSISTANTS · MODEL CONTEXT PROTOCOL

Ask FrySIEM in plain language

FrySIEM is an MCP server. Analysts ask what happened last night, who the riskiest users are or why an anomaly fired. The assistant answers from your events, incidents, cases, Entity 360, behavior analytics and reports, and drafts a triage or an entity summary with ready-made prompts.

  • Claude Code · Desktop
  • OpenAI Codex CLI
  • Cursor
  • VS Code · GitHub Copilot
  • Any MCP client
THIRD-PARTY AI · DETECTIONS

See the AI your company runs

Ready-made detections you can switch on: removed AWS Bedrock guardrails and invocation logging, unusual model access, local LLM tools and model downloads on endpoints, new AI agents and MCP connections in Notion.

  • AWS Bedrock
  • Ollama
  • LM Studio
  • Hugging Face
  • Notion AI
  • GPT4All, OpenRouter and more
01

Granted, not taken

On a consent screen the analyst grants read-only triage or analyst rights, never more than they have. Revoke at any time.

02

Pseudonyms by default

Without the reveal permission the assistant sees stable pseudonyms in behavior analytics, not names. Works council mode included.

03

Every call audited

Tool, arguments, duration and outcome of every call are logged, with rate limits and response caps per token.

04

Your choice of model

FrySIEM needs no public endpoint and sends nothing out itself. Read-only by default; playbooks start as dry runs. Pick a local model to keep everything in-house.

Product names and logos are trademarks of their respective owners and are shown to indicate compatibility. Third-party AI detections are part of the extended rule packs and may need setup.

04 /FROM SIGNAL TO ACTION

A connected workflow.
At every step.

One platform for the entire process.
Every next step carries the context
of the one before it.

01 ↗

Collect

Bring in events from across your infrastructure and normalize their fields.

INGEST → NORMALIZE
02 ↗

Detect

Combine rules, behavior and context to identify the signals that matter.

CORRELATE → PRIORITIZE
03 ↗

Investigate

Reconstruct the sequence of events and gather evidence in one place.

EXPLORE → INVESTIGATE
04 ✓

Respond

Run a playbook, notify the team and document the outcome.

RESPOND → DOCUMENT

05 / DISTRIBUTED COLLECTION

Every site connected.
One place in control.

Keep collection close to the source.
Bring visibility and management together
across branches, data centers and cloud environments.

Collect locallyBring remote sources into the platform through a nearby collector.

Manage centrallyKeep your collector infrastructure under one management center.

Investigate togetherFollow activity across sites from one security workspace.

NATIVE ENDPOINT AGENTS

Three operating systems.
One managed fleet.

Bring endpoint logs into the same workflow. Enroll agents, manage collection policies and monitor their health centrally.

Linux

Collect journald and file logs from your Linux servers.

NATIVE AGENT

Windows

Collect Windows Event Logs and security events from your endpoints.

NATIVE AGENT

macOS

Bring Mac log sources into the same centrally managed fleet.

NATIVE AGENT

06 /YOUR ECOSYSTEM

Built for
your ecosystem.

From firewalls and identity directories to cloud services and issue trackers. Collect data and take action through the tools your team already uses.

Works where your data lives
SOURCES & DEVICES
FortinetCiscoMikroTikPalo AltoWindowsLinux
CLOUD & IDENTITY
aws⌣Entra IDActive Directory
NOTIFICATIONS & RESPONSE
SlackTeamsJiraServiceNowTelegramWebhooks

REST API + MCP for your integrations and AI agents

07 /YOUR SCALE

Your data.
Your environment.

Choose the architecture that fits.
The same query language and interface
stay with you as your system grows.

01 / EMBEDDED

A compact start

For pilots, smaller environments and standalone installations.

  • One server binary
  • Embedded DuckDB + Parquet
  • Linux, Windows and macOS
  • No separate log database server
Explore the platform
02 / CLICKHOUSEMORE DATA

Room to grow

For centralized collection and analysis of larger event streams.

  • ClickHouse columnar storage
  • Retention policies and storage tiers
  • Guided migration from embedded
  • The same FQL and familiar Web UI
Explore the features
03 / HIGH AVAILABILITY

Keep operations running

For environments that need a standby node and controlled failover.

  • Active-passive pair on Linux
  • WAL and metadata replication
  • Automatic failover with a third vote
  • Role and health monitoring
Read the FAQ

08 /THE DETAILS

Good
questions.

What to know
before your first deployment.

How is FrySIEM different from a syslog server?

Log collection is just the beginning. FrySIEM adds normalization, FQL search, correlation, UEBA, Entity 360, investigations and response playbooks. Every stage works with shared events and entities.

Do I need to install ClickHouse?

No. Start with embedded DuckDB and Parquet. When you need more capacity, a migration wizard helps you move to ClickHouse. Both options use the same FQL and interface.

Can I use my own Sigma rules?

Yes. The import wizard converts supported Sigma rules to FQL and shows conversion coverage. Partially converted and unsupported rules remain disabled. Test the results against historical events before enabling them.

How do I control automated actions?

Add an approval step to a playbook, including approvals through Slack or Teams. Protected networks, action limits and an emergency stop help control device actions. Permissions and audit trails keep access accountable.

Where does my data go?

FrySIEM runs on your infrastructure, where events are stored and processed. You choose and configure external destinations for notifications, forwarding and integrations.

THE BIG PICTURE STARTS WITH ONE EVENT

Put your data
to work for security.

See how FrySIEM connects events, context and action.

Discover the platformCOLLECT. UNDERSTAND. RESPOND.

09 /GET IN TOUCH

Your ideas.
Our next conversation.

Have a question about FrySIEM, a feature in mind or feedback to share? This is where we’ll connect.

Write to us directly

Use the form or email info@frysec.com. We read every message.

Leave a message

Your message is sent by email to our team. We use your name, email address and message only to answer your request; the website stores nothing and no third-party services are involved. Privacy policy.

Enlarged FrySIEM interface screenshot

Captured from the FrySIEM demo environment.