CISO Tribune

Vendor comparison · 2 companies

Archipelo vs Daylight

Archipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage. Daylight sells managed agentic security services that combine an AI-native security platform with human expertise to detect, investigate, and respond to cyber threats. CISO Tribune files both under AI model and agent security. This page sets the two records side by side: what each sells, where it is based, who owns and funds it, the customers it names and its recent news, each fact numbered to its source.

Change the companies

Up to four companies side by side.

  • Archipelo
  • Daylight
Archipelo vs Daylight: Products, Customers and Funding Compared
ArchipeloArchipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage.archipelo.comDaylightDaylight sells managed agentic security services that combine an AI-native security platform with human expertise to detect, investigate, and respond to cyber threats.daylight.ai
What it sells
  • Salmon[1][2][3][4][5]Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage.
  • MDR[1][4][5][6][8]A managed detection and response service in which Daylight owns the detection-to-response cycle from alert ingestion to resolution.
  • Phishing[1][4]Handles user-reported emails and security alerts around the clock as part of MDR.
  • DLP[1][4][5]Adds an investigation and response layer to DLP signals.
  • Security Data Lake[1]A security data lake meant to replace a SIEM.
Categories
Headquarters
Not stated on its pagesNot stated on its pages
Founded
Not stated on its pagesNot stated on its pages
Ownership and funding
Not stated on its pagesPrivately held
Named customers
Not stated on its pagesNot stated on its pages
Recent news
Not stated on its pagesNot stated on its pages
G2 and Gartner Peer Insights
  • G2: Not stated on its pages
  • Gartner Peer Insights: Not stated on its pages
  • G2: Not stated on its pages
  • Gartner Peer Insights: Not stated on its pages
Who it fits
From its own pages, Archipelo's Salmon addresses software in which autonomous agents, tools, runtimes, and controllers perform consequential actions. Archipelo describes incident investigation teams as needing to work backward from a consequential state change toward the execution associated with it. Archipelo names systems that investigate, evaluate, govern, and depend upon execution as the systems for which verifiable execution history matters.Not written yet
Last verified
September 30, 2026November 10, 2026

Where they overlap

  • Archipelo and Daylight are both filed under AI model and agent security.

Where they differ, field by field

  • Archipelo's primary category is Software supply chain security; Daylight's is MDR and managed SOC.
  • Archipelo is also filed under Insider risk management. Daylight is also filed under Security data lakes and pipelines and Data loss prevention.
  • Archipelo lists Salmon. Daylight lists MDR, Phishing, DLP and Security Data Lake.
  • Daylight is privately held.

What it sells: Archipelo

What Salmon does[1][2][3][4][5]
Salmon is Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage. Execution is represented as a cryptographically signed event with explicit context. Salmon captures execution as it occurs upstream within supported environments.

What it sells: Daylight

What MDR does[1][4][5][6][8]
Daylight owns the full detection-to-response cycle from alert ingestion to resolution, with contractual accountability. Investigations begin with identity, cloud, endpoint, SaaS, and historical context. For every confirmed case, Daylight drives remediation to completion, such as revoking sessions, resetting credentials, and blocking IPs. Daylight's MDR includes AI Security, phishing, and DLP.
What Phishing does[1][4]
Daylight handles user-reported emails and security alerts around the clock as part of MDR. Each reported email and security alert is investigated to a verdict and then remediated across every affected mailbox.
What DLP does[1][4][5]
Daylight adds the investigation and response layer that turns DLP signals into closed cases. Daylight drives real data theft to resolution and explains benign activity instead of only flagging it. DLP is included in Daylight's MDR.
What Security Data Lake does[1]
Daylight keeps 90 days of telemetry hot and immediately searchable, with older data archived at lower cost. Customers search the data themselves using plain English or KQL. Daylight handles the infrastructure, storage, and data operations.

Questions about Archipelo and Daylight

