<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/self-hosted/</link><description>Recent content in Self-Hosted on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/self-hosted/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Pasting API Keys and Bank Cards into LLM Relays: A Guide to Self-Hosted Privacy Gateways</title><link>https://blog.lynxflow.co/en/posts/llm-privacy-self-hosted-gateway-guide/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/llm-privacy-self-hosted-gateway-guide/</guid><description>&lt;img src="https://blog.lynxflow.co/images/llm-privacy-self-hosted-gateway-guide.png" alt="Featured image of post Stop Pasting API Keys and Bank Cards into LLM Relays: A Guide to Self-Hosted Privacy Gateways" /&gt;Using a third-party LLM relay to access Claude, GPT, or Gemini is cheap and convenient—but have you considered this: the relay operator can see every single word you send to the model.
That includes API keys you casually paste in, bank card numbers, login passwords, ID numbers, medical records&amp;hellip; all sitting in someone&amp;rsquo;s server logs, in plaintext.
This isn&amp;rsquo;t paranoia—it&amp;rsquo;s architecture. A relay is fundamentally a reverse proxy: your request hits their server, gets unwrapped</description></item><item><title>I Turned 148 GitHub Repos Into 'Can't Lose Them All': A Full 3-2-1 Backup Retrospective</title><link>https://blog.lynxflow.co/en/posts/github-backup-3-2-1-2026/</link><pubDate>Mon, 24 Aug 2026 09:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/github-backup-3-2-1-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/github-backup-3-2-1-2026.png" alt="Featured image of post I Turned 148 GitHub Repos Into 'Can't Lose Them All': A Full 3-2-1 Backup Retrospective" /&gt;I counted the repos in my own GitHub account: 148 total—126 private, 22 public—with 3 forks mixed in. Just the repo objects (not counting metadata) amount to over 3 GB. Five-plus years of commit history, unfinished experimental code, automated scripts still running—all there.
Then I stared at that number for a while and asked myself a question: If this account vanished tomorrow, what would I still have?
The answer made me uncomfortable. So last week I spent an all-nighter turning those repos int</description></item><item><title>Installing a Control Plane for 'Script + Cron + Agent' Black-Box Automation: A Survey of 12 Platforms</title><link>https://blog.lynxflow.co/en/posts/2026-08-23-workflow-control-plane-selection/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/2026-08-23-workflow-control-plane-selection/</guid><description>&lt;img src="https://blog.lynxflow.co/images/2026-08-23-control-plane-architecture-cover.png" alt="Featured image of post Installing a Control Plane for 'Script + Cron + Agent' Black-Box Automation: A Survey of 12 Platforms" /&gt; TL;DR: What I need isn&amp;rsquo;t another orchestration tool, but a Control Plane—a coordination layer that answers in one place: which workflow, which version, which run, which step failed, how many retries, when&amp;rsquo;s the next run. cron only knows how to &amp;ldquo;knock on time&amp;rdquo; and then walks away. After surveying 11 platforms, my pick: Windmill first choice, Kestra co-selected; n8n/Temporal/Argo explicitly rejected; Hermes demoted to &amp;ldquo;scheduled agent&amp;rdquo; instead of scheduler.</description></item><item><title>RSS to Social Media Auto Distribution: A Panoramic Survey of Open-Source Projects (The Peers of LynxPipe)</title><link>https://blog.lynxflow.co/en/posts/rss-to-social-media-oss-pipeline-landscape/</link><pubDate>Sat, 22 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/rss-to-social-media-oss-pipeline-landscape/</guid><description>&lt;img src="https://blog.lynxflow.co/images/2026-08-22-rss-social-oss-four-layer-cover.png" alt="Featured image of post RSS to Social Media Auto Distribution: A Panoramic Survey of Open-Source Projects (The Peers of LynxPipe)" /&gt; TL;DR: There&amp;rsquo;s no single open-source project that handles &amp;ldquo;RSS aggregation → processing → social distribution&amp;rdquo; end-to-end, but every layer has mature tools. The combination closest to LynxPipe&amp;rsquo;s full form is RSSHub (sources) + Huginn/n8n (processing) + Postiz (distribution), with a combined star total exceeding 280k. Here&amp;rsquo;s the full research: each project&amp;rsquo;s star count (measured via GitHub API on 2026-08-22), RSS capabilities, and supported social channels.</description></item><item><title>Hermes vs OpenClaw: Which Self-Hosted AI Agent Harness in 2026</title><link>https://blog.lynxflow.co/en/posts/hermes-vs-openclaw/</link><pubDate>Fri, 31 Jul 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/hermes-vs-openclaw/</guid><description>&lt;img src="https://blog.lynxflow.co/images/hermes-vs-openclaw.png?v=090818" alt="Featured image of post Hermes vs OpenClaw: Which Self-Hosted AI Agent Harness in 2026" /&gt;The two rising self-hosted agent harnesses Hermes and OpenClaw are two open-source, self-hostable AI agent harnesses attracting growing attention in 2026. Both let you run an agent that talks to humans across messaging channels, calls tools, and maintains state — but they differ in language, philosophy, and ecosystem.
Dimension Hermes OpenClaw Repo NousResearch/hermes-agent openclaw/openclaw Version (2026-07-31) 0.16.0 2026.7.1-2 Language Python Node.js / TypeScript License MIT MIT One-liner The</description></item><item><title>Self-Hosted AI Agent Landscape 2026</title><link>https://blog.lynxflow.co/en/posts/self-hosted-agent-landscape-2026/</link><pubDate>Fri, 31 Jul 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/self-hosted-agent-landscape-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/self-hosted-agent-landscape-2026.png" alt="Featured image of post Self-Hosted AI Agent Landscape 2026" /&gt;Two categories that get conflated &amp;ldquo;AI agent&amp;rdquo; in 2026 covers two very different things, and mixing them up causes most bad choices:
Build-your-own frameworks — libraries you code against to assemble an agent (LangGraph, CrewAI, AutoGPT-style). You own the plumbing: tool-calling loops, memory, channels. High control, high effort. Ready-to-run harnesses — a packaged agent you install, configure, and deploy as a service. It already has the reasoning loop, the channels, the skills system.</description></item></channel></rss>