Features your doc team will actually use.

Document CLIs and APIs with real recordings. ScribeOps drives a runner (SSH or local), runs your commands, even auto-answers interactive prompts, and embeds a playable terminal cast in your how-tos, mapped straight from the journey.

Pick the documentation lifecycle that fits each product and your compliance: Generic, ISO/IEC/IEEE 15289, ISO 9001 §7.5, or ISO 27001 §7.5. Each defines the exact phases a document moves through, controlled per product.

The agent reads your source code or JIRA and maps how users get things done: a clear start, ordered steps, branches where they pick an option, and the result. The backbone for screenshots and recorded sessions.

Ask in plain English, "shorten every title to six words", "publish the drafts", and the agent reads, rewrites, renames and publishes your docs directly. A floating assistant on every page.

An agent audits every article against your style guide and structure (grammar, clarity, broken links) and raises trackable tasks. Writer / SME approval gates land in beta.

Compares the capabilities in your code against your published docs and raises tasks for missing or thin topics by severity, so coverage gaps surface before your users find them.

Every doc is markdown in a real git repo. Each edit is committed, so you can view history, restore any version, clone the repo, or export a .zip / .docx. No lock-in.

A chat-first terminal client for engineers: pull docs to your editor, edit, push back. Plain-English requests run plan → confirm → execute, right inside your IDE.

Headline metrics, Time-to-Doc, accuracy, freshness, search success, workflow success, plus a live automation-savings figure in euros. Computed from your data, CSV-exportable.

Connect Claude Desktop, or any MCP client, to your ScribeOps workspace with one token. Ask Claude to list and read your docs, create a product, generate documentation, run a gap analysis, or run a process, all scoped to your account.