LogSeam
Cover 01 / 23
§ The agentic SOC platform

The agentic
SOCSOC platform.

An open data lake, every SOC workflow, and the AI agents to run them.

§ The problem

Security can't afford to choose.

Every platform forces a trade-off — visibility vs. budget, retention vs. speed, AI vs. cost. SOC teams stitch six tools that don't talk, pay a per-GB ingest tax, and drop logs on the floor to keep the bill down.

SIEMSOARUEBA Detection engineHunting tool TicketingThreat intel
$2.40/GB
Legacy SIEM ingest tax
Penalty per GB ingested — encourages dropping data.
~30d
Hot retention typical
Anything older lives in cold tiers, queried slowly and at a fee.
6+
Tools to investigate one alert
SIEM → EDR → ticketing → IdP → threat intel → docs.
§ The promise

Run the SOC.
Not the tools.

One platform — replacing SIEM, SOAR, UEBA, and the detection engine — on an open lake you already own, driven by AI agents your analysts govern.

01 / OPEN & COMPOSABLE
Open and composable.
Your data is your data. Put it where you want, in open formats, scaled to your size. No more one-size-fits-all.
02 / THE WORKFLOWS
Every SOC workflow.
Triage, investigate, hunt, detect, respond, attest. Modeled end-to-end. Not a chat bolted on. Not a SOAR you wire up. The whole routine.
03 / AGENTS + ANALYSTS
AI agents and analysts as a team.
A specialized agent for each workflow and function. Reasoning, validating, and governed by humans. Every element of the system composable and accessible.
§ The architecture

One agentic fabric.

Three planes — Interface, Platform, Lake — woven together. Agents move freely across all of them.

The Interface Assistant Explorer Alerts Incidents Dashboard Reports MCP Triage Investigate Hunt Detect Respond Intelligence The Agents The Platform The Lake Logs · Events Files · Objects Indexed Data Integrations Enrichments
§ What you can ask

Humans and agents,
working as one.

Ask the question once. LogSeam turns it into an evidence-backed assessment, recommended actions, and ready-to-use outputs, so analysts move from investigation to decision without stitching tools together.

Critical
You asked "Assess the Okta tenant for authentication threats over the last 60 days."

Okta authentication threat assessment

884,349 failed auth attempts on three high-value targets from Tor and proxy infrastructure. Organized and persistent — not opportunistic.

TOP TARGETS · 60d
d.park
346,644
j.chen
105,899
s.williams
49,589
4 actions readyOpen report →
Info
You asked "Audit our MITRE ATT&CK coverage and draft detections for the gaps."

ATT&CK coverage + 8 new rules

71% tactic coverage. Strong on Initial Access; thin on Defense Evasion and C2. Eight new Sigma rules drafted with backtests.

TACTIC COVERAGE
Initial Access100%
Execution88%
Persistence62%
Defense Evasion31%
Command & Control44%
8 rules · backtested 30dReview & deploy →
High
You asked "Brief me on APT29 and tell me where we're exposed."

APT29 — exposure & coverage gaps

12 of 18 TTPs covered. Six gaps in OAuth abuse and cloud lateral movement — both observed in recent campaigns. Two suspect matches in your data.

COVERAGE BY TECHNIQUE
T1566.002Spear-phishing link
T1078.004Cloud accounts
T1528App access token theft
T1098.005Device registration
T1550.001Pass-the-token
6 gaps · 2 active matchesOpen hunt →
§ The Lake

The open security data lake.

Every security event, from every source, landed as columnar Apache Parquet on object storage — your bucket or ours, with unlimited retention and no proprietary lock-in. Read by any SQL tool.

YOUR BUCKET

Use your S3

  • Point at your S3-compatible bucket
  • Your IAM, your encryption keys
  • Data never leaves your account
  • Zero migration required
  • Full ownership and control
LOGSEAM BUCKET

Managed by us

  • Dedicated managed bucket
  • Global replication built in
  • 11+ nines durability
  • Streamlined onboarding
  • Optimal performance guaranteed
WE FETCH

No agent required

  • Collect from any location
  • Normalize on ingest
  • Secure API-based retrieval
  • Scheduled or real-time pulls
  • No agent installation needed
§ What we do with your data

From logs to a queryable, catalogued lake.

Ingest is just the first step. Every event is compressed, optimized, indexed, catalogued, and continuously understood — so by the time you query, the lake already knows what's in it.

