Managed OpenClaw • Per-user agents • Persistent chat

OpenClaw, turned into a clean hosted product.

Redclaw is a managed SaaS layer around OpenClaw. It adds user accounts, assigned agents, persistent chat, skill controls, backend-managed runtime config, and credits-based billing.

User: Summarize my last meeting and extract action items.
Redclaw → OpenClaw agent → returns answer, stores history, updates billing.
Skills are installed once on the server and exposed per user agent through config.

Core capabilities

Redclaw keeps the OpenClaw runtime underneath, while adding the product layer needed to operate it like a real hosted app.

Per-user agents

Each user gets one assigned OpenClaw agent, one workspace, and one main conversation path.

Managed runtime config

The backend owns the main OpenClaw config and syncs per-agent visibility and behavior automatically.

Credits billing

Usage is priced, marked up, converted into credits, and finalized or refunded after each run.

How it works

Runtime layer

  • OpenClaw runs in Docker on the VPS
  • One main config with shared defaults + per-agent overrides
  • Shared skill inventory under the OpenClaw data root
  • Config-driven skill visibility per assigned agent

Product layer

  • Supabase for auth and data
  • Express backend for orchestration
  • RevenueCat for subscriptions and top-ups
  • Frontend connects through the Redclaw API

Current stack

Frontend

Client app with Supabase sign-in, chat UI, skill toggles, billing screens, and account settings.

Backend

Node.js + Express control plane that provisions agents, syncs config, handles chat, and processes billing events.

Data + Billing

Hosted Supabase stores users, agents, messages, skill state, plans, purchases, and credit ledger records.