Why Solo Founders Should Split Personal and Business Websites

Last weekend, software engineer Matthias Meyer launched a new website—matthiasmeyer.tech—not as a subdomain or an extra page, but as a standalone platform dedicated to his open-source projects. Unlike his agency site, which focuses on client work, this domain exists solely to showcase his repositories, engineering insights, and technical decisions without commercial distractions. Built in a single Sunday session, the site now hosts 22 GitHub projects, six explanatory essays, and a 3D interactive graph that visualizes the relationships between them.

The launch wasn’t just about launching. Meyer’s goal was to create a dedicated home for his open-source contributions, which had previously been buried as a subsection on his agency’s website. That approach, he argues, forced trade-offs between technical depth and business relevance—compromises that no longer make sense as his public repositories grow. His new site is leaner, faster, and more focused, reflecting a deliberate separation between his personal brand and his commercial studio.

The Strategic Case for Separate Domains

This isn’t a novel idea. Developers like Guillermo Rauch (rauchg.com) and Lee Robinson (leerob.com) maintain distinct personal sites alongside their company domains (Vercel). The pattern works because their personal voices—often centered on systems thinking, architecture, or technical commentary—serve audiences different from their companies’ commercial goals. Vercel sells deployment platforms; Rauch writes about React internals. Neither dilutes the other.

For Meyer, the split is practical:

• studiomeyer.io serves clients in DACH and Mallorca, offering custom websites and AI systems, with pricing pages, multilingual content, and SEO-optimized copy.
• studiomeyer.academy provides educational content for builders learning AI tools and workflows.
• matthiasmeyer.tech focuses exclusively on his open-source work—repositories, architecture notes, and technical trade-offs—presented in first person without sales pressure.

SEO purists might argue for consolidating everything under one domain to maximize authority. But Meyer counters that the audiences diverge too sharply. A developer downloading local-memory-mcp from npm and landing on a studio sales page isn’t the same visitor booking a custom website project. Two domains with clear cross-links solve the audience problem, even if they accept a minor authority trade-off.

Inside matthiasmeyer.tech: A Closer Look at the Stack

The site isn’t just a portfolio. It’s a living technical artifact, hosting 22 repositories organized into clusters based on function. Eight are considered cornerstones—core tools that others extend or integrate with—while the remaining 14 are auxiliary projects like connectors, security layers, and workflow templates.

Memory and Agent Clusters

• local-memory-mcp: A 13-tool MCP server that provides persistent, local memory for AI assistants like Claude and Cursor using SQLite, FTS5, and a small knowledge graph. Built without cloud dependencies or API keys, it powers the hosted version at memory.studiomeyer.io for users who prefer multi-tenancy.

• mcp-personal-suite: A 49-tool kit for email, calendar, messaging, search, and image generation, designed for "bring-your-own-key" setups with no sign-up required.

• agent-fleet: Orchestrates specialized agents for research, critique, and analysis, running them in parallel for efficiency.

• darwin-agents: Experiments with prompt evolution via A/B testing and judge-based scoring to optimize agent performance over time.

• mcp-studiomeyer-agents: A connector that lets Pro-tier customers of StudioMeyer Agents access audit data and adjust agent configurations directly from their local AI tools.

Security and Media Clusters

• ai-shield: A zero-dependency LLM security toolkit that detects prompt injection, masks PII, tracks costs, and enforces tool policies—all with sub-25ms scan times across frameworks.

• ai-shield-py: A two-day-old Python port designed for FastAPI and LangChain projects, maintaining identical defenses with native framework hooks.

• mcp-armor: A Rust-based sidecar that validates signed manifests for any MCP server, defending against supply-chain CVEs (including those documented in OX Security’s April advisory) with sub-5ms p99 overhead.

• mcp-server-attestation: A TypeScript companion for teams that prefer Node.js environments, ensuring manifest validation without Rust dependencies.

• mcp-video: Wraps FFmpeg and Playwright behind eight tools for recording, editing, captioning, text-to-speech, and smart screenshots—an unexpected but highly practical addition for marketing automation.

Workflow and Factory Clusters

• n8n-templates: Delivers hardened workflows with cross-session memory, voice agents, customer support bots, and multi-provider LLM routing—ready for production use.

• n8n-nodes-studiomeyer-memory: Bridges those templates to Meyer’s memory backend, enabling persistent state across workflow sessions.

• n8n-workflows: A memoryless variant for teams that don’t require cross-session state, focusing on deterministic, repeatable processes.

• mcp-protocol-conformance: A test harness that validates JSON-RPC 2.0 compliance, OAuth 2.1 PKCE flows, tool schemas, and capability declarations across MCP spec versions—critical for marketplace submissions where discipline outpaces the spec.

The site also integrates build-time GitHub stats to keep metrics fresh and uses a 3D force-directed graph as its hero, where cyan particles represent repositories and edges visualize their relationships. This visual layer wasn’t just decorative—it became a functional index, letting visitors explore the codebase’s architecture at a glance.

What This Means for Solo Founders

Meyer’s experiment highlights a growing trend among solo operators: the need to balance personal branding with commercial clarity. By isolating his open-source work on a dedicated domain, he’s created a space where technical depth isn’t overshadowed by sales language. The approach also future-proofs his public contributions, ensuring they remain accessible and explorable without friction.

For other solo founders, the lesson is clear: if your public work spans multiple audiences—clients, learners, and contributors—consider separating them into distinct surfaces. It’s not about SEO authority; it’s about clarity of intent. As Meyer’s site demonstrates, sometimes the cleanest architecture isn’t just in the code—it’s in the domains themselves.