Automate a self-hosted stack on your own hardware

Jordan Fulghum let Claude Code configure and run several home services on a Beelink mini PC.

Done with Claude Code· Intermediate

What they did
Jordan Fulghum installed Ubuntu Server on a Beelink mini PC, added Tailscale for remote access, and worked from a laptop through SSH. They asked Claude Code to carry out the setup in plain English, and it built the Docker environment, generated Compose definitions, set up Caddy, and brought up Vaultwarden, Immich, Plex, and Readeck. The agent also created a monitoring view and backup workflow, while Jordan created the AWS IAM user on their own.
How it went
The system now hosts 14 containers, with CPU staying below 10% and memory use around one-third. A daily USB backup plus a weekly S3 Glacier copy protects about 500GB of photos for roughly twenty cents per month. Plex hardware transcoding still requires a Plex Pass.
Tips
Keep account creation and access-control decisions for yourself when you hand off infrastructure work to an agent. Ask for a clear pause before any change that could remove data, expose a port, or submit something live.

Try it yourself with Claude Code

I want to run [service or services] on a self-hosted machine at [device name or IP]. Check what is already installed, then create or update the Docker Compose files, reverse-proxy setup, monitoring, and backup plan for me. Explain each step as you go, and pause for my approval before any action that would delete data, change network exposure, alter firewall rules, or publish the service. When finished, confirm that [service] is available at [URL] and give me a short checklist of the backup routine.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on fulghum.io ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.