Index / GoClaw · updated Oct 24, 2026

GoClaw

nextlevelbuilder/goclaw · healthy · rank 20 of 50 by stars

A production-grade Go rewrite of OpenClaw focused on multi-tenant isolation and 5-layer security for deploying agent teams at scale. Single-binary deployment with 20+ LLM providers and PostgreSQL-backed tenancy makes it feel more like an enterprise gateway than a personal assistant.

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

Facts

Repository

Contributors129
Open issues277
Last commitOct 22, 2026
Release cadence~2 days
Latest releasev3.14.0

Runtime

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

Posture

LicenseNOASSERTION
Local-firstNo
Cloud dependencyOptional
Multi-userYes
Privacy postureStrong

Community

Sentiment55% positive
Reddit mentions0
Web results10

Security breakdown

Composite 82 / 100 · how these are scored

Sandboxing7 / 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 — 5 months old (from the public model catalogue)

Pin last edited 29 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 row scoping
  • Go single binary with lower memory footprint and fast boot
  • Explicit 5-layer security model and production-tested gateway design

Tradeoffs

  • Non-commercial license restricts business use
  • Smaller community and fewer channel/skill integrations
  • Heavier infrastructure requirements (PostgreSQL) for simple use cases

Best fit

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

Avoid if

  • You need a permissive open-source license (CC BY-NC)
  • You want a lightweight single-user local assistant
  • You want to avoid running PostgreSQL
Good Confidence72%

Strong evidence from README, releases, and active commit history confirms an actively maintained, security-focused Go rewrite. However, zero Reddit mentions and web results that mostly discuss OpenClaw rather than GoClaw itself mean community sentiment is largely inferred.

AI layer reviewed Oct 5, 2026 · how this is written

Star activity

3,666 stars today

Overview

GoClaw is a ground-up Go reimplementation of OpenClaw positioned as a multi-tenant AI agent platform rather than a single-user personal assistant. It ships as a single binary backed by PostgreSQL 18, supports 20+ LLM providers and 7 messaging channels, and emphasizes a 5-layer security model with tenant isolation, making it suitable for hosting agent teams for multiple users or organizations.

Architecturally it leans on Go's native concurrency for agent orchestration, WebSocket transport, OpenTelemetry observability, and Docker-based deployment. Recent commits show active hardening: provider fixes for Claude adaptive/redacted thinking, vault upsert and migration correctness, lifecycle hook improvements exposing sender/user IDs, and build provenance via embedded commit SHAs — signs of a maturing production codebase.

Compared to OpenClaw, GoClaw trades the massive channel/skills ecosystem and permissive licensing for stronger multi-tenancy, lower resource usage, and enterprise-style gateway features. Its CC BY-NC 4.0 license is a notable constraint for commercial adopters, and its community footprint remains much smaller than the original project.

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.