Hosted Stemma · Pilot program

A hosted DOCX revision API, shaped around your workflow.

We are exploring a hosted version of Stemma for teams that need native Word tracked changes without operating the engine themselves. If you are building document automation, an AI agent, or a Copilot Studio workflow, we would like to understand what production requires.

Apply for the pilot Use the open-source engine

Status: pilot discovery. No generally available hosted service or stable hosted API contract is being offered yet.


The document outcome

Many systems can decide how wording should change. Stemma handles the harder last mile: making that change reviewable inside the Word document.

Apply explicit edits

Turn bounded, structured replacements into attributed native tracked changes.

Compare two DOCX files

Return one redline whose rejected view is the original and accepted view is the revision.

Return a real Word artifact

Produce a .docx reviewers can open, inspect, accept, and reject as usual.

Refuse uncertain targets

Surface missing, duplicated, unsupported, or ambiguous operations instead of guessing.


Where Stemma fits

Your applicationHosted StemmaReviewable DOCX

Explicit revision operations

Your system identifies the old wording, replacement, expected match count, and revision author. Stemma applies the change or returns a specific refusal.

Original and revised documents

Your system sends a base DOCX and a revised DOCX. Stemma constructs a native redline whose accept-all and reject-all readings reproduce those versions.

AI-agent workflows

The agent reasons about the requested wording. Stemma supplies the bounded document operations and produces the final artifact. This separates open-ended language reasoning from revision semantics and file delivery.


Integration interest

Building a Copilot Studio agent?

A hosted Stemma service could sit between your agent and document storage: the agent proposes a bounded change, Stemma applies it as native revisions, and the workflow saves or returns the redlined DOCX.

Copilot Studio or custom agent
              ↓
       revision operations
              ↓
        Hosted Stemma
              ↓
       reviewable .docx

We are particularly interested in workflows involving Copilot Studio, SharePoint, Azure storage, CLM systems, internal agents, and private deployment requirements.


What exists today—and what the pilot explores

Available today

  • Open-source Rust engine
  • Local CLI and MCP server
  • DOCX comparison and explicit worklists
  • Revision inspection and resolution

Pilot questions

  • Stable hosted API shape
  • Authentication, retention, and operational controls
  • Managed versus dedicated deployment
  • Azure and agent-platform integrations

The repository includes a local demonstration HTTP adapter. It has no authentication, authorization, or rate limiting and is not the hosted product described here.


Tell us about the production boundary

Your pre-addressed pilot email asks for:

  • Your product or workflow and approximate monthly document volume
  • The input you expect to send: explicit edits, two DOCX versions, or agent instructions
  • The revision capabilities that matter most
  • Where documents live and how Stemma would need to be deployed
  • Your integration platform and whether implementation help would be useful

Open the pilot brief Sent to hello@stemma.sh.


Frequently asked questions

What is Stemma?

Stemma is an open-source DOCX revision engine for producing native Microsoft Word tracked changes. It runs locally today through its CLI, MCP server, or Rust engine.

Is there a hosted Stemma API?

Not as a generally available service. We are exploring a hosted version with pilot users who have real document-automation workflows.

Does Stemma create real Microsoft Word tracked changes?

Yes. Stemma produces native revisions inside a DOCX, not annotations tied to a proprietary viewer. Reviewers can open the result and accept or reject changes in Word.

Does Microsoft Word need to run on the server?

No. The Stemma engine reads and writes DOCX files directly and does not automate Microsoft Word.

Can Stemma work with an AI agent?

Yes. An agent can decide what should change and use Stemma to inspect the document and apply bounded revision operations. Stemma handles the DOCX artifact and refuses unsupported or ambiguous operations.

Can I use Stemma with Microsoft Copilot Studio?

A hosted Stemma service could provide the document-revision layer behind a Copilot Studio workflow. We are looking for pilot users to shape and test that integration before documenting it as a supported product surface.

Can I run Stemma in our Azure environment?

The open-source engine can be embedded and operated in your own infrastructure. Managed, dedicated, and Azure-hosted deployment requirements are questions we want to explore with pilot users; no private deployment product is promised yet.

Is the hosted API production-ready?

No. This is a pilot invitation, not a generally available API. The open-source engine exists today, while the hosted service, deployment model, and stable API contract are still being shaped.