Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Hyland Software, Inc. · hyland.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
OnBase at a glance
- Vendor
- Hyland Software, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates OnBase 2.5/5, the mean of 6 judges. OnBase, Hyland's document management system, scores highest on document workflows — flat at 7 — for approval management documented end to end (levels, queues, delegation, escalation of expired approvals, reminders, CSV import and export), a SAP ArchiveLink connector naming invoice transaction codes such as MIRO and FB60, and REST, Workflow, Forms and GraphQL APIs. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
OnBase, Hyland's document management system, scores highest on document workflows — flat at 7 — for approval management documented end to end (levels, queues, delegation, escalation of expired approvals, reminders, CSV import and export), a SAP ArchiveLink connector naming invoice transaction codes such as MIRO and FB60, and REST, Workflow, Forms and GraphQL APIs. Capture and indexing follows at 6-7, built on the Hyland OCR engine, intelligent character recognition, form identification, line-item extraction and an index verification step. Weakest are sovereignty at 1-2 — no deployment model, contracting-entity jurisdiction, data residency, subprocessors or data processing agreement stated, and installation guides only imply customer-operated servers — and pricing transparency at 1, with tiers Premier, Standard and Essential named and no public price figure. Audit-proof archiving scores sit at 4 with no variation: retention is documented machinery, but no GoBD statement, auditor's report, immutability mechanism or tax-audit export appears. Score ranges stay narrow throughout; the widest, versioning and permissions at 4-6, turns on how much credit the documented activity log and security-masked keywords earned, and the flagged splits flag none.
Speaks for it
- Approval management is documented end to end — levels, queues, roles, delegation, escalation of expired approvals, reminders, and CSV import and export of approval processes.
- The SAP ArchiveLink connector names invoice transaction codes (MIRO, FB60, KO01, ME21N) with early and late storage, mass archival and an ILM interface.
- Advanced Capture pairs the Hyland OCR engine and intelligent character recognition with form identification, line-item extraction and an index verification step.
- Full-text search supports comparative and logical operators, a custom thesaurus and load balancing, with web, Unity and mobile clients and offline document access.
- Document Retention offers static and dynamic retention per document type or group, evaluation and purge, transaction logs and viewable destroyed-document information.
Held against it
- Sovereignty scores run 1-2, with no stated deployment model, contracting-entity jurisdiction, data residency, subprocessors or data processing agreement — installation guides only imply customer-operated servers.
- Audit-proof archiving scores sit at 4 with no variation, and no GoBD statement, auditor's report, immutability mechanism, tax-audit export or Verfahrensdokumentation is documented.
- Versioning and permissions scores run 4-6, with no public information on version restore, single sign-on or directory sync, or a tamper-evident exportable audit trail.
- Search and portability scores run 4-5, with no public information on bulk export of documents with metadata and versions or any documented exit path.
- License tiers Premier, Standard and Essential are named under Simplified, Additional and Legacy licensing with no public price, billing period or inclusions.
Best for
- You run SAP and want a documented ArchiveLink invoice handover with named transaction codes alongside deep approval routing.
- Your intake is heavy on scanned forms, barcodes and line-item extraction and you want an index verification step before filing.
- Your IT team can install and operate the system on its own servers, matching the customer-operated installation the guides imply.
Avoid if
- You must show a German tax auditor GoBD-conformant, tamper-evident archiving today — audit-proof archiving scores sit at 4 with no variation.
- You must document data residency, the subprocessor chain and a data processing agreement before signing — sovereignty scores run 1-2.
- You need a documented exit with bulk export of documents, metadata and versions when the contract ends — search and portability scores run 4-5.
- Your disputes depend on restoring earlier versions and a tamper-evident, exportable audit trail — versioning and permissions scores run 4-6.
The scores
| Criterion | Panel median |
|---|---|
| Capture, OCR & indexing | 3.5 of 5 |
| Versioning, permissions & audit trail | 2.5 of 5 |
| Audit-proof archiving & retention | 2 of 5 |
| Document workflows & integrations | 3.5 of 5 |
| Search, retrieval & exit | 2.5 of 5 |
| European sovereignty | 1 of 5 |
Capture, OCR & indexing
Show reasoningHide reasoning
How this is scored
How documents get in and become findable: scanning and email intake, OCR, classification and metadata extraction, and whether incoming e-invoices (XRechnung, ZUGFeRD) are read as structured data rather than as pictures.
0 — Not a document intake tool: files cannot be uploaded or captured into the product as documents.
3 — Upload, drag-and-drop or scan import with full-text OCR; email intake, document types and field extraction are basic or not described.
5 — Scanner or app capture and email intake, full-text OCR, and document types with metadata fields, some filled automatically (date, sender, amount or similar).
8 — AI- or rule-based classification and field extraction with a validation step, XRechnung and ZUGFeRD read as structured data, mailbox and Microsoft 365 intake, and duplicate detection documented.
10 — Capture is engineered and shown: classification and extraction trainable per document type, validation queues, e-invoice validation against the standard, intake channels listed with their limits, and where AI processing runs (location, model provider) stated.
The GoBD Auditor
The Advanced Capture manuals document ad hoc and batch scanning, the Hyland OCR engine with intelligent character recognition, bar-code and form identification, keyword lookup/replace dictionaries, line item extraction and an index verification step, plus photo upload from the mobile app and Outlook archiving. We found no public information on XRechnung or ZUGFeRD read as structured data, duplicate detection, or where recognition processing runs, which keeps this below the top level. 1 2 6 8
The Records Manager
Capture is engineered rather than bolted on: the Advanced Capture module documents ad hoc and batch modes, the Hyland OCR engine, intelligent character recognition, bar-code processing, line-item extraction in automatic and manual table decomposition, and an index verification step, with Outlook archiving and mobile photo upload for intake. We found no public information on XRechnung or ZUGFeRD read as structured data, duplicate detection, or where AI processing runs. 1 2 6 8
The IT Integrator
The Advanced Capture documentation shows rule-based form identification (text value and image match), data field zones with automatic and manual line-item extraction, OCR and ICR on Hyland's own engine, barcode and optical-mark processing, and a dedicated Index Verification step — a genuine capture pipeline with validation. We found no public information on reading XRechnung or ZUGFeRD as structured data, on duplicate detection, or on where AI processing runs, and the only email intake shown is Outlook archiving in the SAP connector guide. 1 2 6
The Mittelstand Owner
The Advanced Capture manuals document OCR with the Hyland engine, ICR, bar-code and form-identification zones, line-item extraction, keyword lookup dictionaries and an index-verification step, and the mobile apps add photo capture and bar-code reading. What I miss as an invoice buyer: we found no public information on mailbox or Microsoft 365 intake, on XRechnung or ZUGFeRD being read as structured data, or on duplicate detection. 1 2 8
The Data Protection Officer
Advanced Capture is documented in depth: form identification by text value or image match, data-field zones, automatic and manual line-item extraction, ICR and the vendor's own OCR engine, bar-code processing, index verification, and ad hoc, batch and point-and-shoot modes, with document upload and photo capture on mobile. Document types carry keyword types with AutoFill sets and auto-numbering, and Outlook archiving is documented. We found no public information on reading XRechnung or ZUGFeRD as structured data, on duplicate detection, or on where OCR processing runs. 1 2 6 8
The Skeptic
Advanced Capture is documented in real depth: the Hyland OCR engine plus ICR with accuracy limitations stated, form identification by text value or image match, line-item extraction in automatic and manual table decomposition modes, keyword lookup/replace dictionaries, and an Index Verification step — a validation stage, which I credit. What keeps this down: the captured pages show no XRechnung or ZUGFeRD reading as structured data, no duplicate detection, and no statement of where OCR processing runs. 1 2
Versioning, permissions & audit trail
Show reasoningHide reasoning
How this is scored
Who may see and change which document, what happened to it, and whether earlier states can be recovered: version history, check-in and check-out, role- and attribute-based rights, and an audit trail of reads and changes.
0 — A file drop without users or history: anyone with access sees and overwrites everything, by the vendor's own description.
3 — Version history and folder or workspace permissions; check-out, roles and an audit log are basic or not described.
5 — Version history with restore, users, roles or groups with rights per folder or document type, and a log of who changed or accessed documents.
8 — Check-in and check-out, metadata-driven permissions (by department, client or confidentiality), an audit trail covering reads, exports and deletions, single sign-on and directory sync (Entra ID, LDAP) documented, and administrators' own actions logged.
10 — Access is provable: the audit trail is tamper-evident and exportable, permission changes are themselves versioned, field-level rights and need-to-know access for HR or legal records documented, and the log retention period stated.
The GoBD Auditor
User administration, user groups, document history with a report, an activity log, security-masked keyword values, workflow document security and lock management are documented, giving a workable rights and change-log story. We found no public information on restoring earlier versions, single sign-on or directory synchronisation, or on a tamper-evident and exportable trail, which is what the upper levels require. 2 4 5 8
The Records Manager
User administration, workflow document security, keyword values that can be security-masked, lock management, and a document history with reports and an activity log are all documented, which is the core of accountable access. We found no public information on version restore, directory synchronisation for sign-on, or a tamper-evident, exportable audit trail, so I cannot confirm an earlier state is recoverable when a dispute lands on my desk. 2 4 8
The IT Integrator
Document history with reports, an activity log, user administration, document locks and security-masked keyword values are all documented, which covers who changed what and hints at check-out and field-level masking. We found no public information on restoring earlier versions, on single sign-on or directory sync with Entra ID or LDAP, or on a tamper-evident, exportable audit trail. 2 4 5 8
The Mittelstand Owner
The captured manuals show an activity log, document history reports, user administration, security-masked keyword values and Identity Server authentication, which is a start on who saw what. We found no public information on version history with restore, check-in and check-out, or single sign-on with directory sync, so I cannot see how cleanly personnel files could be walled off from the purchasing team. 2 4 8
The Data Protection Officer
User administration, an activity log, document history with reportable history reports, and document locking are documented, and keyword values can be security-masked — a field-level control I take seriously for personnel files. Approval users, roles, user rules and queues are configurable per group and document type. We found no public information on version history with restore, single sign-on or directory sync, or tamper-evidence of the audit trail. 2 4 5 8
The Skeptic
Document history with a history report, user administration, managing locks, security-masked keywords and an activity log are all documented, and approval delegation provides substitutes. But the audit story stops at viewing an Activity Log inside the retention module; we found no public information on an audit trail covering reads and exports, single sign-on or directory sync, or tamper-evidence of the log. 2 4 8
Audit-proof archiving & retention
Show reasoningHide reasoning
How this is scored
GoBD-compliant, revisionssicher archiving: immutability of archived documents, retention schedules and deletion, tax-audit data access, and the independent evidence behind the claim — scored on what is certified and documented, not on the word "GoBD-konform".
0 — Not an archive: a file store or collaboration space in which, by the vendor's own description, documents can be edited or deleted at any time and no retention function exists.
3 — "GoBD-konform" or "revisionssicher" archiving claimed, or retention mentioned; how immutability is achieved and how retention is configured are basic or not described.
5 — GoBD-compliant archiving stated with archived documents protected against change, retention periods configurable per document type, and GoBD guidance or a sample Verfahrensdokumentation offered.
8 — An auditor's report (IDW PS 880 or comparable) published or named with its scope and date, WORM or equivalent storage described, deletion after expiry and legal hold, GDPR deletion reconciled with retention duties, and Z1–Z3 tax-audit export documented.
10 — Archiving is evidenced end to end: current Testat with scope covering the cloud and on-premises editions as sold, retention and deletion logged and reportable, long-term formats (PDF/A) enforced, and a documented procedure for the tax audit and for moving the archive without breaking its integrity.
The GoBD Auditor
The Document Retention module is genuinely documented: static and dynamic retention configurable per document type or document type group, evaluation and purge, exclusions, a transaction log, and viewable destroyed-document information. We found no public information on a GoBD or revisionssicher claim, on how immutability of archived documents is achieved, on an auditor's report with scope and date, on a tax-audit export, or on a Verfahrensdokumentation — exactly the evidence I would demand before trusting this as an archive. 3 4
The Records Manager
Retention is real and configurable: retention types per document type or group, static and dynamic modes, evaluation and purge, exclusions, a transaction log per process, records of destroyed documents, and a records management link. We found no public information on GoBD or revisionssicher claims, how immutability of archived documents is achieved, an auditor's report, legal hold, or tax-audit export. 3 4
The IT Integrator
Document Retention is documented in depth: retention types per document type or group, static and dynamic retention, exclusions, evaluation and purge, transaction logs and views of destroyed documents. We found no public information on GoBD or revisionssichere archiving claims, on the mechanism protecting archived documents against change, on legal hold, or on any auditor's report. 3 4
The Mittelstand Owner
A dedicated retention module is properly documented: static and dynamic retention configurable per document type, evaluation and purge, destroyed-document records, transaction logs and exclusion handling. But we found no public information on GoBD conformity, immutability mechanisms, an auditor's report or a tax-audit export — and for my German tax office that is the whole question. 3 4
The Data Protection Officer
A full Document Retention module is documented: retention types configurable per document type or document type group, static and dynamic retention, schedule templates, evaluation and purge, exclusions, a transaction log, and destroyed-document information that remains viewable afterwards. We found no public information on GoBD-compliant or revisionssichere archiving claims, WORM or equivalent storage, legal hold, tax-audit export, or how GDPR deletion is reconciled with retention duties — the reconciliation I ask about first. 3 4
The Skeptic
Retention is real machinery — static and dynamic retention configurable per document type or group, evaluation and purge, a transaction log per retention process, and destroyed-document information still viewable afterwards. But the audit-proof claim itself is unevidenced: no GoBD statement, no auditor's report named with scope and date, and we found no public information on how archived documents are protected against change or on tax-audit export. 3 4
Document workflows & integrations
Show reasoningHide reasoning
How this is scored
What happens to a document after it arrives: approval and invoice workflows, tasks and deadlines, and the connectors that tie the DMS to ERP, accounting, DATEV, Microsoft 365 and the rest of the stack.
0 — Storage only: the product is described as an archive or file store with no tasks, approvals or connections to other systems.
3 — An approval, sharing or task step and a few named integrations; a workflow designer and an API are basic or not described.
5 — Configurable approval or invoice workflows with tasks and deadlines, Microsoft 365 or Outlook integration, and an API or connectors to named accounting or ERP systems such as DATEV.
8 — Graphical workflow modelling without code with substitutes and escalation, invoice workflow with ERP or DATEV handover documented, connectors for named ERP systems (SAP, Microsoft Dynamics, DATEV) with their scope, a documented REST API with webhooks or events, and e-signature integration.
10 — Workflows are a platform: versioned workflow definitions, process reporting with throughput times, a public API reference with rate limits and a sandbox, a partner marketplace of integrations with stated maintainers, and workflow history kept in the audit trail.
The GoBD Auditor
Approval management is documented in depth — approval levels, queues, roles, delegation, escalation of expired approvals, reminders, rule conditions on document type and keyword values, an accounts payable application, and CSV import and export of approval processes. The SAP connector names its scope including invoice transactions such as MIRO and FB60 and early storage with workflow, and API Server, Workflow API, Forms API, a Document Management REST API and GraphQL are documented; we found no public information on graphical workflow modelling, webhooks or a partner marketplace. 5 6 8
The Records Manager
Approval handling is deep — levels, roles, queues, delegation, escalation of expired approvals, reminder notifications, rules on document type and keyword values, and approval processes that export and import as CSV — and the SAP connector documents invoice handover through t-codes such as MIRO and FB60, alongside REST, Workflow and GraphQL APIs. We found no public information on graphical workflow modelling, webhooks or events, DATEV, or e-signature integration. 5 6 8
The IT Integrator
Workflow Approval Management is thoroughly documented — approval levels, queues, roles, delegation, escalation of expired approvals, reminder notifications, rule conditions on document type, keyword value and script, and approval processes exportable and importable via CSV — and I get a full SAP ArchiveLink connector with named transaction codes (MIRO, FB60), early and late storage, mass archival, an ILM interface, plus documented REST and GraphQL APIs. We found no public information on DATEV or Microsoft Dynamics connectors, on webhooks or events, on a graphical workflow designer, or on e-signature integration. 5 6 8
The Mittelstand Owner
Approval management is genuinely built out — levels, queues, roles, rules on document type and keyword values, delegation for holidays, escalation of expired approvals and reminder notifications — plus an Accounts Payable application, a deep SAP connector with invoice handover, and REST and GraphQL APIs. We found no public information on DATEV or e-signature integration or webhook events, and workflow logic leans on configuration and Unity Script rather than a graphical no-code designer. 5 6 8
The Data Protection Officer
Approval workflows are documented end to end: levels, approvers, user rules, roles, queues, delegation, escalation of expired approvals, reminders, conditions on document type, keyword value or form fields, an Accounts Payable application, and CSV import and export of process definitions. The SAP ArchiveLink connector is documented with invoice transaction codes (MIRO, FB60, KO01, ME21N), early storage with workflow, mass archival and workflow web services, and REST, GraphQL and Workflow APIs are configurable. We found no public information on DATEV or Microsoft Dynamics connectors, graphical no-code modelling, or e-signature integration. 5 6 8
The Skeptic
Approval management is documented end to end — levels, queues, roles, rules on document type and keyword values, delegation, escalation of expired approvals, reminders, CSV import and export of processes — and the SAP ArchiveLink connector names its transaction codes with early and late storage via workflow, alongside a REST API, Workflow API, Forms API and GraphQL. Below the top because we found no public information on webhooks or events, e-signature integration, DATEV, or graphical modelling explicitly without code. 5 6 8
Search, retrieval & exit
Show reasoningHide reasoning
How this is scored
Finding documents again and taking them with you: full-text and metadata search, saved searches and mobile access, and whether documents, metadata, versions and audit trail can be exported in documented formats when the contract ends.
0 — No search and no way to get documents out again beyond opening them one by one in the product.
3 — Full-text or file-name search and single-document download; metadata filters and bulk export are basic or not described.
5 — Full-text and metadata search with filters, web and mobile access, and documents downloadable in bulk or in their original format.
8 — Saved searches and search across versions and attachments with permissions respected, bulk export of documents with their metadata (CSV, XML or similar) and versions in a documented structure, and an import path from other DMS or file shares named.
10 — The exit is designed in: a documented complete export with schema including the audit trail, export available self-service at any time, the post-termination retrieval window and data deletion stated, and archives stored in open formats so a successor system can take them over intact.
The GoBD Auditor
Full-text search with comparative and logical operators, a custom thesaurus, custom queries, searching in the web and Unity clients, and mobile access with offline document access are documented. We found no public information on saved searches, bulk export of documents with their metadata and versions, or any documented exit when the contract ends — the part an auditor needs when an archive moves. 7 8
The Records Manager
Full-text search carries a thesaurus, comparative and logical operators and load balancing; custom queries and keyword search sit alongside it, with web, Unity and mobile clients and offline document access documented. We found no public information on bulk export that keeps documents, metadata and versions together, or on any documented exit when the contract ends, which is the part I weigh most heavily. 7 8
The IT Integrator
Full-text search comes with comparative and logical operators, a configurable thesaurus and load balancing; custom queries and document search run in the Web, Unity and Mobile clients with deep links and offline access. We found no public information on saved searches, bulk export of documents with their metadata, or any documented exit path when a contract ends — the mass archiving shown is an import into SAP, not a way out. 6 7 8
The Mittelstand Owner
Full-text search with logical operators, a thesaurus and custom keyword queries is documented, with web, Unity and mobile clients and offline access. We found no public information on bulk export of documents with their metadata, a documented exit path, or an import route from an existing system. 7 8
The Data Protection Officer
A dedicated Full-Text Search module is documented with comparative and logical operators, a custom thesaurus and load balancing, alongside keyword-based custom queries, Web and Unity clients, and a mobile app with offline document access and deep links. We found no public information on saved searches, bulk export of documents together with their metadata and versions, or a documented exit path with post-termination retrieval and deletion. 6 7 8
The Skeptic
Full-text search is taken seriously — comparative and logical operators, a configurable thesaurus, load balancing — with custom queries, web and Unity clients, mobile access and offline document access. The exit half is silent: we found no public information on bulk export of documents with metadata and versions, saved searches, or a documented export structure, and the only export documented is of approval process configuration, not of documents. 5 7 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and its owner are, where documents and their metadata are stored and processed in the cloud edition, and who the subprocessors are — including any AI provider that reads document content. Independently sourced by the sovereignty pipeline.
0 — Proven non-EU on every dimension the evidence covers: non-EU contracting entity and non-EU storage of documents, with no EU or on-premises option stated.
3 — One European element proven: an EU contracting entity, EU data centres for the cloud edition, an on-premises edition, or a published DPA, with the rest of the chain unstated.
5 — EU contracting entity and EU data centres stated for the cloud edition, or an on-premises edition, with a DPA offered; the subprocessor chain (hosting, AI processing, support) is unstated or partly non-EU.
8 — EU entity, documents and metadata stored in named EU data centres, subprocessor list with locations published, AI processing location disclosed, an on-premises or private-cloud option offered, and certifications (ISO 27001, BSI C5) published.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every processing location and subprocessor European, customer-controlled keys or on-premises operation available, and certifications with their scope published.
The GoBD Auditor
The captured pages are product documentation only; installation guides for OnBase Mobile and the CPI Proxy imply that components run on customer-operated servers, but the pages never state a deployment model in so many words. We found no public information on the contracting entity's jurisdiction, on where documents and metadata are stored or processed, on the subprocessor chain, or on a data processing agreement. 6 8
The Records Manager
The one dimension the pages bear on is deployment: installation guides imply customer-operated servers, without stating a deployment model in those words or saying whether a cloud edition exists. The contracting entity's jurisdiction, where documents and metadata are stored, the subprocessor chain and a data processing agreement are unknown from the captured pages. 6 8
The IT Integrator
The captured pages prove very little: installation guides imply customer-operated servers, and capture OCR runs on Hyland's own engine rather than a named external AI provider. The pages state nothing on where documents and metadata are stored or processed in a cloud edition, on the contracting entity and its jurisdiction, on subprocessors, or on a data processing agreement, and they never use the words on-premises or self-hosted. 1 6 8
The Mittelstand Owner
The only element these pages begin to show is a customer-operated installation implied by the installation guides; the contracting entity's jurisdiction, where cloud documents and metadata sit, subprocessors and any data processing agreement are all unstated on the captured pages. Before a forty-person firm hands over its invoices, that chain has to be visible. 6 8
The Data Protection Officer
Installation guides imply customer-operated servers, the only sovereignty-relevant element I could find, and capture OCR runs on the vendor's own engine rather than a named third-party provider — though where it processes is not stated. We found no public information on the contracting entity's jurisdiction, data residency for any cloud edition, a published data processing agreement, or the subprocessor chain. Until a data processing agreement and processing locations are published, I cannot say where personnel files and health certificates would sit. 1 2 6 8
The Skeptic
The installation guides imply customer-operated servers — extracting installation files, installing a CPI proxy, disk groups and local databases — but the pages never state a deployment model or address whether a cloud edition exists, and the contracting entity's jurisdiction, data residency, subprocessors and any data processing agreement are all unstated in what we captured. One implied deployment fact is the entire proven picture; I score what is proven and no more. 6 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the cost of a given number of users, storage and modules — including cloud versus on-premises licensing, maintenance, implementation partner fees and price increases — from public pages alone.
0 — No public prices at all; every quote comes from sales or a partner.
3 — A public "from" price or one priced edition, per user or flat.
5 — Prices per user or per edition public for the main editions with the billing period stated and the main inclusions listed.
8 — Every edition and module priced publicly, storage limits and overage stated, on-premises licence and maintenance terms given, onboarding priced, and contract term and notice period published.
10 — Complete cost computability: a configurator or price list covering users, modules, storage and deployment model, partner implementation priced or bounded, and price-increase terms on a public page.
The GoBD Auditor
The documentation names licence tiers — Premier, Standard and Essential — and Simplified, Additional and Legacy licensing models, but quotes no figures. We found no public prices, billing periods, storage limits or inclusions, so a buyer cannot compute any cost from what we read. 1 3 8
The Records Manager
The pages publish licence tier names — Premier, Standard, Essential — and licensing models named Simplified, Additional and Legacy, but we found no public price figures on any page read. A buyer cannot compute a single cost from these pages alone; we found no public information on per-user or per-edition prices, storage, maintenance or implementation fees. 1 3 8
The IT Integrator
The documentation names licensing tiers Premier, Standard and Essential under Simplified, Additional and Legacy licensing, so a buyer knows the structure exists. We found no public price figures, billing periods, storage limits or inclusions on the captured pages, so no cost for a given number of users can be computed. 1 3 8
The Mittelstand Owner
The manuals name license tiers — Premier, Standard and Essential — under simplified and legacy licensing, but we found no public information on any actual price for users, storage or modules. Not one figure to plan with before a partner conversation. 1 2 3 8
The Data Protection Officer
The documentation names license tiers — Premier, Standard, Essential — and licensing models (Simplified, Additional, Legacy), which tells a buyer the structure exists. Beyond that we found no public information on prices: no per-user figure, no edition price, no billing period or inclusions. A buyer cannot compute any cost from the captured pages alone. 1 3 8
The Skeptic
The pages name licensing tiers — Premier, Standard, Essential, under Simplified, Additional and Legacy licensing — but not a single price, billing period or inclusion list appears in the captured pages, so a buyer can compute nothing and every figure would come from sales or a partner. Tier names are not prices, and asking the partner is not an answer. 6 8
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Installation guides imply customer-operated servers, but the pages never use the words 'self-hosted' or 'on-premises' and do not address whether a SaaS option also exists. |
1/1 pts | 6 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about OnBase
Is OnBase European?
Not determined: the vendor’s pages as captured do not say where OnBase is based.
Where does OnBase store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does OnBase have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to OnBase?
As of 19 Nov 2026, the panel rates AMAGNO (3.5/5), PaperOffice (3.5/5) and Doxis (3/5) highest among the other 27 Document Management (DMS) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is AMAGNO (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: OnBase alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting options. Installation guides imply customer-operated servers, but the pages never use the words 'self-hosted' or 'on-premises' and do not address whether a SaaS option also exists.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 6 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Capture, OCR & indexing — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 2 Capture, OCR & indexing — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 3 Audit-proof archiving & retention — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 4 Audit-proof archiving & retention — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 5 Document workflows & integrations — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 6 Document workflows & integrations — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 7 Search, retrieval & exit — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →
- 8 Search, retrieval & exit — found from sitemap docs.hyland.com Checked 10 Nov 2026 Details →