Introducing SpiderPublish: Multi-Tenant CMS for the Edge

After two years of development, we are publicly launching SpiderPublish — a multi-tenant content management system built from the ground up for the AI-native era. This is not another headless CMS. SpiderPublish is a runtime designed to serve hundreds of tenant sites from a single deployment while maintaining complete isolation between them.

Why We Built This

The content management landscape has barely changed in a decade. WordPress powers 43% of the web, yet every site runs its own PHP process, its own MySQL instance, its own plugin stack. That architecture made sense in 2004. It does not scale when your agency manages fifty client sites, each needing custom components, booking flows, and SEO automation.

We wanted a system where spinning up a new tenant takes seconds, not hours. Where components authored once can be deployed across every site with a single API call. Where AI agents can operate the entire publishing pipeline without human babysitting.

The Three-Layer Architecture

STORE — FastAPI + PostgreSQL

Every authored artifact lives in a tenant-isolated PostgreSQL row. Pages, posts, components, forms, settings, templates — all normalized, all versioned. The API is RESTful with 87 atomic endpoints exposed through MCP for agent consumption.

SERVE — Cloudflare Workers

The serving layer is a dispatch worker that routes incoming requests to the correct tenant, fetches the Liquid template from KV, resolves component slugs, and streams the response. Time-to-first-byte is typically under 50ms from the nearest Cloudflare PoP.

MANAGE — Dashboard, MCP, CLI, VSCode

All four management interfaces call the same STORE API. The dashboard provides a visual editor. The MCP server exposes 87 tools for AI agents. The CLI handles batch operations. The VSCode extension enables round-trip editing with live preview.

What Makes It Different

Tenant isolation is not an afterthought — it is the foundation. Every request passes through five security locks before reaching tenant data. Every component renders inside Shadow DOM to prevent CSS leakage. Every deployment goes through a two-phase confirm gate to prevent accidental production pushes.

We believe the future of web publishing is agent-operated. SpiderPublish is the infrastructure that makes that possible without sacrificing security, performance, or design quality.