Managed Paperless-ngx hosting
Pilae installs, patches, backs up and monitors Paperless-ngx for you, on your own servers or in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
From CHF 449EUR 479USD 559 a month on Starter, hosting and onboarding included.
- Business
- Open source
- Replaces DocuWare
- Runs on
- Your own hardware, or a Pilae Cloud region
- Replaces
- DocuWare, M-Files
- Licence
- GPL-3.0
Paperless-ngx among the business apps
CRM, ERP, projects and scheduling. The records you are least willing to rent.
Paperless-ngx system requirements
Before anything is deployed, this is what has to exist. We size it with you in the first session, and we say so when your own hardware is already enough.
All 5 requirements, and why each is there
- CPU and memory4 vCPU · 8 GBOur starting size with Tika and Gotenberg beside it; upstream publishes no minimum. OCR decides the size: task workers times threads per worker should not exceed the core count.
- DatabasePostgreSQLRecommended upstream for new installations. The default is a SQLite file in the data volume, and MariaDB is supported with caveats about case sensitivity.
- Message brokerRedis or ValkeyCarries the task queue, scheduled tasks included. While it is down, nothing is consumed and no mail is fetched.
- Office files and emailTika + GotenbergOptional upstream, and needed for Word, Excel, PowerPoint and .eml files. Gotenberg renders email with JavaScript off and only local files allowed, so a message cannot load a tracking pixel.
- Sign-inOIDC via django-allauthOpenID Connect to Keycloak or Entra ID, with groups synced from a claim onto Paperless-ngx groups of the same name. Password login can be turned off for the web app but not for the API or the Django admin, so those stay on the private network.
Running Paperless-ngx in production: what it takes
Size OCR to your post, then deploy
A version we have run, on a dedicated machine with encrypted disks: PostgreSQL rather than the default SQLite file, a Redis-compatible broker, and Tika and Gotenberg for Office files and email. OCR languages and worker counts are set to match your own post.
Give every intake path an owner
The scanner share, each mailbox and the API get a workflow that assigns the owner, group permissions and document type on arrival. Without one, a file consumed from the folder has no owner and every user can open it.
Turn off password login in the web app
OpenID Connect to Keycloak or your own IdP such as Microsoft Entra ID, with groups synced from the token and password login off in the web app. The API and the Django admin still accept local credentials, so the instance answers only on your private network.
Back up files and database together
The media volume and PostgreSQL go offsite at the same moment, daily, encrypted, while nothing is being consumed. On the Enterprise plan, once a month we restore both into a scratch instance on the same pinned version and run the sanity checker, which compares every original and archive file with its stored checksum.
Upgrade on a copy of your archive
Each release runs its database migrations when the container starts, and the search index rebuilds itself when its format changes. The last major release replaced OCR, consumer and database settings and could only be reached from the final release of the line before. The Pilae Agent tests each upgrade on a copy of your archive, waits for your approval and applies it in your window, with the backup taken just before as the rollback.
From our runbook
A Paperless-ngx environment file for acme
# docker-compose.env (excerpt) · acme-paperless · zur1 PAPERLESS_URL=https://paperless.acme.internal PAPERLESS_SECRET_KEY_FILE=/run/secrets/paperless_secret_key PAPERLESS_TIME_ZONE=Europe/Zurich # PostgreSQL on the private network, TLS required PAPERLESS_DBENGINE=postgresql PAPERLESS_DBHOST=db-01.acme.internal PAPERLESS_DBPASS_FILE=/run/secrets/paperless_db PAPERLESS_DB_OPTIONS=sslmode=require PAPERLESS_REDIS=redis://broker:6379 # French, German and English ship with the image PAPERLESS_OCR_LANGUAGE=fra+deu+eng PAPERLESS_TASK_WORKERS=2 PAPERLESS_THREADS_PER_WORKER=2 # Word, Excel and .eml through Tika and Gotenberg PAPERLESS_TIKA_ENABLED=true PAPERLESS_TIKA_ENDPOINT=http://tika:9998 PAPERLESS_TIKA_GOTENBERG_ENDPOINT=http://gotenberg:3000 # consume/ is the scanner share, one folder per department PAPERLESS_CONSUMER_RECURSIVE=true PAPERLESS_CONSUMER_SUBDIRS_AS_TAGS=true # Sign-in through Keycloak only, groups from the token PAPERLESS_APPS=allauth.socialaccount.providers.openid_connect PAPERLESS_SOCIALACCOUNT_PROVIDERS_FILE=/run/secrets/paperless_oidc PAPERLESS_SOCIAL_AUTO_SIGNUP=true PAPERLESS_SOCIAL_ACCOUNT_SYNC_GROUPS=true PAPERLESS_DISABLE_REGULAR_LOGIN=true PAPERLESS_REDIRECT_LOGIN_TO_SSO=true # Originals survive an emptied trash; AI stays off until asked for PAPERLESS_EMPTY_TRASH_DIR=../media/trash PAPERLESS_AI_ENABLED=false
Migrating from DocuWare to Paperless-ngx
Paperless-ngx has no DocuWare importer, and its own importer reads only what its exporter wrote. The route out is docXporter, a DocuWare add-on licensed separately, which writes each document in its original format with its index data. Each file then goes in through the Paperless-ngx API with its date and index values already set. Paperless-ngx stores every file as it arrives and runs OCR on the ones without a text layer. Stamps and annotations come across only if docXporter burns them into a PDF copy. DocuWare workflows and the old audit trail stay behind: Paperless-ngx workflows act on intake, on a change or on a date, and have no approval steps. Mapping file cabinets and index fields takes longer than the copy.
- CompareSelf-hosting vs managed open source: doing it yourself, or PilaeSelf-hosting gives you the apps and the whole job of running them. Pilae gives you the same open-source apps, operated under a contract, on your premises or in Pilae Cloud.
Moving from DocuWare to Paperless-ngx, step by step
- Map the cabinets and index fields: Which file cabinets are still filed into, which are only kept for their retention period, and what each index field becomes in Paperless-ngx: a document type, a correspondent, a tag or a custom field. This mapping decides the rest.
- Export with docXporter: Cabinet by cabinet, with each export counted against DocuWare before anything is loaded. docXporter needs its own DocuWare licence, which we raise at the start rather than at the end.
- Load through the API: Each file is posted with its title, date, archive serial number and mapped values. A workflow on API intake sets the owner and group permissions, and the classifier learns from the migrated archive, so new post is filed the way the old archive was.
- Switch the scanners and mailboxes last: Scanners move to the consumption share and mail rules take over the invoice mailbox. DocuWare stays read-only until one month-end has closed on Paperless-ngx, and its licence lapses after that.
What Paperless-ngx is, and who runs it
OCR, filing and full-text search for scanned and emailed documents, run in Switzerland, the EU or your own datacentre so invoices, contracts and letters stay on storage you control.
Self-hosted Paperless-ngx for scanned and emailed documents
Paperless-ngx turns paper and PDFs into an archive you can search. Documents arrive from a watched folder, a mailbox, the web upload or the API. It runs OCR with Tesseract through OCRmyPDF, keeps the original file and, for scans, stores a searchable PDF/A copy beside it. Matching rules, or a classifier trained on what you have already filed, assign the correspondent, document type and tags, and full-text search covers the lot.
It grew out of personal and small-office use, and the design still reflects that. The project is community-supported, the successor to Paperless and Paperless-ng, and its own README calls a local server in your own home the safest place to run it. Three things matter at organisation scale: permissions are set per document owner, user and group rather than per cabinet; there are no approval workflows, check-out or retention locks; and files sit unencrypted on an ordinary filesystem. It is what teams move to from DocuWare or M-Files when what they use every day is capture, filing and search rather than workflows.
Read the full briefFold the brief
Paperless-ngx in production: scanners, mailboxes and permissions
It runs on a dedicated machine with encrypted disks, in your own building or in a Pilae Cloud region, where six of our 10+ regions are in Switzerland and the EU, and it answers only on your private network. Share links are public URLs that need no login, so they reach nobody outside until you choose to publish them through the gate on port 443.
Scanners drop into a share with one folder per department, and mail rules read the shared mailboxes. A workflow on each intake path sets the owner and group permissions, because a file consumed from the folder otherwise has none. Sign-in goes through Keycloak or Entra ID, with groups taken from the token.
Probes check the instance every 60 seconds, and a failed consumption task alerts an engineer. Without that alert, a bad attachment is skipped in silence: the message is left where it was but recorded as processed, so Paperless-ngx does not try it again. Backups of the database and the media volume go daily, encrypted, to an offsite location in the country your contract names, and on Enterprise the monthly restore drill ends with the sanity checker. Upgrades go through the Pilae Agent: tested on a copy, approved by you, applied in your window.
The OCR text is available through the REST API, so it can feed retrieval in Open WebUI, provided the document permissions travel with it. Paperless-ngx has its own opt-in AI features, and we point them at Ollama on your network rather than at a hosted API.
Paperless-ngx licence and support
Every feature on this page is in the build we deploy, unmodified. Our operation follows the published plans. Talk to us about the post and the archive you want to move.
What Pilae is responsible for
The same commitments on every app we run, Paperless-ngx included, and what stays yours. How the platform does it.
Ours
- A pinned version: A version we have run, not whatever latest resolves to that day.
- A runbook: What it depends on, how it fails, what to do about it. In your repository.
- Daily backups: Encrypted and offsite, and on Enterprise restored every month. A backup nobody has restored is a file.
- A patch window: Security updates in a window you agreed, with a rollback ready.
- Someone watching: Every endpoint probed on the minute. An alert reaches a person, not a dashboard nobody opens.
Yours
- The credentials: You hold them. Ours are separate, named, logged and revocable with one command.
- The approval: We ask before anything changes outside an agreed window.
- The exit: The machine, the data, the compose files and the runbook are already yours. Nothing stops when our access does.
Who runs it
Engineers who answer for it
Our engineers review every plan the Pilae Agent prepares and answer for the result.
Your data stays where the contract says
On your own servers or in Pilae Cloud. On Business and Enterprise you choose the region, and your contract names each location.
A Swiss company, a Swiss contract
Pilae is a Swiss company, and your contract with it is governed by Swiss law.
Paperless-ngx runs on Starter from CHF 449EUR 479USD 559 a month in Pilae Cloud, or on Business with up to three apps on your own servers.
Compare the plansPaperless-ngx: common questions
Is Paperless-ngx open source?
Where do our documents live?
Can Paperless-ngx replace DocuWare?
How do permissions work across departments?
Does Paperless-ngx send our documents to an AI service?
Ask the engineers who would run your Paperless-ngx
Thirty minutes on the deployment you already have, or the one you are about to start.
- Go deeperPrivate IT and AI for Swiss law firms, notaries and fiduciariesClient files, collaboration and private AI for law firms, notaries and fiduciaries, on your premises or in Switzerland, operated under terms fit for professional secrecy.
- CompareBusiness appsCRM, ERP, projects and scheduling. The records you are least willing to rent.
- CheckData processing agreement (DPA)Our standard DPA under the revised FADP and the GDPR, signed at onboarding, with every sub-processor for your service named in the agreement.