01 · COMPRESS

Parquet

Raw JSON normalized and packed into columnar Apache Parquet — 10–20× smaller, fast to scan, cheap to keep forever.

02 · ENHANCE

Indexes

Bloom filters, page indexes, statistics, dictionary encoding — queries skip everything they don't need.

03 · STORE

Tiered

Partitioned, tiered, and compacted for your access pattern. Hot is fast, cold is cheap, no re-architecting.

04 · CATALOG

Discoverable

Every dataset registers in an open catalog with schema, partition spec, and time-travel snapshots.

05 · UNDERSTAND

Rosetta Stone

Continuously studies the lake — what each column means, how values relate across sources. Schemas drift; the catalog keeps up.

§ Sources

Every event. Every source. One lake.

Whether your data starts in a SIEM, an EDR, a SaaS, or a custom app, it ends up here — landed as open Parquet, read by any tool that speaks SQL.

SIEM

Splunk · Sentinel · Elastic

Export colder data into LogSeam for long-term retention and lightning-fast search. Drop-in S3 destinations preserve your original SIEM schema as open Parquet.

SECURITY PRODUCTS

EDR · Firewall · IAM · CSPM

Centralize telemetry from every security tool. Open formats ensure permanent access without vendor lock-in. Unified retention with intelligent tiering and enterprise RBAC.

LOG PIPELINES

Cribl · Monad · Vector

Add LogSeam as your durable, cost-efficient destination. Simple S3-compatible target config with high-throughput, low-latency ingestion.

DIRECT

Vector · Fluent Bit · Logstash · Custom JSON

Single S3-compatible endpoint for all environments. Automatic schema-on-read and global replication. Any source that outputs JSON, in minutes not months.

§ The Platform

The engine that runs the SOC.

One runtime replaces SIEM, SOAR, UEBA, and the detection engine — with economics that don't punish you for ingesting data.

ONE ENGINE

Replaces SIEM, SOAR, UEBA, detection engine.

Detection, response, hunt, and intelligence on one runtime. Stop paying four vendors and stitching their APIs to get one outcome.

NODE PRICING

Pay for the nodes you run. Not per event.

Predictable per-compute-node pricing. No per-GB ingest tax, no per-query meter, no surprise bill when alert volume spikes.

OPEN STORAGE

Your bucket. Open Parquet. No retention tax.

Apache Parquet on object storage you already own. No per-GB ingest fees, no cold-tier surprises, no egress charge when you leave.

COMPOSABLE

Workflows · rules · patterns · agents — same primitive.

A workflow can call a workflow. An agent can call a workflow. A pattern can feed a rule. One runtime, one audit trail, infinite combinations.

§ 01 · Scale

Per-query compute. Two nodes or two hundred.

A small query gets a small footprint. A petabyte hunt gets a fleet. LogSeam adapts the compute envelope to the request — automatically, per query — and accelerates everything with distributed SQL, smart caching, and entity tables.

Small query Petabyte hunt SELECT … 1d SELECT … 90d 2 nodes · 200ms 200 nodes · sub-second Scale up Scale down

Per-query elastic compute means the engine right-sizes itself to the work. One analyst's quick search runs cheap. The same lake hosting a petabyte hunt runs the same query plan across hundreds of nodes — automatically, with no operator intervention.

Underneath: an advanced distributed SQL planner, smart result caching, and pre-computed entity tables for users, hosts, IPs, and sessions that fold repeated joins into sub-second answers.

  • per-query node allocation — 2 to 200+, automatic
  • distributed SQL with cost-based planning
  • result and intermediate-stage caching
  • entity tables — users, hosts, IPs, sessions
  • sub-second median search across billions of rows
§ 02 · Workflow

Composable workflows. Triggered by anything.

A workflow is how repeatable work moves through the platform. Anything can start one — an event, a schedule, an alert, a rule match, an agent. Every workflow scales across the cluster and composes freely with every other.

Workflow run
Detect lateral movement
STEP 01 fetch failed auths · last 24h QUERY
STEP 02 join entity tables · IOC lookup ENRICH
STEP 03 hunt — score behavioral anomalies ● AGENT
STEP 04 if score ≥ 0.85 GATE
STEP 05 respond — propose containment ● AGENT
STEP 06 open incident · page on-call ACTION

