Compare the Top Agentic AI Platforms that integrate with OpenCode as of August 2026 - Page 2

This a list of Agentic AI platforms that integrate with OpenCode. Use the filters on the left to add additional filters for products that have integrations with OpenCode. View the products that work with OpenCode in the table below.

  • 1
    Spawn

    Spawn

    OpenRouter

    Spawn is an experimental OpenRouter tool for deploying AI coding agents on your own infrastructure with a single command. Pick an agent, choose a cloud, and Spawn provisions a virtual machine, installs the agent and its dependencies, authenticates to OpenRouter and the cloud using a CLI OAuth flow, configures endpoints and model routing, and then opens an SSH session so you can start working. Each agent-and-cloud combination is implemented as a self-contained script, avoiding Terraform and YAML while keeping deployment portable. Supported agents include Claude Code, OpenClaw, Codex CLI, OpenCode, Kilo Code, Hermes Agent, Junie, Pi, Cursor CLI, and T3 Code, making it easy to explore coding-agent workflows or switch between them with one command. Spawn supports cloud environments such as DigitalOcean, Sprite, Hetzner Cloud, AWS Lightsail, GCP Compute Engine, and Daytona, as well as a local machine or a throwaway local Docker sandbox.
  • 2
    Bevel

    Bevel

    Bevel

    Bevel is a vendor-agnostic, Git-backed control plane for enterprise AI agents, where an organization’s agents, context, skills, tools, permissions, and identities are defined as files the company owns in its own infrastructure and served to any agent runtime over MCP. Context is stored as typed knowledge nodes with provenance for every fact, including where it came from, who last changed it, and when it was verified, then compiled into a graph that can be traversed, updated, and used for dashboards. Skills are written as plain Markdown procedures that process owners can read, review in diffs, and port across runtimes. Tool manifests define available capabilities, while secrets stay in a vault and access rules determine which agents may read specific files or call endpoints. Each agent has its own identity, credentials, and scope so actions remain attributable.