M-Files On-Premises

Customer-operated document vault and information-governance platform with metadata-driven workflows.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Licensed Windows Server installation; vendor implementation planning

  2. Operated by

    Your team

    Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    M-Files self-managed cloud deployment ↗ · Source checked 2026-11-12

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    M-Files self-managed cloud deployment ↗ · Source checked 2026-11-12

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    M-Files self-managed cloud deployment ↗ · Source checked 2026-11-12

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodLicensed Windows Server installation; vendor implementation planning
InfrastructureServers / containers
Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.
Licensing modelCommercial Only
Commercial M-Files server subscription software. The EULA covers ordered on-premises or cloud software and associated licenses/support; this entry selects on-premises operation.
LicenseCommercial subscription software; on-premises and support entitlements follow the order

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The vault authentication guide explicitly links on-premises Microsoft Entra configuration and OAuth 2.0/OIDC providers for any environment. Client/web-add-in configuration and licensed implementation requirements remain separate.

M-Files document-vault authentication; not Hubshare or automatic cloud login setup · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

The guide documents subscription-level SCIM for on-premises servers joined to M-Files Manage. A separate vault-level Entra SCIM method requires Entra ID Premium and limits Entra authentication to Desktop; on-premises plugin-based synchronization is also documented.

M-Files on-premises provisioning; Manage connection, method and client limitations differ · Source ↗ · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The vendor supplies an installation package containing Server, Admin and optional desktop components. The guide links the latest package through the vendor download portal and documents advanced installation options. Package access and entitlements must be obtained; this is not a public infrastructure template.

Current on-premises Windows installer distribution · Source ↗ · Deployment artifact ↗ (Vendor latest-download portal; authenticated or entitled access may be required) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The single-server guide lists 2 CPU cores, 1 GB RAM and 300 MB for M-Files Server itself. Its examples scale to 4 cores/4 GB for 50,000 objects and 8 cores/16 GB plus SQL Server for one million. File storage, database, backups and HA need separate sizing; these are object-count examples, not a 100-user guarantee.

Vendor single-server guidelines; application storage and HA excluded · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The on-premises server is linked to a customer subscription using an initial licence from M-Files Manage. Automated renewal needs outbound licensing endpoints. This establishes subscription/licence delivery, not a published per-user price or infrastructure cost.

On-premises server subscription and licence automation · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.

Category fit

Document management
Metadata-driven document vaults with controlled access, document relationships and workflows.
Records management
Configurable records retention and disposition rules with document history and audit trails.
Policy & procedure management
Configured SOP, compliance and training workflows supported by metadata, permissions and document lifecycle controls; not a separately verified turnkey policy module.

Compare within Document management

  • Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
    • AWS
    Customer-operated · Open Source / Open Core
  • Apache JSPWikiApache file-based wiki for documentation and knowledge content.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • DocassembleSelf-hosted guided interviews and automated document assembly.
    • AWS
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocspellSelf-hosted document ingestion, OCR, classification and search.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
    • Azure
    Customer-operated · Commercial Only
  • eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
    • Hostinger
    Customer-operated · Open Source / Open Core

Showing 8 of 41 other listings in Document management. These products address related workflows; read their category-fit notes before comparing scope. See all of Document management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • M-Files self-managed cloud deployment ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory