# How Waldium made a blog platform work for humans and AI alike

DevFeed: [How Waldium made a blog platform work for humans and AI alike](<https://devfeed.tech/articles/how-waldium-made-a-blog-platform-work-for-humans-and-ai-alike-754.md>)

Original publisher: [Read original article](<https://vercel.com/blog/how-waldium-made-a-blog-platform-work-for-humans-and-ai-alike>)

Author: Nic Vargus

Published: 2026-04-01T05:00:00Z

Content type: article

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Content Management System](<https://devfeed.tech/topics/cms.md>), [Model Context Protocol (MCP)](<https://devfeed.tech/topics/model-context-protocol-mcp.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Code](<https://devfeed.tech/topics/code.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blog](<https://devfeed.tech/tags/blog.md>), [developer](<https://devfeed.tech/tags/developer.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

Waldium built an agentic CMS that automates content research and creation while giving each customer blog its own MCP server endpoint. The platform serves more than 500 customer blogs from a single Next.js deployment on Vercel, enabling AI agents to search and interact with blog content inside developer workflows.

## Source excerpt

Waldium is a two-person, YC-backed startup that built an agentic CMS for businesses. Co-founded by Amrutha Gujjar and CTO Shivam Singhal, the platform automates content research and creation, and gives every customer blog its own MCP server endpoint so AI agents can query it directly. Today, it all runs from a single Next.js deployment on Vercel. Amrutha spent years building software where the infrastructure kept getting in the way. "I was never stuck on the part I was excited to build," she says. "It was always the infrastructure friction around it." That frustration became a design principle for Waldium. The infrastructure needed to disappear so the product could stay focused on what made it interesting. Waldium on Vercel 500+ customer blogs served from a single Vercel deployment New customers get MCP endpoints live in under 5 minutes AI query response times consistently under 50ms globally 45% lower infrastructure cost vs. per-customer deployment model One customer generated 1,000+ posts in a single month; research time cut from weeks to hours When agents became part of the audience Waldium started the way most content platforms do, building blogs for humans to read. But something Amrutha kept noticing was quietly changing who, and what, showed up to read them. Developers and technical teams were pulling blog content into their coding environments, into Claude Desktop, into ChatGPT, using it as live context in the tools where they actually worked. The browser tab was still part of the picture, but it wasn't the whole story anymore. Content that couldn't travel into those environments was leaving reach on the table. That insight pointed Waldium toward MCP (Model Context Protocol) as the right primitive. If every customer blog had its own MCP server endpoint, an AI assistant could search, retrieve, and interact with that content directly, without anyone leaving their workflow. A developer could ask an agent to find a specific code snippet across an entire blog arch