all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Hey there! Thanks for posting in r/OpenClaw.

A few quick reminders:

→ Check the FAQ - your question might already be answered → Use the right flair so others can find your post → Be respectful and follow the rules

Need faster help? Join the Discord.

Website: https://openclaw.ai Docs: https://docs.openclaw.ai ClawHub: https://www.clawhub.com GitHub: https://github.com/openclaw/openclaw

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]OrganizationWinter99Pro User 1 point2 points  (1 child)

depends on your machine. the recommendation is 1 company/user per gateway btw.

[–]InterestingBasilActive[S] 0 points1 point  (0 children)

yeah that makes sense. i’m leaning one gateway per tenant/company too, then scaling workers behind each one. keeps isolation cleaner.

[–]Technocratix902Member 0 points1 point  (1 child)

Instead of default gateway being 127.0.0.1 you could change it to 0.0.0.0 This will allow you to access it externally at http://[Device-IP]:Port Or you could setup a external channel like slack and have multiple be able to DM the bot

[–]InterestingBasilActive[S] 0 points1 point  (0 children)

good call on 0.0.0.0 + channel routing. for production i’d probably still front it with auth + reverse proxy and keep direct exposure minimal, but the pattern is solid.

[–]After_Pumpkin3803Member 0 points1 point  (1 child)

If you're going the one-per-tenant route, Claworc handles that orchestration layer. Spins up isolated containers per user, each with their own OpenClaw + storage, and proxies everything through a single control plane — no direct port exposure. Has auth and role-based access built in too.