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.
153
published stories2
public authors13,229
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.
Shared Credits, Separate Realms: Run 5 Brands Without Cross-Billing Chaos
One client's runaway agent just burned another brand's entire monthly credit budget. If you're running multiple brands on one AI workspace, you're one misconfigured key away from the same disaster. There's a governance pattern that fixes this at the architecture level.
Build a Public-Service AI Assistant Like Malaysia's AI for the People
Everyone wants to build an AI assistant for the public good, but most teams ship a chatbot that nobody trusts and nobody uses. The gap isn't model quality. It's the architecture around it. Here's the pattern that changes everything.
Shared Agent Wallet: Spend Limits for Family and Team
Your AI agents are spending money across five platforms with zero oversight. One leaked key drains the account before you notice. The fix is a shared wallet with hard limits, and it takes an afternoon.
How DevGhouse Runs a Coding Lane End to End
Every DevGhouse feature moves through the same seven seats, from Starter to Merger, and skipping a seat never skips the work it does.
One AI Account, Three Lives: Wedding, Business, Chess League
Juggling a wedding, a side hustle, and a chess league in separate apps is a recipe for burnout. You don't need more tools - you need one AI account that runs them all. Here's the exact system.
7 AI Patterns That Declutter Work and Personal Apps Fast
Your digital life is a mess: 20 apps, 50 tabs, endless notifications. It's costing you hours weekly and constant mental load. There's one pattern that changes everything. And it's not in any tutorial.
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.