openclaw-host-kit

Infrastructure

self-hosted deployment

SHOW HN2026

openclaw-host-kit

Open source setup to self-host OpenClaw instances on any host

github.com

#self-host#traefik#docker hosting#multi-tenant#openclaw

7points
9comments
#3,530of 4,366 in 2026
Top 81%of 2026 by points

How HN took it

MixedNo clear lean

3 positive, 1 neutral or asking, 2 mixed, 0 critical, out of 6 comments about the project. Thread score +0.35.

Idea: 2 for, 0 againstDesign: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Useful for people who already run a VPS and want isolated per-user resources

    From 3 comments
    • This is a neat idea, especially for people who already have a VPS lying around. I like that you didn’t try to hide the complexity behind too much magic. The sizing notes are…
      faizan1009 on HN
    • This feels like something internal teams could use to spin up multiple OpenClaw environments fast. The wildcard DNS + provisioning script combo sounds convenient. I like that…
      rehman24 on HN
    • This seems perfect for people who already self-host things. Probably not beginner-friendly, but that’s fine. The value here is avoiding all the annoying glue work most people…
      adeebch39 on HN
  • Keeps forward-auth small and readable

    From 1 comment
    • The forward-auth piece caught my attention. Keeping it small and readable is a nice touch. Security-wise, this looks decent, but I wonder how it holds up once multiple people…
      muneebch1009 on HN

Objections

  • About 4GB RAM per instance is expensive

    From 1 comment
    • I’m a bit torn on this. On one hand, owning the infra is great. On the other, 4GB per instance is not cheap anymore. Curious if that number comes from real usage or just safe…
      azfar0007 on HN
  • Chromium instances use a lot of memory

    From 1 comment
    • Very true and actually totally spot on! It's the damn chromium instances that chugs memory like an Irish man chugs beer. I experimented launching containers with it and quickly…
      vishnukool on HN

Requests

  • Add a monitoring dashboard

    From 1 comment
    • This feels like something internal teams could use to spin up multiple OpenClaw environments fast. The wildcard DNS + provisioning script combo sounds convenient. I like that…
      rehman24 on HN

Questions

  • How painful are upgrades with many tenants

    From 1 comment
    • This is a neat idea, especially for people who already have a VPS lying around. I like that you didn’t try to hide the complexity behind too much magic. The sizing notes are…
      faizan1009 on HN
  • Is the 4GB figure from real usage

    From 1 comment
    • I’m a bit torn on this. On one hand, owning the infra is great. On the other, 4GB per instance is not cheap anymore. Curious if that number comes from real usage or just safe…
      azfar0007 on HN
  • How does the auth hold up with multiple users

    From 1 comment
    • The forward-auth piece caught my attention. Keeping it small and readable is a nice touch. Security-wise, this looks decent, but I wonder how it holds up once multiple people…
      muneebch1009 on HN

Alternatives named

  • Managed OpenClaw hosting

    From 1 comment
    • I wanted to let a few friends get a hosted OpenClaw setup without each of them dealing with Docker, reverse proxy, SSL certs, etc. So I built a small toolkit that turns one Linux…
      vishnukool on HN
  • Agent 37 hosted OpenClaw offering

    From 2 comments
    • At the moment it's more of a demo for hobby users setting up for themselves and friends, but if it's an enterprise use case where you need more control, we have…
      vishnukool on HN
    • Yes exactly! Although we've launched a Claude Skill to help setup OpenClaw! So Agent 37 is literally the easiest Openclaw setup at this point :)
      vishnukool on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/46946310)