Pleng: Self-Hosted Cloud Platform with AI-Driven Infrastructure Management

Pleng is a self-hosted cloud platform driven by an AI agent designed to simplify infrastructure deployment and management. The tool addresses what the creator calls "localhost syndrome"—the friction of manually setting up VPS, Docker, Traefik, and SSL certificates that often prevents side projects from reaching production.
How It Works
You install Pleng with a single command on a fresh Ubuntu VPS. Instead of using a dashboard, you manage your entire infrastructure through a Telegram bot using natural language commands. For example, you can text the bot: "Deploy the main branch of this GitHub repo to mydomain.com" or "Why is my app crashing?". The AI agent then handles cloning, Docker containers, reverse proxy setup, SSL configuration, and log reading.
Security Architecture
The creator acknowledges the security concerns of giving an AI root server access. Pleng addresses this with strict isolation measures:
- The agent runs inside a heavily sandboxed Docker container
- It has NO access to the host machine, NO sudo privileges, and NO access to the Docker socket
- It can only affect infrastructure by calling a separate platform API over HTTP
- It uses a deterministic CLI tool under the hood that can deploy, restart, fetch logs, or read metrics, but cannot execute destructive commands like
rm -rf /
Current Features
- Deploy from GitHub (public or private repos) or local directories
- Automated Traefik routing with Let's Encrypt SSL certificates
- Built-in basic analytics for pageviews and visitors
- Automated backups, health monitoring, and log inspection directly in the chat interface
The tool is licensed under AGPL-3.0 and represents an early version built primarily to solve the creator's own deployment challenges. It's positioned as useful for indie hackers and developers who want to push projects to production with minimal friction.
📖 Read the full source: r/openclaw
👀 See Also

Claude Code: How to Connect Your AI-Built Frontend to a Real Backend
Claude Code builds polished frontends but often uses hardcoded data. Here are four ways to connect it to real backends: raw APIs, SDKs, CLIs, and MCP.

AutoClaw Local Runner Review: Easy Setup, Credit Costs, and Uninstall Issues
A user tested AutoClaw, a local runner for OpenClaw/AutoGLM from Zai_org, finding the setup smooth but encountering high credit consumption, task failures, and concerning persistence after uninstallation including registry entries and plaintext credentials.

AutoSkillUpdate: A Claude Code Plugin That Detects Outdated Skills
AutoSkillUpdate is an open-source Claude Code plugin that scans your codebase, compares it against existing skills, and identifies drift. It provides drift reports with file paths and line references, then offers to rewrite outdated skills with user confirmation.

Benchmark Results: 15 LLMs Tested on 38 Real Workflow Tasks
A developer benchmarked 15 cloud and local LLMs on 38 tasks from their actual workflow, including CSV transforms, letter counting, modular arithmetic, and format compliance. Claude 3.5 Sonnet and Opus both scored 100%, but Sonnet costs 3.5x less per call.