AI-DMS — UI · Chat Agent · API
Web · Desktop · Mobile The app for teams — capture, search and approve documents. Claude · ChatGPT · Cursor Use PaperOffice via chat — same workspaces and permissions. REST · MCP · one API key All capabilities for developers — one platform, one key.Use PaperOffice as a complete AI-DMS, as a headless document layer or directly through MCP. You define the product, interface, industry expertise and service package.
Trusted by leading companies worldwide
OEM PARTNERSHIP
Dedicated landing pages, direct integration, data stays on your NAS.
Sole official DMS partner for QNAP NAS — documents stay on your device, AI runs through PaperOffice.
More
Listed by ASUSTOR as “the DMS for ASUSTOR NAS” — sole official partner.
More
Extraction, archive, signature or agents exist individually in the market — as one shared, governance-secured MCP surface they exist with PaperOffice.
AI agents work inside a complete DMS: workspaces, storage, history, relationships and processes. The agent can search, file, link, request approval, sign and send — in the same context.
Others: document in, JSON out. No workspace, no archive, no process.
Workspace protection, permissions, human-in-the-loop requirements, legal hold, WORM and audit trail are enforced server-side. No prompt and no agent can bypass them.
Others: agent frameworks without governance, or DMS governance without an agent surface.
Trigger signature requests, start workflows, send with audit trail, take calls through the phone agent — with HITL stops at critical steps.
Others: read-only RAG. Chat about documents without triggering actions.
Own EU data center and own models on own hardware. Documents do not leave the platform toward US hyperscalers.
Others: extraction as a thin layer over OpenAI, Azure or Google.
This rests on 24+ years of DMS practice since 2002: compliant archiving and real archive operations — not only an API.
Every agent works only in the granted workspace context.
Read, write and action rights apply independently of the prompt.
Critical steps can require approval before execution.
Actions remain traceable even when an agent triggers them.
Immutable storage protects audit-ready holdings.
Holds and retention rules are enforced in the layer.
The access paths are not separate products. They use the same workspaces, permissions and processing flows. The access path is a business-model decision — not a product decision.
Web, desktop and mobile for teams, roles, workflows and agents.
Ready to use as a finished productInvisible document and process layer behind your own application.
Your brand, your user experienceDocuments, OCR, IDP, workflows, search and administration over REST.
300+ documented REST callsClaude, ChatGPT, Cursor and custom agents on curated capabilities.
300+ MCP tools across multiple profilesIDP, workflow, chat, phone and ticket agents.
Human-in-the-loop for critical stepsEvery document application is built from the same five primitives. Because PaperOffice covers all five completely and combinably, every industry solution is a configuration — not a rebuild.
Illustrative industry configurations
| Building block | Tax firm | Logistics | Property management | Healthcare |
|---|---|---|---|---|
| Ingest Email ingest, watchfolder, upload, BYOS storage mounts | Client mailbox | Waybill scan at the gate | Tenant upload portal | Report intake |
| Understand AI OCR, IDP agents, entities, embeddings, knowledge graph | Invoice & accounting export | Delivery note & waybill | Lease & utilities | Handwriting & forms |
| Decide Rules, HITL queues, Trust/Redact/Split agent | HITL approval per client | Duplicate & integrity checks | Deadline review with approval | PII redaction before handoff |
| Act Workflows, signature, audited delivery, phone/chat agent, webhooks | Accounting export via webhook | ERP handoff & notice | eIDAS lease signature | Audited delivery |
| Govern Workspaces, rights, WORM, legal hold, audit trail, revisions | Audit-ready client archive | Long-term customs archive | Object-based workspaces | Role-based access, audit report |
Your vertical is another column — the same building blocks, a different configuration.
Integrate OCR, document chat, IDP or full document processing into an existing SaaS or ERP environment.
Higher product value without building Document AI yourselfOffer PaperOffice as a complete solution under your own customer relationship.
Own market position on a finished platformPreconfigured solutions for finance, legal, logistics, healthcare or public administration.
Industry knowledge as a differentiable productCombine rollout, migration, storage mounts including mirrors and health monitoring, operations, audit reports and support.
Recurring services around the platformEquip custom AI agents with document, workflow and communication tools; chat, phone and ticket agents on the same workspace.
Agentic processes with real enterprise dataEmail ingest per client mailbox
Split agent separates batch PDFs
Invoice and accounting extraction
HITL approval by firm staff
Audit-ready archive and accounting export
Upload via API from the partner app
IDP extraction and duplicate checks
Entity and supplier matching
Webhook delivers structured data to the ERP
Audit trail and retention in the background
Custom agent connects to a protected workspace
Semantic search and knowledge graph provide context
Agent prepares an action — HITL stop before execution
Signature request or audited delivery is triggered
Phone agent answers follow-ups on the same workspace
No. PaperOffice can be used as a finished AI-DMS. A custom interface is only required for headless or embedded offerings.
Yes. An application can process documents over REST while an AI agent uses the same workspaces through a curated MCP profile. Data and rules stay identical.
No. Workspace protection, rights, human-in-the-loop requirements, legal hold and audit trail are enforced server-side — regardless of how the agent is driven.
No. All solutions are built from the same five building blocks — ingest, understand, decide, act, govern. Industry solutions are configurations of these blocks.
Go deeper on the integrator track, review the reseller model, or start directly with MCP and API.
