Skip to content
Install free

Enterprise

Keep cross-functional review moving, with a paper trail that holds up.

Decision documents stall in review, lose their history across tools, and shut out the stakeholders who need a say. DraftMesh fixes that, starting with one document owner and no procurement.

Start with the free local appTalk to us

The problem

Every hop between tools costs your review its context.

A decision document passes through six stakeholders and three tools, and by the end nobody can say who approved what, or why the language changed between drafts.

01

Reviews stall on tooling, not substance

A doc lives in Google Docs, gets exported to a wiki, and is circulated over email as a PDF — each hop loses context, and reviewers spend their time locating the latest version instead of reading it.

02

Decisions lose their paper trail

When a policy document has been edited a dozen times across three tools, nobody can reconstruct who changed what, or why — right when an auditor or a new stakeholder asks.

03

Stakeholders who aren't in the tool don't get a voice

A cross-functional reviewer without an account in the tool of record gets a static export and a Slack thread instead of a real seat in the review.

Deployment

Fully local, or managed sync — your call, and you can change it.

DraftMesh doesn't force a deployment model on you before you've proven the workflow matters.

Fully local

Each person runs the free app on their own machine, reading and writing plain files that never leave it. No account, no central service, nothing to provision. This is where a rollout starts: one owner proving the workflow on their own documents. The planned optional usage ping carries no document content, account or device identifier. Its network address is used only in memory to limit abuse and is never stored. Current npm dev and latest builds have no ping target; DRAFTMESH_USAGE_PING=0 keeps it off across a fleet when a target is introduced.

Managed sync

When a team needs cross-device access and multi-person collaboration, the paid tiers add sync with encryption in transit and at rest, backed by the same file-on-disk model. Sync moves your files as they are rather than replacing them with something proprietary.

Identity & access management

Sign-in stays with the identity provider you already run.

From the Team tier up, people sign in through your SAML or OIDC provider, and which domains and people may sign in stays configured there. DraftMesh handles only what each person can open: grants to named people, groups and agents, on one document or a whole workspace.

SSO via SAML or OIDC

Single sign-on through your existing identity provider. No separate DraftMesh password for anyone to manage.

Access granted per document or workspace

Most grants name one document and one person, group or agent, so a mistaken grant exposes only what it names. A whole-workspace grant is the deliberate exception. Four levels: view, comment, suggest, edit.

One org-wide access review

Every grant and every guest link, across every workspace, in one list with a Revoke on each row and a CSV export for your security questionnaire.

A read-only Auditor role

Give compliance a role that reads every document and the whole admin console, including both CSV exports, and can change nothing: no comments, edits, approvals or sharing.

Governance & audit

A paper trail that survives scrutiny — and no lock-in to worry about.

Governance usually gets added after an audit has exposed the gaps. With DraftMesh, portability is there from day one and the audit trail comes with the Team tier — not bolted on afterward.

Attribution

Every change, share and guest session, and every refusal of an identified caller, is tied to the specific person or agent who caused it — no shared logins standing in for a team.

Approvals you can produce on demand

Every sign-off request and approval is its own audit entry, pinned to the version approved. “Everything approved this quarter” is one filtered view and one CSV. Versions and audit entries are kept indefinitely.

Exportability

Documents are plain .md, .html and .json files the entire time, on the free and paid tiers alike — there is no export step because there is nothing proprietary to export from.

No lock-in

Because the underlying files were never anything but portable markdown, leaving DraftMesh is a non-event for the content itself.

Agents under organizational control

Each agent is its own principal, with its own name, credential and grants. Admins can switch every agent off at once or block one person's connector, and no agent can approve, restore a version or share, whatever it holds.

Integrations

Fits the toolchain you already run.

DraftMesh is designed to sit alongside the systems your organization already relies on, not to replace them.

Identity providers

Single sign-on against the identity provider your IT team already administers. Which provider, which domains, and who may authenticate stay configured there, not here.

Cloud storage & file sync

Works alongside the file-sync tools your teams already use to keep folders in step across machines.

Engineering toolchains

Documents stay ordinary .md files in an ordinary folder, so the places your engineers already keep them carry on working exactly as they do today.

AI agent frameworks

A coordinated read/write surface for agent frameworks that need multiple agents working the same markdown without corrupting it.

