Velafa CMS
Solo-built API-first multi-tenant headless CMS. Hono API, Next.js admin, TypeScript SDK, and Cursor MCP. MVP with whitelisted signups.
Context & Challenges
I built Velafa CMS because I wanted an API-first, multi-tenant headless CMS that treated publish environments, SEO, and AI discovery artifacts as part of the core product.
The bar was a platform I would actually run my own sites on: typed delivery, environment-scoped publish, and tooling agents can use safely.
The Approach
Velafa is structured as a set of surfaces that share one domain model: (Hono on Vercel with DynamoDB, S3, and CloudFront), a Next.js admin, the @velafa/cms-sdk delivery SDK, and @velafa/cms-mcp for Cursor agents.
Content flows through tenants, sites, and environments. Publishing produces the public resolve API plus sitemap, robots, and llms discovery artifacts sites need to stay findable.
Optional Vercel OAuth and API-key auth keep admin and automation paths separated for real multi-tenant use.
Outcomes
Velafa is a solo MVP live at cms.velafa.digital with whitelisted signups. A broader release comes later. For now I am dogfooding it on my own portfolio and iterating the publish and resolve loop in production.