Vale CMS

Build, test, edit, and ship your entire Vale project.

Vale CMS is not a YAML textarea with a save button. It is a hosted control plane for the whole Vale project: config, rules, vocabularies, dictionaries, filters, views, templates, tests, previews, and Git publishing, all grounded in the engine your team already runs in editors and CI.

Open Vale CMS Read the Vale docs
product-docs · main Save
RepeatedWord.yml
Form Raw
1 # Flags an immediately repeated word. 2 extends: repetition 3 message: "'%s' is repeated." 4 level: error 5 alpha: true 6 tokens: 7 - '[^\s]+'
compiled \b([^\s]+)\s+\1\b
Test · onboarding.md
Welcome new writers to the the team. Please utilise a clear voice.
error 'the' is repeated.
suggestion Prefer 'use'.
engine ready 14 assets 2 alerts saved · main

The real Vale engine, while you work.

Build rules with confidence because the CMS validates what Vale will actually load, compile, and report.

Why it exists

A CMS for the system behind your writing standards.

A mature Vale setup is an editorial system: rule logic, exceptions, package dependencies, scopes, ignore patterns, test cases, and publishing conventions. Vale CMS gives that system a purpose-built interface without hiding the files that keep Vale portable.

Author the full project

Config, rules, actions, vocabularies, dictionaries, filters, views, and output templates all get first-class editing.

Test against the real engine

Lint samples, inspect compiled regex, validate references, and catch broken rules before they reach CI.

Ship reviewable changes

Open a repository, commit to a branch, or propose a pull request while Git remains the source of truth.

Workflow

From idea to reviewed style-guide change.

The product is built around the work that usually slows Vale adoption: translating guidance into checks, proving those checks against real examples, and publishing the result through the same Git workflow as the docs or content it protects.

  • Use guided forms for every Vale check type, then drop into raw YAML when you need exact control.
  • Autocomplete real .vale.ini keys, rule fields, styles, scopes, vocabularies, and package paths.
  • Preview exactly what a rule catches with the same output shape your CLI, editor, or docs pipeline sees.
  • Keep tests, dictionaries, templates, filters, and config changes together instead of editing scattered files by hand.

Privacy and security

Designed for private repositories and real team workflows.

Vale CMS needs to open projects and write changes, but it is intentionally shaped around short-lived broker calls and browser-held credentials. Git remains the system of record; Vale CMS supplies the editing and validation layer.

Repository content stays in your source of truth

Vale CMS reads from GitHub, GitLab, local folders, samples, or zip files. The hosted app does not persist your style-guide content.

Git tokens are not stored on Vale CMS servers

Provider tokens live in your browser and are forwarded per request to the SCM broker. The broker calls the host API and stores nothing.

Scoped provider flows

GitHub uses a GitHub App with installation-scoped repository access. GitLab uses OAuth Authorization Code with PKCE.

AI is optional and bring-your-own-key

Assistant requests go from your browser to the provider you choose. Your AI key and chat transcript do not touch Vale CMS servers.

Powerful without becoming proprietary lock-in.

Vale CMS is commercial software, but it is designed around the same open, file-based model that makes Vale useful everywhere. Your project remains a normal Vale project: readable, reviewable, portable, and usable by the CLI, GitHub Action, editor integrations, and MCP.

Access

Try it free.

Explore the sample project for free. Pro starts at $12/month with a 30-day trial, and team plans are available for shared style-guide work.

Launch Vale CMS