Workflows live as code, run distributed across the cluster, and chain freely. A workflow can spawn other workflows. An agent can launch a workflow. A workflow can call an agent. Same engine, same audit trail.

Anything repeatable belongs in a workflow — scheduled threat assessments, daily rule reviews, threat-model application against new alerts, intelligence refreshes, evidence packaging at incident close.

  • triggers: event · schedule · alert/incident · rule · agent
  • composable — workflows call workflows or agents
  • distributed execution across the cluster
  • full audit trail for every step
  • versioned in code — diffable, reviewable, reusable
§ 03 · Rules & Patterns

Rules for what's known. Patterns for what isn't.

Detection-as-code in two complementary forms. Rules cover known TTPs in a single Sigma / SQL match. Patterns chain SQL and analytics steps to model behavior, statistics, and outliers across the entire lake.

RULE · SINGLE MATCH

Sigma, backed by SQL.

Author in Sigma — the open, vendor-agnostic standard — or write SQL directly. Every rule shows a live SQL preview of exactly what will execute. Single-shot match, MITRE-classified, instantly testable.

# sigma rule — admin login from new country
title: Admin Auth from Unseen Country
logsource:
  product: okta
detection:
  selection:
    eventType: user.session.start
    user.role: admin
  filter:
    geo.country: in known_admin_countries
  condition: selection and not filter
  • SIGMA in, SQL out — open standard
  • live SQL preview in the editor
  • quality gates: precision, FP rate, latency
  • MITRE ATT&CK classification per rule
PATTERN · MULTI-STEP ANALYTICS

Composed analytics. Behavior, baselines, outliers.

Patterns chain multiple SQL or analytics steps into one detection. Use them for behavioral sequences, statistical baselines, user/host profiling, or outlier hunts across petabyte data.

01baseline auth volume per user · 30d
02profile normal source ASNs & geos per user
03score last-24h auths against baseline (z-score)
04emit top-N outliers · join entity table for context
  • chain SQL + analytics steps · share state
  • behavioral sequences over time
  • statistical baselines · z-scores · percentiles
  • user / host / session profiling via entity tables
  • outlier hunts across the full lake
§ The AI · roster

Specialized agents. At swarm scale.

A growing fleet of purpose-built agents mapped to how SOCs actually work — analyst-grade specialists who answer the questions, operational agents that close the loop, and platform agents that run the room. The harness is open, so you can add your own.

— The analysts —
  • Triage
  • Investigations
  • Case Briefing
  • Threat Hunting
  • Detection Engineer
  • Forensics
  • Malware Analyst
  • Network Analyst
  • Data Analyst
— The operations —
  • Correlation
  • Rule Generation
  • MITRE ATT&CK
  • IOC Worker
  • Threat Intel
  • Vulnerability
  • Incident Response
  • Compliance
— The platform —
  • Canvas
  • SOC Platform
  • Dashboard
  • Composer
  • Reports
  • Librarian
  • Integrations
  • Data Advisor
  • Agent Creation
§ Context graph

Agents reason on a graph, not a log line.

Every event we ingest is linked to the entities it touches — users, hosts, identities, processes, files, IPs, alerts, tickets. When an agent asks "who else touched this account?", the answer is one hop away — not a half-hour pivot through a dozen tools.

authenticated accessed triggered on linked Alert INC-4471 User d.park Host web-01 Identity Okta File config.yaml IP 1.2.3.4 Ticket JIRA-882
01

Built at ingest.

Every record is parsed for the entities it references and stitched into the graph — no separate ETL job, no nightly rebuild.

02

Queried by agents.

Agents traverse the graph instead of fanning out raw SQL. "Show me everything that touched this account" becomes one query.

03

Grounded in your data.

Identities from your IdP. Assets from your CMDB. Tickets from your ITSM. The graph reflects your environment — not a generic schema we picked.

04

Open and queryable.

Exposed via MCP, SQL, and the API — for your agents, your analysts, and any tool you want to point at it. No black box.

§ Agent memory

Recall, not re-query.

Two layers. Session memory captures the raw work — queries, findings, reasoning. The Library captures curated knowledge — who you are, what you own, who's after you. Investigations compound; compute spend doesn't.

agent memory · session recall
# Tuesday — Hunt agent investigates 10.0.4.22
> hunt: lateral movement from 10.0.4.22
  847 results stored → memory: inv-4a7f