Rollout

Prove it on one person's documents. Bring the team in when it's earned.

Adoption is bottom-up, not a mandate. One document owner fixes their own drafting and review loop on the free local app; Team brings in named teammates, single sign-on and audit once the workflow has earned its place.

01

One owner, nothing to provision

A document owner installs the free app and drafts with their own agents, with every change attributed and every version kept. No procurement cycle.

02

Prove the workflow

Comments anchored to rendered prose, complete version history, and agent-safe editing solve a real problem before anyone asks IT to get involved.

03

Expand with governance in place

When more teams need in, add sharing with named teammates and managed sync — the same files, now with organization-wide identity, single sign-on and audit, and the guest links outside stakeholders already used on Individual. Enterprise adds the vendor commitments on top.

Pricing

Enterprise is priced per agreement.

We start with your volume, scope and use cases, then propose terms that fit. Everything on Team, free Reviewer seats and the Governance pack as they ship, and named support are included. Talk to us about uptime terms, a DPA and security review. Team, at $50 a seat a month or $500 a seat a year, already includes single sign-on with no minimum — start there if that is all IT needs.

See pricingTalk to us →

Talk to us

Tell us about the review process you're trying to fix.

Email support@draftmesh.com and describe the documents, teams, and stakeholders involved. We'll help you decide whether to start with the free local app, with Team, or with an Enterprise agreement and its dedicated onboarding. Ask for our security overview and administrator guide, written to hand to your security team.

Email support@draftmesh.com

Questions operations leaders ask

Who is DraftMesh built for inside an enterprise?

The person who owns how documents and decisions move through the organization — typically Chief of Staff or Business Operations. It fixes review cycles that stall and decisions that lose their paper trail across teams.

Do we have to deploy this company-wide to get value?

No. Rollout usually starts with one document owner on the free local app, drafting with their own AI agents and full history, with no procurement step. Outside reviewers can join on guest links with Individual. When named teammates need to review and sign off, Team adds sharing, single sign-on and the audit log to the same files.

What does Enterprise cost?

Enterprise is priced per agreement. We start with a conversation about your volume, scope and use cases, then propose terms that fit. An agreement includes everything on Team, agent activity now, Reviewer seats and the Governance pack as they ship, and named support. Talk to us about uptime terms, a DPA and security review. Team itself is $50 a seat a month or $500 a seat a year, with single sign-on included and no minimum.

How does DraftMesh handle identity and access management?

Single sign-on via SAML or OIDC through your existing identity provider. To be exact about today's scope: DraftMesh does not read your directory — there is no SCIM and no directory sync, and groups are managed inside DraftMesh. Access is granted to people, groups and agents — mostly one document at a time, or a whole workspace — at four levels: view, comment, suggest, edit. Every grant in the organization is listed and revocable in one place.

What happens to our documents if we stop using DraftMesh?

Nothing changes about the files themselves. Documents are plain files the whole time — .md, .html, and .json — whether local or synced, so there is no export step and no migration required to leave. You already have everything in a portable format.

Does DraftMesh integrate with our existing identity and storage tools?

DraftMesh is designed to fit an existing toolchain rather than replace it: your identity provider for single sign-on, the file-sync tools where teams already keep their folders, and the AI assistants your people already use, through the DraftMesh CLI and skill or the cloud connector.

Is there a required deployment model?

No. DraftMesh supports a fully local deployment with no document content leaving individual machines, and a managed sync deployment for teams that need cross-device and cross-person collaboration. Most organizations start local and add managed sync only when they need it. A planned weekly usage ping sends only the version and operating system when a user opts in; it is off by default. Current npm dev and latest builds have no ping target and cannot send it. Set DRAFTMESH_USAGE_PING=0 in the daemon environment to keep it off across a fleet, even if a user opts in.

How is document access governed and audited?

Every change, share and guest session, and every refusal of a caller DraftMesh can identify, is attributed to a specific person or agent and retained in an append-only log. Documents remain exportable at any time because they were never anything other than plain files on disk — there is no lock-in to reverse.

Start with one owner. No procurement required.

The free local app is free forever — no account, no upload, no card. Prove the workflow, then decide what to expand.

Install freeCompare plans

Free forever, local, no account