What do Archipelo and Daylight sell?
Archipelo sells Salmon. Daylight sells MDR, Phishing, DLP and Security Data Lake.
Are Archipelo and Daylight in the same category?
They share AI model and agent security. Archipelo's primary category is Software supply chain security and Daylight's is MDR and managed SOC.
Who owns Archipelo and Daylight?
Daylight is privately held.
Who are Archipelo and Daylight sold to?
From its own pages, Archipelo's Salmon addresses software in which autonomous agents, tools, runtimes, and controllers perform consequential actions.

About Archipelo

Archipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage. Archipelo builds Salmon for autonomous multi-actor software systems. Archipelo, Inc. is the company developing and stewarding Salmon.[1][3][4][5]

Archipelo states that autonomous agents, tools, runtimes, and controllers increasingly perform consequential actions themselves. Archipelo states that the resulting state alone cannot show which execution occurred, in what order, or how each state transition derived from the ones before it. Archipelo develops infrastructure that makes autonomous multi-actor software execution independently verifiable. Archipelo states that safe and reliable agents need verifiable evidence of their execution history.[4][5]

Archipelo points to Git as showing the value of persistent, linked source code history. Archipelo says Execution Verification Infrastructure addresses a different problem, which is establishing a verifiable record of state transitions and the resulting state.

Archipelo describes execution as represented by a cryptographically signed event with explicit context. Archipelo states that Salmon captures execution as it occurs upstream within supported environments, not downstream after the event has already taken place. Archipelo states that Salmon does not visually or structurally manufacture execution continuity when execution continuity has not been established.

Archipelo states that agent generated changes can involve delegated execution, tools, subprocesses and multiple state transitions. Archipelo states that execution history provides a durable record of supported execution relationships to verify outcomes. Archipelo states that during incident investigation, teams need to work backward from a consequential state change toward the execution associated with it, to determine what caused the outcome.

One principle is that downstream systems should not be forced to establish execution history solely through retrospective inference where it can be captured during supported execution. Archipelo states that what an actor was permitted or instructed to do is distinct from what it actually executed. Archipelo states that machine-speed software systems require execution evidence that other software systems can consume and verify. Archipelo describes identity, policy, observability, security, engineering, and governance systems as solving adjacent problems.[5]

Archipelo describes itself as a deep tech company building foundational infrastructure for verifiable autonomous systems.[1][3][4][5]

Archipelo on the record

Sources

Archipelo full record

  1. [1]archipelo.comArchipelo · archipelo.com · undated page, accessed September 30, 2026 · Tier A
  2. [2]Archipelo - Making Autonomous Software Execution VerifiableArchipelo · undated page, accessed October 30, 2026 · Tier A
  3. [3]Terms of Service — SalmonArchipelo, Inc. · published September 20, 2026 · Tier A
  4. [4]Archipelo - This page has been retiredArchipelo · undated page, accessed October 30, 2026 · Tier A
  5. [5]About — SalmonArchipelo · undated page, accessed November 10, 2026 · Tier A

Daylight full record

  1. [1]daylight.aiDaylight · daylight.ai · undated page, accessed November 10, 2026 · Tier A
  2. [2]Daylight vs reliaquestDaylight · daylight.ai · published June 2, 2026 · Tier A
  3. [3]Managed Security Services | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  4. [4]Managed Agentic Security ServicesDaylight · undated page, accessed November 11, 2026 · Tier A
  5. [5]Managed Detection and Response (MDR) Services | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  6. [6]AI Threat Detection & Security Services | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  7. [7]Managed Threat Hunting Services | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  8. [8]Managed Security Data Lake | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  9. [9]Security Integrations | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  10. [10]How Antidote Health Secures a Fast-Changing StackDaylight · undated page, accessed November 11, 2026 · Tier A
  11. [11]How LVT Scaled Security Operations with DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  12. [12]How Lusha Scaled Security Without Building a SOCDaylight · undated page, accessed November 11, 2026 · Tier A
  13. [13]Our Story | DaylightDaylight · undated page, accessed November 11, 2026 · Tier A
  14. [14]How The Motley Fool Reached Zero Backlog with DaylightDaylight · undated page, accessed November 11, 2026 · Tier A

Spot a factual error? Request a correction.