Last post of the series, and the one people will actually ask about: can you do this, and should you?

Short answer: yes, and probably, but manage your expectations.

What it costs. Time, mostly. I reused subscriptions I already had (chat model access, an existing VPS, a NAS I’d had for years). The only real spending was a few API keys and a bit of compute. If you’re starting from zero you can run a surprising amount of this on a $20 a month VPS plus whatever you already pay for a chat model. The expensive part is the hours, not the dollars.

What you need. A genuine itch. Not “AI is cool”, but a specific thing you’re sick of doing by hand. Mine was dinner decisions and context switching. Yours might be email triage, expense tracking, or remembering people’s names. Start there. The assistant that survives is the one that does one job you actually care about, and grows from that.

What you don’t need. A homelab. I have one because I already had one, but the same stack runs fine with nothing but a VPS and a laptop. What you do need is a tolerance for debugging, because the first month is mostly that, and the willingness to say the assistant wrote this when it did.

What surprised me most. That the ceiling isn’t the technology. It’s the trust. The moment I started letting it remember things and run things without me watching, everything changed. That’s a leap, and it’s a personal one. I can’t tell you when to make it. I can tell you it was worth it.

That’s the month. If you’ve read this far, you now know more about my assistant than most of my clients do. Ask me anything, or better yet, go build the one you’ve been thinking about. If you do, I’d genuinely love to hear how it goes.

Tags on this series: build-log, hermes-wrote-this. Every post in it was drafted by my assistant from my notes and logs, and reviewed by me before publishing. That’s the deal, and it’s a good one.

Nobody wants to read about boring infrastructure, so I’ll keep this short, but it’s the reason any of this works and it’s the bit people always skip.

My setup, in one breath: a Synology DS218+ NAS at home running the media stack, Home Assistant, and a reverse proxy (SWAG) behind Cloudflare. A Hostinger VPS in the cloud running Coolify, n8n, and the Mission Control stack. Tailscale stitching it all together into one private network. Docker everywhere, because Docker is how you stop fighting your own servers.

Three rules I kept the whole month:

No new firewall ports. Anything new gets exposed through the reverse proxy or over Tailscale. My perimeter is smaller now than when I started, which is the opposite of how these projects usually go.

Encrypted backups of everything that’s hard to rebuild. The assistant’s config, my Google tokens, the skills library. If the PC dies, the recovery path is documented and tested, not improvised.

Monitoring from both sides. Uptime Kuma watches from the internet, the assistant watches from inside. When a website went down last month, I knew before anyone else did, because two different systems both noticed and one of them texted me.

The boring truth about self-hosting: it’s not cheaper, it’s not easier, and it will occasionally ruin your evening. What it gives you is ownership. My assistant’s memory lives on my hardware. My automations don’t vanish when a startup pivots. My data is mine, my failure modes are mine, and my fixes are mine too.

I’d rather own my problems than rent someone else’s.

A month is long enough for the honeymoon to end and the real relationship to start. Here’s the honest report.

What broke. Plenty, and that was the point. A scheduled script had a timezone bug that was quietly producing wrong dates for months before we caught it (a fixed +12 offset forgot daylight saving, which is peak irony for a country that changes its clocks twice a year). A WordPress admin lockout ate a whole evening and taught me more about my own backup strategy than I wanted to know. A bridge between my desktop and the VPS refused to connect because a database driver was stricter about SSL than the last version. Every break was a lesson, but the stat that matters is that I spent roughly a third of the month fixing things and two thirds watching things work.

What stuck. The deal cron (never missed a night, and it’s bought my dinner twice). The spend watchdog (it caught a runaway job at 2am before it cost me real money). The morning briefing (I genuinely miss it when it doesn’t run). The knowledge graph (the more it knows, the more I rely on it). The things that stuck are the ones that removed a decision I used to make every day.

What surprised me. Three things. One: how much better a remembering assistant is than a clever one. Give me a model that remembers what I said last week over a model that’s 10% smarter, every time. Two: how quickly it became normal. The future is just a text message that knows your history. Three: how much of it is plumbing. The assistant is 90% infrastructure and 10% intelligence, and that’s not a bug, that’s the job. The magic is in the plumbing.

Would I do it again? Yes, and I’d start the same way: one automation that matters to you personally, then let it grow. More on that in the last post of this series.