docs: align studio open-core positioning

Author: Contentrain

AGENTS.md

@@ -1,6 +1,6 @@
 # Contentrain Studio
 
-AGPL-3.0 licensed cloud product for team content management over Git.
+Open-core product for team content management over Git. This repository contains the AGPL-3.0 core.
 Conversation-first CMS — chat with AI agent to manage structured content.
 
 ## Stack
@@ -17,7 +17,7 @@ Conversation-first CMS — chat with AI agent to manage structured content.
 
 ### Provider/Adapter Pattern — CRITICAL
 
-Studio is deployment-agnostic. There is no "hosted SaaS" — the product is self-hosted / on-premise first.
+Studio is deployment-flexible. The AGPL core is self-hostable, and the same product model can also be operated as a managed Pro/Enterprise service.
 All external services are accessed **only** through provider interfaces. No implementation detail ever leaks into components, pages, composables, or server routes.
 
 Provider interfaces live in `server/providers/`:
@@ -63,7 +63,7 @@ User → Workspace (billing entity) → Project (connected repo)
 - GitHub App installation lives on workspace (not project)
 
 ### Route Structure
-This is an AGPL product — no marketing pages. All routes are authenticated:
+This repository is the AGPL core product surface — no marketing pages. All routes are authenticated:
 ```
 /auth/login ............... Auth (public)
 /auth/callback ............ Auth callback (public)

CLAUDE.md

@@ -1,6 +1,6 @@
 # Contentrain Studio
 
-AGPL-3.0 licensed cloud product for team content management over Git.
+Open-core product for team content management over Git. This repository contains the AGPL-3.0 core.
 Conversation-first CMS — chat with AI agent to manage structured content.
 
 ## Stack
@@ -17,7 +17,7 @@ Conversation-first CMS — chat with AI agent to manage structured content.
 
 ### Provider/Adapter Pattern — CRITICAL
 
-Studio is deployment-agnostic. There is no "hosted SaaS" — the product is self-hosted / on-premise first.
+Studio is deployment-flexible. The AGPL core is self-hostable, and the same product model can also be operated as a managed Pro/Enterprise service.
 All external services are accessed **only** through provider interfaces. No implementation detail ever leaks into components, pages, composables, or server routes.
 
 Provider interfaces live in `server/providers/`:
@@ -63,7 +63,7 @@ User → Workspace (billing entity) → Project (connected repo)
 - GitHub App installation lives on workspace (not project)
 
 ### Route Structure
-This is an AGPL product — no marketing pages. All routes are authenticated:
+This repository is the AGPL core product surface — no marketing pages. All routes are authenticated:
 ```
 /auth/login ............... Auth (public)
 /auth/callback ............ Auth callback (public)

CONTRIBUTING.md

@@ -79,7 +79,7 @@ The most important project rules are architectural, not stylistic.
 
 ### Provider Pattern
 
-Contentrain Studio is deployment-agnostic and self-hosted-first. External services are accessed only through provider interfaces in `server/providers/`.
+Contentrain Studio is deployment-flexible. The AGPL core can be self-hosted, and paid plans can also be operated as managed services. External services are accessed only through provider interfaces in `server/providers/`.
 
 Do not:
 

README.md

@@ -16,7 +16,7 @@
 
 ## What Contentrain Studio Is
 
