zolvek.net · Falkenstein
A compact host for automation, observation, and an LLM agent.
AI Tools is a purpose-built Docker host. Caddy publishes HTTPS; each app is its own Compose stack on a private proxy network. Small on purpose, so every new service has to earn its RAM.
proxy
Deployed
Three tools, one public info page.
Each hostname is a purpose, not a product name. They share the host, not a Compose file.
Flows
n8n workflow automation. Connect APIs, webhooks, and schedules without putting another runtime on the box.
Open flowsMonitor
Beszel hub and agent. Host CPU, RAM, disk, and per-container usage so the 4 GB budget stays visible.
Open monitorAgent
Hermes Agent dashboard. An LLM agent with memory, skills, and a capped memory limit so it cannot starve the rest of the host.
Open agentPlatform
Built as a control plane, not a pile of containers.
Git is the source of truth. Stacks sync to /opt independently. Public HTTPS exists only through Caddy; apps expose ports on the Docker network and never publish 80 or 443 themselves.
-
Location
Hetzner Cloud, Falkenstein (
fsn1), Ubuntu LTS. -
Network
Domain
zolvek.net. A and AAAA records, TLS at the edge. - Isolation One Compose project per app. Named volumes hold runtime state; they are never torn down casually.
- Authoring Reusable Python, n8n workflow exports, and Hermes skills live beside the stacks, not only on the server.
Potential
Headroom for more purpose-named tools.
The host is already wired for another stack: add Compose, a Caddy site block, DNS, and a light container. Monitoring is in place before the next service arrives.
Automation that compounds
n8n can grow into a library of versioned workflows: alerts from Beszel, webhook receivers, reports, and glue between APIs — without a second application server.
An agent with a job
Hermes can take provider keys, skills, and longer sessions. The dashboard is already public; the memory cap keeps it a neighbor, not a tenant that fills the machine.
More small sites
This page is nginx on 32 MB. Status pages, internal docs, and landing URLs fit the same pattern: static files, Caddy, a purpose subdomain.
A known budget
4 GB is the constraint and the design. New work stays lightweight, observed, and independently deployable — or it does not ship here.