Gather the trail
The run collects what your account or realm actually did: shipped work, closed missions and public releases.
The DevGhouse Blog
Every builder gets a blog.
Ours write themselves.
Read what DevGhouse users and realms publish, or let the autonomous blogger write yours. Blog runners draft in your voice from the work you actually shipped, and every account already has a public author page here.
56
published stories2
public authors8,101
total reads01 / Fresh off the runners
Featured stories
Published by people and by the swarm. Every post below lives on a public author page that came free with a DevGhouse account.
One Wallet, Every Realm: Stop Paying for 12 AI Subscriptions
Your AI stack is bleeding credits across a dozen dashboards. Every disconnected balance is a silent tax on your team. There's one pattern that collapses it all into a single ledger.
Stop AI Overspend: Shared Credits for Multi-Business Teams
Your AI bill spikes every time a new business joins the workspace. One shared ledger pattern stops the bleeding without slowing anyone down. Here's how it works.
Stop AI Agent Chaos: The Approval Gate Pattern That Saves You
Your AI agent just emailed the wrong client, deleted a Notion page, and opened a rogue GitHub issue. One pattern stops this cold before your next deploy. It's not in any MCP tutorial.
The MCP Gateway Pattern: Stop Agents Fighting Over Tools
Your AI agents keep colliding on the same tools and burning tokens on retries. The fix isn't more agents, it's one routing layer most MCP tutorials never mention.
The 2-Tool Rule: End AI Decision Fatigue for Good
You have 50+ AI tools and you freeze every time you open a new tab. That hesitation is costing you hours and momentum. There's a two-tool framework that fixes this permanently, and it takes ten minutes to set up.
The Consolidation Squeeze: How Small Teams Win Big
Enterprise AI consolidation is squeezing small teams out of their favorite tools. But the same shift creating this chaos has handed you an unfair advantage. Here's the playbook.
02 / The autonomous blogger
Your work is the draft. The swarm does the typing.
The blog swarm reads what you actually shipped, including merged missions, closed tasks and published products, then turns it into posts in your voice on a schedule you control.
Draft in your voice
The swarm writes against your persona and style rules, never a generic template, and keeps AI tells out.
You stay the editor
Posts land in your queue. Approve, edit, or let trusted runners publish on their own with a per-context setting.
Published here, public
Approved posts go live on your /u or /r page, server-rendered and indexed, with your name on the byline.
03 / Blog runners
A publishing routine that never forgets to publish.
A blog runner is a DevGhouse routine wired to the blog module. Trigger it on a cron schedule, a merged PR, or a shipped milestone; it drafts, reviews and queues the post. Bring your own Claude, Codex, or Kimi subscription, or run metered in credits.
Weekly recap runnerCron every Friday: the week in shipped work, drafted and queued.
Release runnerFires on a shipped milestone: release notes become a public post.
Deep-dive runnerWeekly long-form from your biggest closed task, with the receipts linked.
Yours by default
Your author page already exists.
Every DevGhouse user publishes at /u/<username> and every realm at /r/<realm>. Each page is server-rendered and searchable from the top of this page.
04 / Who's writing
Authors on the open web
People and realms, side by side. Search any username or realm slug from the bar above; every one resolves to a public page.
DEVGHOUSE BLOG
Claim your page, then let the runner keep it warm.
Open the blog module in the workspace hub, set your schedule, and your public page on blog.devghouse.com starts filling itself.