Skip to content
BotConduct logo

BotConduct

Records the behavior of autonomous agents interacting with your systems from the receiving side, producing cryptographically signed evidence.

Developer toolsSecuritySecurityMonitoringCompliance
botconduct.org ↗Launched on Product Hunt · 2026-04-23
At a glance
Price
Price not read
Use
Use not read yet
Activity
Activity not read yet
Company
founding year not on record
Alternatives in Developer toolsby use, among tools still maintained
  • Spotlight by BackplanesMonitors AI agent activity, drafts security policies from observed behavior, and enforces controls on agent access to tools and external services.

    Emerging

    97 linking domains
  • Dominion ObservatoryMonitors MCP servers for security drift and behavioral anomalies, providing continuous trust scores and signed audit attestations.

    Emerging

    51 linking domains
  • Oconee RuntimeDetects, controls, and enforces policies on AI tool usage to prevent sensitive data exposure and risky actions.

    EmergingMaintained

    21 linking domains
  • VibeLegitScans deployed web applications for security vulnerabilities, exposed secrets, and compliance gaps specific to AI-generated code.

    EmergingActively maintained

  • FlowtriqDetects and automatically mitigates DDoS attacks in under one second using traffic analysis and BGP rules.

    EmergingActively maintained

    ≈ 202 visits/mo
  • Cloudback MCP ServerBacks up GitHub, GitLab, Azure DevOps, and Linear repositories with customer-managed encryption and fast recovery.

    Emerging

    ≈ 114 visits/mo

All Developer tools tools →

Questions this page answers
  • What is BotConduct?

    Records the behavior of autonomous agents interacting with your systems from the receiving side, producing cryptographically signed evidence.

  • What are alternatives to BotConduct?

    In Developer tools, by use: Spotlight by Backplanes, Dominion Observatory, Oconee Runtime, VibeLegit, Flowtriq, Cloudback MCP Server.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.