Index / GoClaw · updated Oct 2, 2026

GoClaw

nextlevelbuilder/goclaw · healthy · rank 16 of 43 by stars

A full Go rewrite of OpenClaw aimed at production multi-tenant deployments, with PostgreSQL-backed tenant isolation and a 5-layer security model. It trades OpenClaw's personal-assistant simplicity for a single-binary gateway that orchestrates agent teams at scale.

#go#multi-tenant#agent-gateway#llm-providers#self-hosted
Compare vs OpenClaw
GitHub ↗

Facts

Repository

Contributors126
Open issues266
Last commitSep 30, 2026
Release cadence~0 days
Latest releasev3.14.0

Runtime

LanguageGo
Memory18 MB
Boot time35 ms
Deploymentself-hosted · cloud · desktop
Setup difficultyMedium
Plugin ecosystemEmerging

Posture

LicenseNOASSERTION
Local-firstYes
Cloud dependencyOptional
Multi-userYes
Privacy postureStrong

Community

Sentiment55% positive
Reddit mentions0
Web results10

Security breakdown

Composite 85 / 100 · how these are scored

Sandboxing8 / 10

higher is safer

API security8 / 10

higher is safer

Network isolation7 / 10

higher is safer

Telemetry safety7 / 10

higher is safer

Shell access risk5 / 10

higher is riskier

Model access

Read from the repository, not written by a model · 101 files examined

6 providers · runs locally · custom endpoint

Direct
AnthropicGoogleOpenAIQwenVertex AIZhipu
Local
Ollama
Compatible
OpenAI-compatible

Pinned models

MiniMax-M3MiniMax
glm-5.2Zhipu
kimi-k2.5Moonshot

MiniMax-M3 released 2026-05-31 — 4 months old (from the public model catalogue)

Pin last edited 6 days ago

Several defaults are pinned; the project picks one per provider rather than shipping a single default.

Evidence

Decision

Why choose GoClaw over OpenClaw?

Why choose this

  • Native multi-tenant isolation with PostgreSQL
  • Single static Go binary with low resource footprint
  • 5-layer security model and SSRF-safe media handling

Tradeoffs

  • Non-commercial license restricts business use
  • Smaller community and fewer third-party integrations
  • Heavier operational requirements (PostgreSQL, ffprobe)

Best fit

  • Teams deploying multi-tenant AI agent platforms
  • Operators wanting a single Go binary with PostgreSQL backing
  • Users needing 20+ LLM providers behind one gateway

Avoid if

  • You want a lightweight personal assistant setup
  • You need a permissive commercial license (CC BY-NC 4.0)
  • You prefer a large plugin ecosystem over a monolith
Good Confidence72%

Strong evidence from the README and detailed recent commits shows active, security-conscious development, but there is zero Reddit presence and web sentiment is indirect, so community reception is uncertain.

AI layer reviewed Sep 21, 2026 · how this is written

Star activity

3,638 stars today

Overview

GoClaw is a ground-up Go rewrite of OpenClaw positioned as a production-grade, multi-tenant AI agent gateway. It ships as a single binary backed by PostgreSQL 18, supports 20+ LLM providers and 7 messaging channels, and exposes a WebSocket API with OpenTelemetry observability. Its headline differentiators are tenant-level isolation, a 5-layer security model, and native Go concurrency for orchestrating teams of agents.

Recent commit activity shows a mature, security-focused engineering culture: media payloads are priced against agent token budgets using ffprobe/pdfinfo measurements rather than byte counts, SSRF-safe HTTP clients guard remote fetches, and team-task delegation has carefully audited authorization and notification routing with regression tests. The dashboard supports human-in-the-loop operations like cancelling and retrying stuck team tasks.

Compared to OpenClaw, GoClaw targets operators and teams rather than individual users: it requires PostgreSQL and optional runtime tools (ffprobe, pdfinfo), and is licensed CC BY-NC 4.0, which blocks commercial use. In exchange it offers stronger multi-tenant isolation, a smaller runtime footprint, and a gateway architecture suited to deploying agent teams at scale.

Nominate a clone

Add a new Claw

Paste a GitHub repository and tell us why it belongs on the tracker.

Opens a prefilled issue on GitHub — every nomination is public. Comfortable with a PR? Adding the repo to projects.json is faster.