Running OpenClaw for multiple users requires isolation and security layers
A developer shared their experience running OpenClaw for multiple users, highlighting that while OpenClaw works well as a personal assistant for single users, scaling to multiple users introduces significant security and operational challenges.
Key Challenges with Multi-User OpenClaw
The developer identified several specific problems when trying to run OpenClaw for multiple users:
- Isolating users properly
- Keeping secrets out of the runtime
- Giving agents files without sharing a real filesystem
- Exposing bash without giving away the machine
- Keeping state while not having a 24/7 running instance
The developer noted that Peter (likely OpenClaw creator) has said OpenClaw is meant more like a personal assistant, not a multi-user business system.
The Infrastructure Solution
To address these challenges, the developer built a thin infrastructure layer around OpenClaw with these components:
- One gateway for Slack, Telegram, WhatsApp, and Discord integration
- One isolated worker per user/thread
- Virtual bash (just-bash sandboxing) instead of broad host access
- A virtual filesystem per worker
- Secrets kept in the gateway, not inside workers, with outbound traffic proxied/filtered
- Persistent state with scale-to-zero workers
The developer used this setup for wedding planning, tax return help, prenup/agreement drafting, and small business administration workflows. They also set up OpenClaw for two friends getting married, though maintenance and upgrading proved challenging.
Open Source Project
The solution is available as a fully open-source project at https://github.com/lobu-ai/lobu.
The developer notes that getting OpenClaw to run wasn't the hard part—the challenge was making it usable for multiple people without creating security and operational problems.
📖 Read the full source: r/openclaw
👀 See Also
A Non-Coder's File System Project Management Setup for Claude Desktop
A Reddit user shares their system for using Claude's Chat with Filesystem and Cowork features to manage multiple long-running projects. The setup uses a standardized directory structure with WORKFLOW.txt as the entry point and includes specific project instructions for maintaining continuity across sessions.
User Deploys AI Assistant 'Elvis' on VPS for Project Management Tasks
A developer spent three days setting up an AI assistant called 'Elvis' on a Linux VPS, integrating it with Microsoft Teams, JIRA, Asana, and email systems. The assistant successfully handled project management tasks including reading emails, extracting requirements, updating change requests, and coordinating with team members.
Porting Doom to PS3 Using Claude AI Without Programming Experience
A developer with zero C programming experience used Claude AI over 25 chat sessions to port Chocolate Doom 3.1.0 to PS3 hardware, achieving 35fps with native cellGcm API calls and custom audio/input systems.
Speculative Decoding Benchmarks on RTX 3090 with Qwen Models for HVAC Business Use
A developer tested speculative decoding on an RTX 3090 using Qwen models for an HVAC business Discord bot, achieving up to 279.9 tokens/sec with a 236% speedup using Qwen3-8B with a Qwen3-1.7B draft model.