Self-Hosting on emsenn.net

Compute Infrastructure for Small Organizations

Fri, 03 Apr 2026 00:00:00 +0000

A small organization building a software system faces an infrastructure question that larger organizations can defer to specialized teams: where does the system run? The answer determines cost, operational burden, scaling path, and the degree of control the organization retains over its own systems. This text surveys the real options as of 2026, with documented pricing and practitioner-reported tradeoffs.

¶Virtual private servers

A virtual private server (VPS) is a virtual machine rented from a hosting provider, accessed via SSH, with full root control. It is the most common starting point for small teams.

Companion Tools for OpenClaw, March 2026

Mon, 09 Mar 2026 00:00:00 +0000

¶Purpose

This text surveys the tools that most often recur around OpenClaw in current official documentation and practical guide material as of March 9, 2026. The source base does not support exact usage counts, so “often used” here means recurring companions in the current OpenClaw ecosystem rather than measured market share.

¶What the tool stack reveals

The current OpenClaw ecosystem is converging on a distinctive practice. OpenClaw itself stays as the long-running control plane, memory layer, and multi-channel agent surface. Specialized work is pushed outward:

OpenClaw Gateway

Mon, 09 Mar 2026 00:00:00 +0000

The OpenClaw Gateway is the long-running control-plane process in an OpenClaw deployment. It coordinates sessions, channels, tools, configuration, routing, and web interfaces while the assistant remains the user-facing product surface.

¶Role

The Gateway gives OpenClaw a persistent runtime. It keeps the assistant reachable through chat channels, the Control UI, WebChat, and paired device surfaces without reducing the system to a single interactive terminal session.

¶Trust boundary

OpenClaw’s security model treats the Gateway as a trusted operator boundary, not as a hostile multi-tenant service. Within one Gateway instance, authenticated control-plane access carries authority over the configured agents, sessions, and policies in that deployment.

OpenClaw Node

Mon, 09 Mar 2026 00:00:00 +0000

An OpenClaw node is a paired device surface that exposes host-local capabilities to an OpenClaw Gateway. Nodes let the assistant act through device-specific interfaces such as voice, camera, screen capture, notifications, and host-local command execution.

¶Pairing model

OpenClaw documents node pairing as an operator-approved connection to a Gateway. Once paired, node actions are treated as trusted operator actions on that device rather than as requests from an untrusted external sender.

OpenClaw Summary, March 2026

Mon, 09 Mar 2026 00:00:00 +0000

¶Purpose

This text surveys OpenClaw as of March 9, 2026. OpenClaw is a self-hosted personal AI assistant platform organized around a persistent OpenClaw Gateway that exposes one assistant across the channels and devices a user already uses.

¶What OpenClaw is

The OpenClaw repository describes the project as a personal AI assistant that runs on the user’s own devices. The README’s central claim is that the Gateway is only the control plane. The product is the assistant itself: an always-available agent that can answer through messaging platforms, web chat, and companion apps.

Using OpenClaw on Windows, March 2026

Mon, 09 Mar 2026 00:00:00 +0000

¶Purpose

This text collects practical advice for using OpenClaw on Windows as of March 9, 2026. The source base combines official OpenClaw documentation with two independent guides that contain operational advice rather than only product description.

¶Baseline: treat Windows as a WSL2 host

The official OpenClaw guidance is consistent: on Windows, run OpenClaw through WSL2, with Ubuntu recommended. The Windows page states that native Windows installs are untested and more problematic, while the CLI and Gateway are expected to run inside Linux.