SveltyCMS connects to the hosted marketplace at marketplace.sveltycms.com for plugin discovery, license verification, and one-click installation. Combined with the AI Widget Scaffolder, this provides two complementary paths for extending the CMS.

Architecture

Marketplace API (marketplace.sveltycms.com)

Local CMS license gates

Which plugins/widgets call checkExtensionLicense and how fail-open works is documented in:

License Gate Inventory

Two Paths to Extend

The marketplace hosts community-built plugins. The scaffolder generates custom code on demand. Together they cover the full spectrum from “I need a Stripe integration” to “I need a very specific testimonial carousel.”

Marketplace Client API

List plugins

import { marketplace } from "@src/services/intelligence/marketplace-client";

// Browse all plugins
const { plugins, total } = await marketplace.list({
  type: "widget",
  limit: 10,
});

// Search
const results = await marketplace.search("seo");

// Filter by license tier
const freePlugins = await marketplace.list({ license: "free" });

Install a plugin

import { installPlugin } from "@src/services/intelligence/marketplace-client";

const plugin = await installPlugin("svelty-stripe");
// → Downloads files, creates src/plugins/stripe/, writes all files

License management

import { setLicenseKey } from "@src/services/intelligence/marketplace-client";

// Set your pro/enterprise license
setLicenseKey("svl_xxxxxxxxxxxxxxxxxxxxxxxx");

// Check if license allows a specific plugin
const { valid, tier } = await marketplace.checkLicense("enterprise-audit");

Check for updates

// Pass your installed plugins
const updates = await marketplace.checkUpdates([
  { id: "redirect-manager", version: "1.0.0" },
  { id: "sitemap", version: "1.0.0" },
]);

// → [{ id: "sitemap", version: "1.1.0", ... }]

Extension Types

License Tiers

Extension Pricing Overview

Performance

The marketplace client is offline-resilient: if marketplace.sveltycms.com is unreachable, it serves cached listings and degrades gracefully.

Phased Migration & Documentation Federation

As extensions migrate from the monorepo to marketplace.sveltycms.com, their co-located .mdx documentation leaves the local source tree. This creates a challenge for docs.sveltycms.com, which generates llms-full.txt and subset variants (llms-api.txt, llms-dev.txt, llms-guides.txt) by scanning local {name}/{name}.mdx files.

Migration Phases

Doc Stub Pattern

During migration, each removed extension leaves a lightweight .mdx stub in its original path that redirects readers to the marketplace:

---
title: "Remote Video Widget"
redirect: "https://marketplace.sveltycms.com/packages/remote-video"
---

# Remote Video Widget

This widget has moved to the [SveltyCMS Marketplace](https://marketplace.sveltycms.com/packages/remote-video).

The docs pipeline detects redirect frontmatter and fetches the full documentation from the marketplace API.

Federation Architecture

Marketplace API — Documentation Endpoint

The marketplace package schema includes a documentation field for serving the full .mdx content:

This field is exposed via GET /api/packages/{slug} and is ingested at build time by the docs pipeline. Cached with a 30-minute TTL, matching the marketplace client cache duration.

llms-full.txt Coverage Guarantee

The federation layer ensures 0% documentation loss during migration — every extension, whether local or marketplace-hosted, appears in llms-full.txt for AI agents and RAG pipelines.

Related

• AI Integration & Hosted Knowledge — AI widget scaffolder and behavioral learning
• Behavioral Learning Engine — Learns from usage patterns
• Plugin Architecture — Building plugins for SveltyCMS
• Widget Development — Building custom widgets
• Project Roadmap — Migration timeline and milestones