runelay

runelayvsComposioNov 2026

The open-source, self-hosted Composio alternative

Keep OAuth tokens on your own server, pay nothing per seat and share memory across every agent.

$0per seat, MIT
1container or desktop app
AES-256tokens on your server
1,045tokens at connect

runelay vs Composio at a glance

runelayComposio
Runs onYour computer or serverComposio’s cloud
Self-hostingFree, one containerEnterprise arrangement
PriceFree, MIT$18 per seat
Where tokens liveYour server, your keyComposio’s cloud
Open source✓—
Memory across agents✓—
Skills served to agents✓—
Imports your agent setup✓—
Integrations~25 curated + any MCP or OpenAPILarge managed catalog

runelay fits when

  • Your own agents (Claude Code, Codex, Cursor, Grok) should share accounts, skills and memory.
  • Tokens and the audit log must stay on infrastructure you control.
  • You want no seats to count and no call limits.
  • Context is tight: 1,045 tokens at connect for 125 tools.

Composio fits when

  • You want a large catalog of integrations managed for you.
  • You are building a product that authenticates your own end users.
  • You do not want to run anything at all.

Switching takes a few minutes

  1. Install runelay

    On your computer or on any server with Docker.

    $curl -fsSL runelay.com/install | sh
  2. Import what your agents already have

    Accounts they were logged into arrive connected, the rest go into one reconnect queue.

    $runelay migrate
  3. Keep a Composio endpoint during the move

    runelay accepts any remote MCP URL, so a Composio endpoint can sit behind it until you replace it.

Questions

Is runelay really free?

Yes. It is MIT licensed, self-hosted and has no paid tier, seat price or call limit.

Can I self-host Composio instead?

Self-hosting Composio is an Enterprise arrangement. runelay is built to be self-hosted from day one: one desktop app or one Docker container with SQLite.

Does runelay have as many integrations?

No. It ships around 25 curated MCP servers with one-click OAuth, and adds anything else through a remote MCP, a local MCP or an OpenAPI spec.

Where are my OAuth tokens stored?

On your server only, encrypted with AES-256-GCM using your RUNELAY_SECRET.