# Thursday — Investigate agent picks it up
> recall: inv-4a7f — correlate with new C2 indicators
  12 matches found across stored results
  no re-query needed — 0 additional compute
library · curated knowledge
★ Company information
org chart · critical assets · acceptable-use policy
★ Threat actor profiles
APT29 · FIN7 · Lazarus — TTPs, IOCs, write-ups
★ Environment knowledge
network topology · IAM model · tiering · golden paths
★ Risk register
crown jewels · exposure · compensating controls
Pods
Isolated agent runtime
Each agent runs in its own pod — state, memory, scope. Spread thousands across the cluster.
Swarms
Coordinated work
Need agents that coordinate? Compose them into a swarm working a single job together.
BYOM
Any model, your choice
Anthropic · OpenAI · Bedrock · Gemini · MiniMax · Kimi · self-hosted. Swap without rewriting an agent.
§ Governance harness

Every function is an action. Every action is accounted.

There is no "agent did something" black box. Every tool call an agent makes is a typed action with a caller, a scope, a policy, and an audit record. Sensitive actions wait for a human.

Action lifecycle AGENT respond.containment caller · d.park POLICY · SCOPE classify action auto · or · approve AUTO execute HUMAN approve analyst · oncall AUDIT LOG action · result signed · timestamped policy classifies · human gates the rest · everything is recorded

Every tool an agent invokes — query, enrich, ticket, block, isolate, page — is a typed action. Actions carry the caller's identity, the agent that emitted them, scope, inputs, and a policy classification.

Read-only actions auto-execute. Anything destructive — containment, deletion, deployment, ticket creation — pauses for a human approval from the analyst or on-call engineer you've designated. Nothing happens behind your back.

  • typed actions — no free-form side effects
  • per-action policy: auto · approve · forbid
  • RBAC + scope inherited from caller
  • signed, timestamped audit log — every step replayable
  • bring-your-own-model — Claude, GPT, Gemini, self-hosted
§ The Interface

Your team's surface. Or no surface at all.

Six interfaces for the work — or skip them entirely and drive everything from your own tooling via MCP. Same lake. Same agents. Same workflows. The Interface is one front-end among many.

01 / ASSISTANT

Natural-language entry point

Question in, answer out — with the work shown. The fastest way for an analyst to ask anything across the lake. The Assistant searches, runs agents, produces visualizations, and explains its reasoning.

02 / SPACES

Collaborative investigation canvas

Infinite zoomable workspace. 16 widget types — search, tables, timelines, ATT&CK matrix, entity cards, enrichment. Templates for Phishing, Lateral Movement, Malware. Live cursors and AI copilot on the canvas.

03 / ALERTS

Live queue, AI-triaged

Every alert pre-assessed by the Triage agent with verdict, IOCs, and source logs. Seconds for triage instead of minutes. Every alert reviewed end-to-end before it lands on a human.

04 / INCIDENTS

NIST IR case management

Five-phase IR with timeline, evidence management, and the IR agent in every phase. 80% of the report already written when the case closes. The whole team works the incident together.

05 / DASHBOARDS

Live SOC ops

40+ widget types, custom SQL widgets, per-board AI chat — "why did volume spike?" Real-time metric cards, severity, alert timelines, technique rankings. Multiple boards per team, auto-refresh.

06 / REPORTS & MCP

AI-generated · or headless

Executive (30s), Compliance (SOC 2 / ISO 27001 / HIPAA in <2min), Incident, Technical — export to PDF/HTML. Or skip the UI entirely and drive every workflow from your own tooling via MCP.

§ Outcomes

Humans and agents, working as one.

Hours → Min
Mean time to investigate
From hours of analyst pivoting to minutes of agent review.
All
Alerts auto-triaged
Every alert reviewed by agents with a full evidence trail — escalated to analysts only when humans are needed.
~.25¢/GB
Lower SOC operating cost
You hold the speed dial — from turtle (cheap, deep) to rabbit (instant, hot).
FOR ANALYSTS

Less toil, more judgment

Agents handle the rote — triage, enrichment, correlation. Analysts work the cases that need a human, with full evidence and the work shown.

FOR ENGINEERS

Detection-as-code, one runtime

Rules, patterns, workflows, agents — all composable, all versioned, all in one engine. Build once, reuse everywhere.

FOR LEADERS

Predictable bill, complete coverage

Per-node pricing, pass-through compute/storage/AI at cost. Stop dropping data to manage budget.

