Mode 3 — DocMark cloud
Zero install. Our managed SaaS on Azure, with DocMark-managed AI included — sign in and get verified, on-brand deliverables.
The promise
Nothing to install, nothing to host. Sign in at app.docmark.md (access is by invitation today), submit a prompt and your files, and get back verified, on-brand deliverables — with the AI managed by DocMark on our Azure infrastructure. This is the fastest way to start.
Live today: branded decks, documents (DOCX), charts & dashboards (XLSX), video, newsletters, and brochures (PDF). Sign in, submit your prompt and files, download the result, edit and regenerate or delete it, and get a completion email when it’s ready. Per-client branding is applied by construction.
Zero-egress, the cloud meaning
In this mode, zero-egress means something specific — and different from on-prem. It does not mean “no internet”; this is a cloud service. It means no PII reaches the execution plane: your identity stays in the control plane, and the render worker that builds your deck never sees who you are. (On-prem uses the phrase to mean nothing leaves the building — both are real, and they are not the same thing. The comparison lays it out.)
How it works
The same pipeline discipline as the other modes runs on our infrastructure: AI authoring where you ask for it, deterministic branded rendering always, and the visual-QA gate before delivery. Every deliverable carries its provenance record.
The API and MCP doors — private preview
The /v1 REST API and an MCP server are available for DocMark cloud in private preview
(by invitation — issue a token from Admin → Integrations). Your copilot writes the outline and DocMark
returns a verified, on-brand deck or document — or precise findings your copilot can fix and resubmit.
Claude Desktop, Claude Code, and enterprise copilots that speak MCP treat DocMark as their
document-production arm (a two-file setup: point the MCP server at the cloud with your token), while your
brand rules and the verification gate stay enforced on our side.
Want API or MCP access in the managed cloud today? Talk to us about the private preview. (If you need the API and MCP server running in your own boundary right now, that’s Mode 2 — Client cloud, where you operate them yourself.)
Who it’s for
Teams whose content isn’t restricted to their own network: marketing, internal enablement, agencies, and anyone who wants the fastest possible start. If your content must stay on your own network or inside your own cloud tenant, look at Mode 1 — On-prem or Mode 2 — Client cloud instead — the comparison page makes the trade-offs explicit.