Article · 4 min read

I run servers for a living. Here's why I'm building creator automation.

A note on where CreatorLab comes from: infrastructure work, a homelab, and a bias toward systems you can actually run yourself.

Back to Learn
Grzegorz Rodak
FounderBuild in public

By day I'm an infrastructure engineer at Gcore, working on edge and distributed systems. By night I run a homelab — Proxmox, Docker, Coolify, a stack of self-hosted apps, and local LLMs on my own hardware. CreatorLab comes straight out of that world.

Why that background matters here

Years of running things in production teaches you a healthy distrust of magic. Systems break under load, in the gaps between tools, and right where someone assumed a step was safe to automate. That instinct is exactly what creator automation needs — because the failure mode here isn't downtime, it's publishing something off-brand to your audience.

It also makes me biased toward portability. I'd rather give you a workflow you can import, read, and run on your own runtime than a black box you rent. The Newsletter Research Desk ships as an n8n file with placeholder credentials, a schema, and a setup guide — not a login to someone else's platform.

  • Workflows you can read, edit, and self-host
  • Local-LLM-friendly — your keys and data stay yours
  • Approval gates built in, not bolted on

Everything I publish here gets tested on real hardware before I write about it. I don't recommend things I wouldn't run myself.

Free weekly briefing

Become the creator operator your business needs.

Get the starter kit