Get help with Contentrain
Email support@contentrain.io, or open an issue in the GitHub repository of the product you use. The docs cover setup, configuration and the API.
Questions about your account or an order
Write to support@contentrain.io about your account, billing, a Studio project or a Migrate order. Say which project or order you mean, what you did, and what you expected to happen.
GitHub
Bugs and feature requests
The AI packages, Studio and the Bridge plugin are public repositories on GitHub. Open an issue in the one you use, with the version and the steps that show the problem. The cards below link each one.
- AI packages: github.com/Contentrain/ai
- Studio: github.com/Contentrain/studio
- Bridge: github.com/Contentrain/wordpress-bridge
Security
Security issues go to security@contentrain.io
Do not open a public issue for a vulnerability. Email security@contentrain.io instead; the security page describes how disclosure works.
Next paths
Continue through the content system
Issues: AI packages
MCP server, CLI, query SDK, rules and skills.
Issues: Studio
The Studio app and its self-hosted deployment.
Issues: Bridge
The free WordPress plugin that exports a site.
AI package docs
Packages, MCP tools and framework guides.
Studio docs
Studio, MCP Connector, API and self-hosting.
Security
How to report a vulnerability privately.
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.