§ Versus traditional SIEM

What you're really choosing.

Strip away the marketing. The engine choice tells you what each platform will be good at.

DimensionTraditional SIEMLogSeam
PricingPer-GB ingest taxPer-node. Predictable.
Storage formatProprietary index, lockedOpen Apache Parquet
Storage locationVendor cloudYour bucket — or ours, at cost
RetentionHot/cold tiers, fees per tierUnlimited — one tier, one price
ComputeFixed — pay for idlePer-query elastic, scales to zero
WorkflowsSIEM + SOAR + UEBA bolt-onsOne runtime, end-to-end
DetectionSingle-shot rulesSigma rules + multi-step patterns
AIChat bolted onAgents native to every workflow
MemoryNo — every question re-queriesSession + Library — investigations compound
GovernanceFree-form integrationsTyped actions, audit, human gates
EgressPay to leaveNo exit fee — it's your bucket
§ Pricing

Transparent pricing. Nothing hidden.

Two components. One varies with what you actually run; the other is a flat per-node line for software and support. Compute, storage, and AI are pass-through — at cost, no margin.

01 · PASS-THROUGH

Compute · Storage · AI

EC2-type compute, S3-class storage, and the model providers your agents call — Anthropic, OpenAI, Bedrock, Gemini, MiniMax, Kimi, or self-hosted. Pay your providers directly at your contract rate, or we pass the invoice through at cost — no margin.

02 · LOGSEAM PER-NODE

Per-node software & support

One flat rate per node for the lake, the agents, the orchestrator, the UI, and your support tier. Static (always-on) and dynamic (auto-scaled per query) nodes priced separately. A node is any EC2-type compute node, any size.

Node type
Core Support · 8×5
Critical Support · 24×7
Always on
$250/ node / mo
$500/ node / mo
Dynamic node
$175/ node / mo
$350/ node / mo
§ Node sizing

How many nodes do we need?

Sizing depends on the roles your deployment needs: log processing, search, orchestration, and MCP access. Each role can scale independently based on ingest volume, analyst concurrency, workflow load, integration patterns, and the CPU/memory shape of each node.

LOG PROCESSING

Ingest tier

Ingest, parse, normalize, enrich, and write telemetry into the lake. This tier scales with daily volume and transformation cost.

  • scales with daily ingest volume
  • parse · normalize · enrich
  • writes columnar Parquet
SEARCH

Query tier

Interactive queries, hunts, dashboards, and rule execution. This tier scales with analyst concurrency, query shape, and retention window.

  • scales with analyst concurrency
  • hunts · dashboards · rules
  • per-query elastic compute
MASTER

Control plane

Control-plane coordination for schedules, workflow state, cluster membership, and query orchestration. Usually small, but critical.

  • schedules · workflow state
  • cluster membership
  • small footprint · always on
MCP

Agent & API tier

API and tool-facing nodes for agents, integrations, and MCP clients. This tier scales with automation volume and external access patterns.

  • scales with automation volume
  • agents · integrations
  • MCP clients · external API

→ Each role scales independently · we'll size the node mix to your actual ingest profile and query pattern

§ Deployment

Deploy your way.

LogSeam Managed, your cloud, or on-premises. Every deployment is single-tenant — your own dedicated infrastructure, never shared with another customer.

LOGSEAM MANAGED

Fully managed. We handle everything.

We run the control plane, the compute, and the lake. You bring data and users. Multi-region available with data residency by region. Fastest time to value.

  • dedicated single-tenant cluster — never shared
  • 24/7 monitoring and support
  • multi-region · automatic scaling
YOUR CLOUD

BYOC — your AWS / GCP / Azure / OCI

LogSeam runs entirely inside your own account — fully isolated. Your IAM, your encryption keys, your network policies. We manage the software; you own the perimeter and the spend.

  • AWS, GCP, Azure, OCI support
  • Kubernetes or specific instances
  • your account, your storage, your keys
ON-PREMISES

Air-gapped or sovereign

Your hardware, your data center, your air-gap. Self-hosted models supported, no outbound network requirement. Same platform, same agents — custom-scoped pricing.

  • fully air-gappable
  • self-hosted models
  • LogSeam engineering collaboration

Run the SOC.
Not the tools.

A demo on your data — with our agents working a real alert end-to-end.

← → arrows · 1–9 jump · home/end first/last