Hosting model

WiseWig is an open-source, developer-first CMS framework. It should be useful when self-hosted and straightforward to deploy through a hosting adapter; a managed deployment is optional, not a requirement for using the framework.

Framework and adapters

The framework owns the portable contracts: typed components, page documents, theme manifests, editor metadata, command semantics, permissions, plugins, and MCP tool declarations. Themes target the Astro-first renderer in v1 and should not need to know whether a site is self-hosted or managed.

Hosting packages implement the operational boundary: request handling, domain resolution, identity integration, persistence, assets, cache invalidation, queues, and observability. @wise-wig/hosting-cloudflare is the reference and first production adapter. Other adapters can implement the runtime interfaces without changing a theme’s component/content contract.

The open-source project must have a documented local-development path, deployable reference configuration, versioned migrations, and no hidden dependency on WiseWig Cloud for normal editing or publishing.

Managed deployment

The managed deployment operates the Cloudflare-first adapter and can handle upgrades, domains, operational security, backups, and managed identity.

It must use the same public framework, theme manifest, plugin contracts, and command layer as self-hosting. It must not create a separate content model or a proprietary theme runtime.

Theme supply

Theme packages may be supplied through different development workflows:

1. Starter themes — maintained themes for common small-business needs, usable by any deployment.
2. Developer themes — private or shared packages installed through a versioned release workflow with compatibility and migration metadata.

Themes remain developer-owned. Customers can edit only the schema, variants, structural permissions, and appearance tokens that the theme intentionally exposes. A theme switch always uses the slot migration review flow; it never silently converts arbitrary layout or content.

Contract boundaries

• Framework permissions, content validation, plugin capabilities, audit semantics, and MCP public/private isolation are required in both managed and self-hosted deployments.
• A content editor cannot gain authority over a developer theme merely by being able to edit its content.
• Exporting structured site content and assets must remain possible across deployments.

Near-term implications

• Keep @wise-wig/runtime hosting-neutral and treat Cloudflare bindings as adapter implementation details.
• Define a versioned theme package/release format.
• Build the Cloudflare adapter as a complete reference deployment, including documented local and production configuration.
• Design Studio so agency/partner theme management is distinct from customer content editing.