-Contentrain Studio is a self-hosted, Git-backed content operations platform built with [Nuxt 4](https://nuxt.com/). It is designed for teams who want structured content, reviewable Git workflows, and an AI operator without giving up repository ownership.
+Contentrain Studio is an open-core, Git-backed content operations platform built with [Nuxt 4](https://nuxt.com/). Teams can self-host the AGPL core or use a managed Pro/Enterprise offering while keeping Git as the source of truth.
 
 The product model is:
 
@@ -26,7 +26,7 @@ The product model is:
 - changes become branches, commits, diffs, and merges
 - delivery can happen through media, CDN, and API surfaces
 
-This repository contains the AGPL core. Proprietary enterprise implementations live in [`ee/`](ee/) under a separate license.
+This repository contains the AGPL core. Proprietary enterprise implementations live in [`ee/`](ee/) under a separate license. Managed Pro/Enterprise deployments can be operated on top of the same product model.
 
 ## Why It Exists
 
@@ -36,7 +36,23 @@ Traditional CMS products hide content workflows behind opaque databases and admi
 - schema validation protects structured content quality
 - AI is bounded by tools and permissions, not used as an uncontrolled shell
 - workspaces and projects map cleanly to team and repository boundaries
-- self-hosting remains the first-class deployment model
+- self-hosting remains a supported trust path, and managed operation is also available
+
+## Relationship to Contentrain AI
+
+Studio shares the same `.contentrain/` contract with the MIT package surface in the `contentrain-ai` repository. Developers usually enter the ecosystem through local-first package workflows, then move into Studio when review, roles, and delivery become operational needs.
+
+| AI surface | Primary job | Studio bridge | Docs |
+| --- | --- | --- | --- |
+| `@contentrain/mcp` | Deterministic local content operations and normalize | Studio applies the same content contract through authenticated review and delivery workflows | [MCP Tools](https://ai.contentrain.io/packages/mcp) |
+| `contentrain` CLI | `init`, `serve`, `generate`, `diff`, `validate` | Studio takes over when teams need a web surface, project management, and approval | [CLI](https://ai.contentrain.io/packages/cli) |
+| `@contentrain/rules` | Shared quality and schema standards | Studio chat, review, and validation should stay aligned with the same rules | [Rules & Skills](https://ai.contentrain.io/packages/rules) |
+| `@contentrain/skills` | Agent playbooks and workflow hints | Studio mirrors these workflows in onboarding, chat-led operations, and handoffs | [Rules & Skills](https://ai.contentrain.io/packages/rules) |
+| `@contentrain/query` | Local typed consumption and CDN client transport | Studio extends the same content into remote delivery and API-key-based CDN access | [Query SDK](https://ai.contentrain.io/packages/sdk) |
+
+Typical path:
+
+`contentrain init` → normalize hardcoded content → review in Studio → invite teammates → deliver through CDN/API when needed
 
 ## Product Surface
 

docs/DEPLOYMENT.md

@@ -1,6 +1,6 @@
 # Deployment Guide
 
-Contentrain Studio is designed for self-hosted deployment. The product is a single Nuxt/Nitro application with external dependencies for auth/data, GitHub integration, optional billing, optional object storage, and optional Redis.
+Contentrain Studio supports self-hosting of the AGPL core and managed operation of paid plans. The product is a single Nuxt/Nitro application with external dependencies for auth/data, GitHub integration, optional billing, optional object storage, and optional Redis. This guide focuses on deploying it yourself.
 
 ## Deployment Shapes
 
@@ -23,9 +23,9 @@ Optional but recommended:
 
 - Redis for distributed rate limiting
 - Resend or compatible app-email provider
-- Anthropic API key for Studio-hosted AI
+- Anthropic API key for the operator-managed AI surface
 - Cloudflare R2 for CDN/media delivery
-- Stripe for hosted billing
+- Stripe for billing when commercial plans are enabled
 
 ## Production Checklist
 
@@ -74,7 +74,7 @@ If billing is not enabled:
 
 - Leave Stripe keys unset
 - Leave `NUXT_PUBLIC_BILLING_ENABLED` unset
-- Studio will operate in self-host/no-billing mode
+- Studio will operate in no-billing mode
 
 ### CDN / Media
 

docs/DOCKER.md

@@ -1,6 +1,6 @@
 # Docker Guide
 
-This repository ships with a production Dockerfile for self-hosted deployments.
+This repository ships with a production Dockerfile for self-hosted or operator-managed deployments.
 
 ## What the Docker Image Contains
 

docs/RELEASING.md

@@ -1,6 +1,6 @@
 # Releasing Guide
 
-Contentrain Studio ships as a self-hosted application image, not as an npm package.
+Contentrain Studio ships as an application image used for self-hosted and managed deployments, not as an npm package.
 
 The release source of truth is:
 

docs/SELF_HOSTING.md

@@ -1,6 +1,6 @@
 # Self-Hosting Guide
 
-Contentrain Studio is self-hosted-first. There is no requirement to run it as a managed SaaS.
+Contentrain Studio supports self-hosting of the AGPL core. This guide covers the self-managed deployment path; managed Pro/Enterprise operation may also be available separately.
 
 This guide describes the practical model for operating Studio in your own environment.
 
@@ -48,7 +48,7 @@ Contentrain Studio (Nuxt/Nitro)
 
 ### Minimal Core Mode
 
-Use this when you want the AGPL core without premium operational surfaces.
+Use this when you want to run the AGPL core yourself without premium operational surfaces.
 
 Recommended config: