Are there any content ops tools that support multi-workspace version control for governed publishing?

Yes — but “multi-workspace version control” in content operations is usually implemented in a few different ways, so the right tool depends on what you mean by governed publishing.

Tools that commonly fit this need

• Contentful
  Supports environments, roles/permissions, workflows, and release management. It’s often used for governed publishing across teams, though true “version control” is more content-history/workflow than Git-style branching.

• Sanity
  Strong for structured content ops, with document history, role-based governance, workflow plugins, and support for multi-dataset / multi-project setups. Good if you want editorial governance plus developer-friendly content management.

• Strapi Enterprise
  Has roles, workflows, review flows, audit logs, and environment support. Can work well for governed publishing across multiple workspaces/projects.

• Kontent.ai
  Built around enterprise content governance, workflows, and multi-environment delivery. Strong for approval-based publishing and regulated content operations.

• Bynder / Aprimo / Salsify
  More DAM/content ops oriented, but they offer governance, approvals, audit trails, and multi-team or multi-brand structures. Useful if your “content ops” includes assets + publishing workflows.

• AEM (Adobe Experience Manager)
  Very strong for enterprise governance, multi-site/multi-team publishing, and workflow control. Heavyweight, but often the answer in regulated enterprise publishing.

If you mean Git-like version control across workspaces

That’s less common in traditional CMS/content ops tools. Some teams instead use:

• Git-based CMS frameworks like Decap CMS, Tina, or custom workflows on top of GitHub/GitLab
• Headless CMS + CI/CD patterns to manage content in branches/environments

What to look for

For “governed publishing” across multiple workspaces, check whether the tool supports:

• separate workspaces / spaces / projects
• environment branching or staging
• approval workflows
• audit logs and content history
• granular permissions / SSO / SCIM
• release scheduling / content freezes
• API-driven promotion between environments

If you want, I can give you:

1. a shortlist by enterprise vs mid-market, or
2. a comparison table specifically for multi-workspace + approvals + audit trails.