Mayan EDMS
Key Info:
Mayan EDMS is an open-source, self-hosted electronic document management system for storing, classifying, searching and controlling files. It combines document types, metadata, OCR, previews, versions, permissions, workflows, signatures and a REST API in a web-based application.
Details
Document ingestion and description
Documents are created under defined document types and can receive structured metadata, labels and related business context. Sources and staging workflows support ingestion, while OCR and parsing make scanned or textual content available to search. Preview generation lets users inspect supported formats in the browser. Administrators should test queue throughput, failed conversions, language-specific OCR and a document whose metadata is incomplete before choosing worker and storage capacity.
Control and retrieval
Mayan EDMS retains document versions and can apply fine-grained permissions to document types and individual items. Search, indexes, tags and smart links provide several retrieval paths, while event logs preserve an operational history. Signature functions and document transformations support specialised governance processes. A proof should confirm that restricted metadata, previews, search results and API responses all obey the intended role model.
Workflow and integration
A workflow engine can model document states, transitions and automated actions. The REST API exposes document and configuration resources for integration with other applications, and web links provide additional connection patterns. Deployments can use Docker and can be scaled with separate workers and storage components. Teams should define who owns configuration, upgrades, monitoring, backups, secrets, extensions and recovery because self-hosting transfers those responsibilities to the operator.
Fit and evaluation
Mayan EDMS may suit technically capable organisations that want an open-source DMS and need control over hosting or integration. It is not a managed cloud service by default, so total cost includes infrastructure and operational expertise. Evaluate the current supported release, license, installation model, performance, accessibility, identity, permissions, search, OCR, workflow administration, audit retention, backup and restore. Complete a restore exercise and an upgrade rehearsal before treating a pilot as production-ready.
Decision record
Document the tested document types, retrieval results, permission model, exception handling, required edition or modules, migration assumptions and named operational owner. Keep unsupported pricing, customer-size, language and device values blank until a current official source maps them exactly to the BBS field.