CISO Tribune

Vendor comparison · 2 companies

Archipelo vs Bay

Archipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage. Bay is an AI agent security platform that gives enterprises visibility into every agent across devices, browsers and cloud workloads, and control over what those agents do in real time. 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
  • Bay
Archipelo vs Bay: Products, Customers and Funding Compared
ArchipeloArchipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage.archipelo.comBayBay is an AI agent security platform that gives enterprises visibility into every agent across devices, browsers and cloud workloads, and control over what those agents do in real time.bay.io
What it sells
  • Salmon[1][2][3][4][5]Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage.
  • Bay[1][2][3][4][5][6][7][8][9]Bay is an AI agent security platform covering agents on devices, in browsers and in cloud workloads. Bay returns allow, ask, steer or block decisions on agent actions at runtime.
  • Lighthouse[6]Lighthouse is Bay's embedded agentic system that drafts policy from an organization's own agent activity.
  • Wave[3]Wave is the ephemeral binary Bay uses to deploy through an existing MDM or EDR.
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 pagesNot stated on its pages
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 5, 2026

Where they overlap

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

Where they differ, field by field

  • Archipelo's primary category is Software supply chain security; Bay's is AI model and agent security.
  • Archipelo is also filed under Insider risk management. Bay is also filed under Endpoint management and application control and Workforce AI usage security.
  • Archipelo lists Salmon. Bay lists Bay, Lighthouse and Wave.

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: Bay

What Bay does[1][2][3][4][5][6][7][8][9]
Bay maps every agent, MCP server, extension, model and skill on devices on its first scan. Bay builds a contextual entity graph of the users, MCP servers, SaaS apps and access connected to each agent. Bay deploys with one script through an existing MDM and does not require a proxy. Bay keeps full transcripts of prompts, actions and MCP calls.
What Lighthouse does[6]
Lighthouse drafts policy from an organization's own agent activity. Users answer 7 questions about risk appetite, and Lighthouse recommends a setting for each question and builds the policy. Bay replays 30 days of agent history to show what a policy would do before enforcement.
What Wave does[3]
Bay is agentless and deploys through an existing MDM or EDR using Wave, an ephemeral binary. There is no persistent agent to maintain and no proxy in the path.

Questions about Archipelo and Bay

What do Archipelo and Bay sell?
Archipelo sells Salmon. Bay sells Bay, Lighthouse and Wave.
Are Archipelo and Bay in the same category?
They share AI model and agent security. Archipelo's primary category is Software supply chain security and Bay's is AI model and agent security.
Who are Archipelo and Bay 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

Bay full record

  1. [1]bay.ioBay · bay.io · undated page, accessed November 5, 2026 · Tier A
  2. [2]Security Researcher — Careers at BayBay · undated page, accessed November 10, 2026 · Tier A
  3. [3]AI Endpoint Security — BayBay · undated page, accessed November 10, 2026 · Tier A
  4. [4]About — BayBay · undated page, accessed November 10, 2026 · Tier A
  5. [5]Cloud Workspaces — BayBay · undated page, accessed November 10, 2026 · Tier A
  6. [6]Platform — BayBay · undated page, accessed November 10, 2026 · Tier A
  7. [7]Browser — BayBay · undated page, accessed November 10, 2026 · Tier A
  8. [8]AI Governance & Compliance — BayBay · undated page, accessed November 10, 2026 · Tier A
  9. [9]AI Security Posture — BayBay · undated page, accessed November 10, 2026 · Tier A

Spot a factual error? Request a correction.