What We've Been Building: A Tour of Our Latest GitHub Repositories
From AI-powered DNS management to a full infrastructure operations platform — here's a candid look at the 10 most recent repositories across our webhousecode and cbroberg GitHub accounts, and what each one does.
We build a lot of software. Some of it is for clients, some of it is infrastructure we run ourselves, and some of it is tooling that makes our daily work faster and less error-prone. Most of it lives in private repositories — working code that quietly does its job. But occasionally we think it's worth opening the curtain a little.
Here's a tour of the 10 most recent repositories across our webhousecode organisation and cbroberg personal account — what they are, what they do, and whether they're public or private.
1. cms — The Brain Behind @webhouse/cms
🔓 Public · webhousecode · Last active: March 2026
This is the most active repository we have right now, and it's the one we're most excited about. cms is the core engine powering @webhouse/cms (or webhouse.app)— our own developer-first content management system that we've been building and writing about in the CMS Chronicle series.
The recent commits tell the story better than any description could. In just the past few days: an AI Orchestrator with a curation queue and approval workflow, configurable AI agents (Content Writer, SEO Optimizer, Translator, Content Refresher), a token budget tracker, an MCP client and server with public and admin tool surfaces, brand voice discovery via conversational interview, link-checking logic, and an llms.txt manifest for AI agent discovery.
This is what an agentic CMS actually looks like from the inside — agents that run on a schedule, propose content, wait for human approval (or self-publish when trust is high enough), and expose themselves to AI clients via Model Context Protocol.
Stack: TypeScript · Next.js · Anthropic API · MCP
2. whop — WebHouse Operations Platform
🔒 Private · webhousecode · Last active: March 2026
This one is purely internal — and it's a good example of the kind of tooling we build to keep 30 years of infrastructure under control.
WHop (WebHouse Operations Platform) is our server inventory, health monitoring, and migration planning tool. It maps 21 servers across AWS Frankfurt, Stockholm, Ireland, and Keyweb Erfurt — with 419 Apache VirtualHosts scanned and indexed across them. The dashboard shows server cards with notes, EOL warnings, sites, SSL health, and disk status.
The standout feature is the AI migration analyser: it sends real per-server data (DNS-confirmed sites, traffic, bandwidth, monthly cost) to Claude and gets back a structured migration plan — priority actions, estimated savings, proposed new infrastructure, and a migration order. With several servers still running Ubuntu 16.04 and 18.04 (EOL), this isn't a theoretical exercise.
Scheduled cron jobs handle HTTP health checks every 15 minutes, nightly SSL checks, Apache log collection, AWS sync, DNS sync, and weekly SSH scans — all managed via our own cronjobs.webhouse.net platform.
Stack: Next.js 15 · TypeScript · Tailwind CSS · SQLite/Drizzle · Anthropic API · ssh2 · AWS SDK
3. whapi — Internal API Testing Platform
🔒 Private · webhousecode · Last active: March 2026
WHapi is our internal replacement for Postman — a modern API testing and documentation platform, live at api.webhouse.net.
It's a full HTTP client with support for GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS — with query params, headers, JSON/text/form body, and bearer/basic/API-key auth. Requests are organised into collections and folders, with drag-to-reorder. There's environment switching with {{variables}}, a server-side HTTP proxy (no CORS issues), a history of the last 500 requests per user, and Postman v2.1 import.
The API Docs feature lets you load any OpenAPI 3.x spec by URL and browse endpoints inline — clicking an endpoint pre-fills the request builder. Authentication is passwordless: a 6-digit OTP sent to your email, whitelist-only.
We built this because Postman has become bloated and account-dependent. This one runs on a 1 GB fly.io instance with a SQLite database and does exactly what we need.
Stack: Next.js 16 · TypeScript · Tailwind CSS v4 · shadcn/ui · SQLite/Drizzle · undici · fly.io
4. webhouse-site — This Very Website
🔒 Private · webhousecode · Last active: March 2026
The repository for webhouse.dk itself — the site you're reading right now.
It's built with Next.js and our own @webhouse/cms, which means the articles, case studies, services, and team pages you see are all managed through the CMS we're actively developing. The site is, in a sense, both a product showcase and a live test environment for our own tooling — every new CMS feature gets exercised here first.
Stack: Next.js · @webhouse/cms · TypeScript
5. dns-mcp — DNS Management via Claude
🔒 Private · webhousecode · Last active: February 2026
This is a TypeScript/Node.js MCP (Model Context Protocol) server that gives Claude direct access to manage DNS zones and records — from any Claude client, including Claude Desktop, Claude Code, claude.ai, and the iOS/Android apps.
The server exposes 12 tools covering everything from listing and creating zones, to batch-upserting records and verifying that expected records exist. You can literally type "Create an A record on www.example.dk pointing to 1.2.3.4" into Claude and it happens.
It supports both stdio transport (for local use with Claude Code and Claude Desktop) and an HTTP transport hosted at dnsmcp.webhouse.net with OAuth 2.1 authentication — so it works on mobile too. This is the MCP in practice that we've been writing about: not a demo, but a tool we use every day.
Stack: TypeScript · Node.js · MCP SDK · OAuth 2.1 · fly.io
6. dns-api — REST API for BIND 9 DNS Management
🔒 Private · webhousecode · Last active: February 2026
The API that dns-mcp (and dns-gui) sit on top of. This is a REST API built with Hono and Bun that controls BIND 9 DNS zones on our master DNS server (dns2.webhouse.net) via SSH.
It manages 399 DNS zones across a master/slave setup (Frankfurt → Ireland), with a full set of endpoints for zones and records — including batch upsert, record verification, and JSON templates for common configurations like Resend email setup (DKIM, SPF, DMARC, MX in one call).
Design choices worth noting: a dedicated dnsapi service user (not a personal account), one SSH TCP connection per operation, per-domain mutex locking, automatic zone file backups before every change, named-checkzone validation before reload, and deterministic SHA1 record IDs. It's the kind of unglamorous infrastructure work that keeps 399 client domains running correctly.
Stack: Hono · Bun · TypeScript · SSH · BIND 9 · fly.io
7. dns-gui — Web GUI for DNS Management
🔒 Private · webhousecode · Last active: February 2026
The browser-based front-end for managing DNS zones and records through the dns-api. Accessible at dns.webhouse.net, it gives us a visual interface for the same operations available via the API and the MCP server.
Together, dns-api, dns-mcp, and dns-gui form a complete DNS management stack — usable from the browser, the terminal, or a conversation with Claude.
Stack: TypeScript · Next.js (inferred)
8. fysiodk-aalborg-sport — Sports Injury App
🔒 Private · webhousecode · Last active: March 2026
A hybrid mobile and web application for sports injury reporting and case management at FysioDanmark Aalborg Sport, live at sport.fdaalborg.dk and published on both the App Store and Google Play.
Patients can report a sports injury in under two minutes using a guided flow with an interactive body model. Physiotherapists get a case management dashboard. Clinic administrators have full user management, audit logging, and statistics. The whole system has role-based access (Owner, Admin, Physiotherapist, Patient), push and email notifications, GDPR-compliant data retention (5 years, automatic deletion), and support for email/password, Google, Apple ID, and biometric login.
At the time of last commit, version 1.5.1 was in review on both platforms. It's a full-stack production application — monorepo with a Next.js web app, Capacitor shells for iOS and Android, Playwright E2E tests covering 10 user flows, and Fastlane pipelines for App Store and Google Play deployment.
Stack: Next.js 16 · React 19 · TypeScript · Supabase · Capacitor 8 · Tailwind · shadcn/ui · AWS SES · Turborepo
9. claude-agents — Agent Orchestration & Workflow Guide
🔓 Public · cbroberg · Last active: January 2026
A personal repository from Christian with a structured library of Claude agent definitions — covering the full software development lifecycle from discovery through to security audit.
The agents are organised into phases: Discovery & Planning (codebase analyser, planning specialist, web research), Architecture & Design (enterprise architect, API architect, UI/UX designer, database expert), Implementation (Next.js frontend engineer, DevOps infrastructure), and Quality & Review (code quality, code review, testing/QA, security compliance, documentation).
This is less a product and more a working methodology — a practical answer to the question of how you actually structure multi-agent workflows when building real software. It reflects how we think about AI integration: not as a single "AI button", but as a composable set of specialists with defined responsibilities.
Stack: Markdown · Claude agent definitions (.claude/agents/)
10. svg-logo-generator-cli — SVG Logo Batch Generator
🔒 Private · cbroberg · Last active: February 2026
A Next.js web application for generating SVG logos in bulk from a CSV file containing product names and types. Upload a CSV via drag-and-drop, configure spacing, generate, preview, and download.
A few details worth noting: it includes automatic Cyrillic character detection with font switching (for Bulgarian and other languages), persistent settings between sessions, and optional OAuth authentication via Google or GitHub. It's the kind of focused internal tool that solves a specific, repetitive problem — exactly the type of automation we describe on our AI tools page.
Stack: Next.js · TypeScript · NextAuth.js
What these repositories tell us
Looking across these ten repositories, a few themes stand out.
First, almost everything is built on the same modern stack: Next.js, TypeScript, Tailwind CSS, shadcn/ui, SQLite or Supabase, and fly.io for hosting. We've standardised deliberately, and it pays off in speed and maintainability.
Second, AI is everywhere — but not in a superficial way. Claude isn't bolted on as a chatbot. It's integrated into DNS management, infrastructure planning, content workflows, and development tooling. The MCP pattern specifically keeps appearing: we keep building MCP servers so that AI clients can act on our systems, not just talk about them.
Third, we build our own tools. WHapi instead of Postman. WHop instead of a spreadsheet. A DNS stack instead of a SaaS DNS provider. This isn't stubbornness — it's that bespoke tooling fits our exact workflow, runs on our infrastructure, and often becomes the foundation for something we can offer clients.
If any of this sounds like the kind of thinking you want applied to your own systems, we'd love to hear about it.
Repository data sourced directly from github.com/webhousecode and github.com/cbroberg via the GitHub API. All repository descriptions, README content, and commit messages are real and unedited.