Arthritis Took My Hands Offline for 3 Days. The System Did Not Notice.

Running six apps and writing seventeen books while working a senior job at a tech company full time.

Last March, the arthritis flared badly enough that typing was hard for three days. Not dramatically hard. Just painfully impractical. I could peck things out slowly but sustained writing was out.

The content pipeline published on schedule. LinkedIn, Medium, Pinterest, Substack, Mastodon, Quora, Dev.to, IndieHackers, and the blog on chadtdyar.com, all covered, all on time, all from content generated the previous Sunday when my hands were working fine.

That is the whole design goal in one Tuesday morning.

Current numbers: Six live apps, ContentForge at contentforgehq.com, Momentum at momentumfit.app, HomeGrown at thehomegrown.app, PillPal at getpillpal.app, PawFormance at pawformance.app, Palette Pro at hue-pilot-pro.lovable.app. Seventeen published books across professional development, SEL picture books, and fiction. Forty distribution accounts across nine platforms. One automated pipeline running off a Supabase marketing queue, a local Python publisher process, and a scheduled content generation task every Sunday evening.

Revenue situation: early stage across the apps. ContentForge and the Lovable apps are converting free users but the paid tiers are still building. Book revenue is consistent but not the main story. The infrastructure story is.

What I want to know from people who have done similar things: at what scale does keeping the publisher process local become untenable? Running it on my machine means machine-down equals queue-backup. Been debating moving it to a Cloudflare Worker but have not pulled the trigger.