Mode 1 — On-prem

The promise

Your analysts author the content. DocMark — running entirely on your own hardware, inside your own network — renders it into a branded, client-ready deliverable and verifies it locally. No AI, no cloud, no internet anywhere in the pipeline; the box can run fully air-gapped. That is not a configuration choice that someone could flip; it is how this mode is built, and it is verified at installation on your box.

In this mode, zero-egress means exactly that: nothing leaves the premises — no internet, no model, no telemetry. (DocMark’s managed cloud uses the phrase differently — there it means no PII reaches the execution plane. Both are real; they are not the same thing. See the comparison.)

How it works

1. An analyst drops a content file into a shared intake folder — that’s the whole integration.
2. The DocMark box (a managed appliance on your hardware) picks it up and renders it in a no-network sandbox, applying your committed brand specification and logos.
3. The local visual-QA gate renders every page and checks it for blank or failed pages (deeper visual checks are on the roadmap).
4. Pass: a verified branded deliverable appears in the results folder, carrying its zero-egress label and a brand-provenance record. Fail: a plain-language reason appears in the failed folder instead — the deliverable is withheld.

Who it’s for

Legal teams, valuation and M&A groups, and anyone whose content is client-confidential enough that “we have a DPA” is not an acceptable answer. If your security review starts with “nothing may leave the building,” this is your mode.

Proof, not promises

• End-to-end verification runs offline — disconnect the box and it still works.
• At handover, our installation checklist runs on your machine, with your team watching.
• Every artifact carries a machine-written egress-class label; the zero-egress claim is enforced by the pipeline, not by policy documents.