The team operating surface for governed content in Git
Studio gives teams structured editing, chat-assisted content work, roles, and review over Git-backed projects. Media, CDN, forms, webhooks, APIs, and remote MCP appear when the edition, plan, provider, and deployment support them.
Operating model
A team surface over Git, not a separate content database
Studio operates structured content through a content engine that validates, serializes, branches, commits, and reviews files. The repository remains the audit layer while the app gives non-developers a usable workspace.
- Workspace and project management
- Model-aware editing for collections, documents, dictionaries, and singletons
- Repositories connected through the Contentrain GitHub App
AI workflow
Conversation-first content operations
Studio chat is not a generic prompt box. The server builds project and permission context, then filters the operations available to the user. Conversation history is part of Studio; external Conversation API access is available on eligible editions and plans.
- Tool-driven, project-aware content operations
- Permission-filtered operations for each user
- Conversation history and eligible external API access
Governance
Roles, review, and branch health for teams
Studio adds workspace owner and admin controls plus project editor, reviewer, and viewer roles. Model-scoped access is available where the plan supports it, and branch health helps reviewers assess changes before merge.
- Workspace owner, admin, and member access
- Project editor, reviewer, and viewer roles
- Model-scoped constraints on eligible plans
Delivery
Add media and delivery operations when your deployment supports them
Studio can add asset management, media variants, CDN delivery, forms, submissions, and outbound webhooks to the same project workflow. These capabilities are conditional: availability depends on the Studio edition, workspace plan, provider facets, storage, and project configuration.
- Media library and upload on eligible plans with storage configured
- CDN delivery on eligible plans and enabled projects
- Forms and webhooks according to plan and edition
Review policy
Decide which changes need a human, in a file in your repo
On the review workflow, agent writes stay on their own branch until someone approves them. An approval policy file in the repository (.contentrain/approval-policies.json) sets which kinds of change can merge on their own and how many approvals the rest need. Without a file, every change above read-only needs one review. An agent can never approve its own work.
- Policy as a versioned file, not a hidden setting
- Risk classes from content edits to schema changes and deploys
- A new commit invalidates earlier approvals
- Receipts show what ran under each approval
{
"version": 1,
"rules": [
{ "risk": "low_risk_content",
"gate": "change",
"mode": "single" }
]
}
# risk classes: read_only, …,
# destructive_schema, deployment
Publishing
Deploy hooks and scheduled publishing
Paste a Netlify, Vercel, Cloudflare Pages or generic build hook, and Studio starts your build when content is published, when a scheduled time arrives, or when an owner clicks Deploy now. Entries can carry a publish time and an expiry time, set through the API or by an agent; Studio fires each boundary on time, and a missed one fires late rather than never.
- Netlify, Vercel, Cloudflare Pages or any build hook URL
- Builds on publish, on schedule, or by hand
- The hook URL is stored encrypted
- On the review workflow, a manual deploy waits for an approved release
Host
Netlify build hook
Vercel deploy hook
Cloudflare Pages deploy hook
Any POST endpoint
✓ Deploy when content is published
✓ Deploy at scheduled publish
/ expiry
Deploy now
# build hook URL stored encrypted
Comments
Comments on your static site, moderated in Studio
Turn comments on per model and your site reads and posts them through a public API. New comments wait in a moderation queue by default: approve, reject, mark as spam or reply, one by one or in bulk. Captcha, a honeypot and per-IP rate limits keep bots out, and owners and admins can get an email when a comment arrives. Comments from WordPress can be imported.
- Public read and post API with nested threads
- Moderation queue with bulk actions and replies
- Captcha, honeypot and rate limits
- WordPress comment import
Require Approval
# new comments stay hidden until
# a moderator approves them
Approve · Reject · Spam
Reply as moderator
Import from WordPress
Public endpoint (read + submit):
/api/comments/v1/…/{entryId}
Forms
Form submissions without a form backend
Turn a collection model into a form: your site posts to a public endpoint, and submissions land in Studio for review. Approving one turns it into a draft entry. Owners and admins can get an email for each submission. Captcha, a honeypot, rate limits and input sanitizing are built in.
- Public form config and submit API
- Review before anything becomes content
- Email notifications to owners and admins
Form Enabled
Exposed Fields
Honeypot Field · CAPTCHA
Rate Limit (per IP/min)
Email Notifications
GET /api/forms/v1/…/config
POST /api/forms/v1/…/submit
# Approve → a draft entry
Webhooks
Signed webhooks for every content event
Studio sends signed webhooks when content is saved or deleted, a branch is merged or rejected, a CDN build completes, media is uploaded, a form or comment arrives, a deploy hook fires, or a schedule boundary passes. Each delivery is signed with HMAC-SHA256, failed deliveries are retried with backoff, and the delivery log shows every attempt. Outbound webhooks are part of managed Studio and the Enterprise edition, not the Community edition.
- 13 event types
- HMAC-SHA256 signatures
- Retries and a delivery log
AI keys
Choose provider keys or managed AI usage where available
Studio supports deployment-specific AI key strategies and metered usage. Managed Studio keys, bring-your-own-key options, billing, and overages vary by edition and plan, so teams can choose the operating model their deployment supports.
- Deployment-aware AI key configuration
- Plan usage and overage visibility
- Billing controls for managed workspaces
Bring your own AI key
Use a Studio-hosted key or connect your own Anthropic account — your usage, your control.
Deployment choice
Start locally, add team operations when needed
Developers can begin with the MIT packages. Teams can then choose managed Studio or self-managed Community and Enterprise paths based on collaboration, infrastructure, support, and licensed-feature requirements, while content remains in Git.
- MIT packages for local developer workflows
- Managed Studio for eligible team operations
- Community and Enterprise paths for self-managed deployment
Pro
Team collaboration, higher limits, BYOA, and the Conversation API.
Common questions
Is Studio required for Contentrain projects?
No. Developers can initialize, validate, normalize, generate, and use the local MCP server with the MIT packages. Add Studio when content becomes a shared team workflow.
When should a team add Studio?
Add Studio when editors and reviewers need structured views, roles, branch review, and a shared workspace. Managed media, delivery, APIs, and remote MCP depend on the selected plan and deployment capabilities.
Does Studio bypass Git?
No. Studio is designed around Git-backed content files, commits, branches, diffs, validation, and the project's configured merge workflow.
Can Studio publish on a schedule?
Yes. An entry can carry a publish time and an expiry time, set through the Studio API or by an agent. Studio checks every minute and serves the entry only inside that window. When a boundary passes, it rebuilds the CDN content if CDN delivery is on and can start your deploy hook. The editor shows whether an entry is scheduled or expired.
Does Studio host my site?
No. Studio connects to your repository and builds through hooks and APIs. Your site stays a static or framework site on your own host; Studio only starts the build through the deploy hook you configure.
Next paths
Continue through the content system
Studio adoption playbook
Add Studio for team review and roles, with media, delivery, and enterprise options where enabled.
Content editor workflow playbook
Give editors Studio workflows without losing Git review.
Content teams solution
How non-developers operate content with review.
Pricing
Compare Studio plans, included usage, and deployment options.
Start local. Scale to Studio.
Build a governed content layer before content becomes product debt.
Start locally with the MIT packages. Add Studio when teams need review, roles, structured editing, managed delivery, or deployment control.