whats-best.ai
Search Sign in

Document Management (DMS)

agorum core

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by agorum Software GmbH · www.agorum.com

Report an error on this page Is this your product? →

Link to this page

agorum core: AI-assisted analysis on whats-best.ai agorum core: AI-assisted analysis on whats-best.ai (dark)

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.

agorum core at a glance

Vendor
agorum Software GmbH
Headquarters
Not stated on the vendor’s pages as of 13 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 13 Oct 2026
Free plan
Not stated on the vendor’s pages as of 13 Oct 2026
Panel verdict
The AI panel rates agorum core 2.5/5, the mean of 6 judges. agorum core is an open-source-based document management system from agorum Software GmbH in Ostfildern, Germany, offered on premises or in agorum Cloud. how scores are made
As of
Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources

agorum core alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

Knows the DMS ends up holding personnel files, health certificates and customer contracts in one place. Asks where the cloud edition stores them, which AI provider reads them during capture, who the subprocessors are, and how GDPR deletion is reconciled with retention duties.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Panel median The Data Protection Officer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Data Protection Officer
Capture, OCR & indexing 3 of 5 2.5 of 5
Versioning, permissions & audit trail 3 of 5 3 of 5
Audit-proof archiving & retention 2.5 of 5 2.5 of 5
Document workflows & integrations 3.5 of 5 4 of 5
Search, retrieval & exit 2 of 5 2 of 5
European sovereignty 1 of 5 1.5 of 5
Pricing transparency 1 of 5 1 of 5

Capture, OCR & indexing

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 — Manual upload only; no OCR, no metadata beyond file name and folder.

3 — Upload, drag-and-drop and scan import with OCR mentioned, but indexing is manual and no word on email intake or e-invoice formats.

5 — Scanner, email and folder intake, full-text OCR, document types with metadata fields, and automatic extraction of common fields (date, sender, amount) documented.

8 — AI- or rule-based classification and field extraction with confidence and 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.

Report an error

The Data Protection Officer

Scanner and email intake into a central inbox, server-side OCR with language packs, barcode types and searchable-PDF output, plus a keywording-and-filing module, are documented, and the Mistral OCR tool is described for digitising scans and extracting structured invoice data. We found no public information on classification with confidence values and a validation step, on XRechnung and ZUGFeRD being read as structured data, or on Microsoft 365 intake. The OCR route runs through Mistral's API under a customer-supplied key, and where that processing happens is not stated. 5 6 10 9

Report an error

Versioning, permissions & audit trail

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 — Files overwrite each other; rights only at folder level or not described; no log of who did what.

3 — Version history and folder permissions exist, but no check-out, no record-level rights and no documented audit log.

5 — Version history with restore, check-in and check-out, roles and groups with document-type or record-level rights, and an audit log of changes documented.

8 — Metadata-driven permissions (by department, client or confidentiality), 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.

Report an error

The Data Protection Officer

Automatic versioning with restore, check-in comments, one version per locked edit session and a checkout module, a documented audit trail of every create, change and delete with user and timestamp, and two-factor and single sign-on give me a defensible who-did-what record for personnel files. The captured pages describe permissions only as folder and workflow ACLs, and I found no public information on logging of reads, exports or administrators' own actions, on directory sync with Entra ID or LDAP, or on field-level and need-to-know rights for HR or legal records. 7 8 2 11

Report an error

Audit-proof archiving & retention

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 — No statement on archiving, retention or GoBD.

3 — "GoBD-konform" or "revisionssicher" claimed with no certificate, no description of how immutability is achieved and no retention settings documented.

5 — Archived documents documented as unchangeable, retention periods configurable per document type, deletion after expiry, and a sample Verfahrensdokumentation or GoBD guidance offered.

8 — An auditor's report (IDW PS 880 or comparable) published or named with its scope and date, WORM or equivalent storage described, 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.

Report an error

The Data Protection Officer

Documents marked audit-proof are documented as unchangeable, undeletable and immovable for a chosen number of years, the original version is permanently protected, and a sample Verfahrensdokumentation is offered with the project effort put at two to six consulting days. We found no public information on an auditor's report such as IDW PS 880, on logged deletion after retention expiry, on legal hold, on Z1–Z3 tax-audit export, or on how GDPR deletion is reconciled with retention duties for archived material. 9 10 7

Report an error

Document workflows & integrations

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 — No workflows; documents are stored and nothing else.

3 — A fixed approval or sharing step and a handful of named integrations, with no workflow designer and no API documentation.

5 — A workflow designer for approvals and invoice processing, tasks with deadlines and substitutes, Microsoft 365 or Outlook integration, and a documented REST API.

8 — Graphical workflow modelling without code, invoice workflow with ERP or DATEV handover documented, connectors for named ERP systems (SAP, Microsoft Dynamics, DATEV) with their scope, 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.

Report an error

The Data Protection Officer

The workflow editor is documented in operational depth — versioned definitions where the old version stays runnable, subworkflows, testing, deployment, process overview and log inspection — alongside task, approval and checkout modules, DATEV invoice handover with mapped ledger types, named SAP and Odoo connectors, e-signature via inSign, and folder structures invokable per API. The captured pages give no public information on process reporting with throughput times, on an API reference with rate limits and a sandbox, or on the scope of the ERP connectors. 11 2 12 8

Report an error

Search, retrieval & exit

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 — Folder browsing only; no export beyond downloading single files.

3 — Full-text search exists, but no metadata filters, and bulk export is undocumented or only on request.

5 — Full-text and metadata search with filters and saved searches, mobile or web access, and bulk export of documents with their metadata (for example CSV or XML) documented.

8 — Search across versions and attachments with permissions respected, export of documents in original format with metadata, versions and audit trail 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, 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.

Report an error

The Data Protection Officer

Full-text, metadata and tag search on Solr with its own query syntax is documented, and a migration export plugin is described for moving data from one agorum core system into another. That export's formats and scope — whether metadata, versions and the audit trail travel with the documents — are not documented, and I found no public information on saved searches, mobile access, an import path from other DMS or file shares, or export formats a successor system could take over intact. 14 13

Report an error

European sovereignty

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 — Non-EU contracting entity, no statement on where documents are stored, and subprocessors unnamed.

3 — An EU entity contracts, but the cloud edition runs on a non-EU-controlled hyperscaler without a stated safeguard, or the subprocessor list is absent.

5 — EU contracting entity and EU data centres stated for the cloud edition, with a DPA, but significant parts of the chain (hosting, AI processing, support) are non-EU-controlled without a stated safeguard.

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.

Report an error

The Data Protection Officer

On-premises operation and an open-source product developed in Germany give buyers a way around the cloud question, but the captured pages make no statement on where agorum Cloud stores documents and their metadata, name no subprocessors, and publish no certifications or data-processing agreement. Meanwhile document content demonstrably reaches third-party AI: OCR runs through Mistral's API under a customer key, and ALBERT can be attached to OpenAI or Azure OpenAI models, with no processing location stated for any of it. 1 2 6 8

Report an error

Pricing transparency

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 "from" price or a single edition priced, but modules, storage, maintenance and partner implementation are unstated — the real cost is unknowable.

5 — Editions priced per user or per month, but at least one commonly needed cost (storage, archiving or workflow module, maintenance percentage, onboarding) is missing or "on request".

8 — Every edition and module priced publicly, storage limits and overage stated, on-premises licence and maintenance terms given, 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.

Report an error

The Data Protection Officer

The pricing page names its billing dimensions — fixed or concurrent users, volume and traffic, monthly ALBERT token volume, a reader module with monthly quotas from 100 documents — and states that cloud maintenance, backup and 50 GB volume are included, but no euro figure appears in the captured pages and module prices are described as heavily project- and volume-dependent. A buyer cannot compute a given setup's cost from public pages, and we found no public information on storage overage prices, on-premises maintenance terms, or contract term and notice period. 2 4 10

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Questions about agorum core

Is agorum core European?

Yes. whats-best.ai classifies agorum core as EU-Made.

Where does agorum core store data?

Not stated on the vendor’s pages as of 13 Oct 2026.

Does agorum core have a free plan?

Not stated on the vendor’s pages as of 13 Oct 2026.

What are the best alternatives to agorum core?

As of 15 Oct 2026, the panel rates AMAGNO (3/5), Doxis (3/5) and EASY Archive (2.5/5) highest among the other 14 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: agorum core alternatives.

Where this could be wrong

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.

Do you know more about agorum core? Tell us Report an error on this page

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.agorum.com Checked 13 Oct 2026 Details →
  2. 2 Pricing page www.agorum.com Checked 13 Oct 2026 Details →
  3. 3 Privacy policy www.agorum.com Checked 13 Oct 2026 Details →
  4. 4 Legal notice www.agorum.com Checked 13 Oct 2026 Details →
  5. 5 Capture, OCR & indexing — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  6. 6 Capture, OCR & indexing — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  7. 7 Versioning, permissions & audit trail — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  8. 8 Versioning, permissions & audit trail — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  9. 9 Audit-proof archiving & retention — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  10. 10 Audit-proof archiving & retention — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  11. 11 Document workflows & integrations — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  12. 12 Document workflows & integrations — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  13. 13 Search, retrieval & exit — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →
  14. 14 Search, retrieval & exit — found from sitemap www.agorum.com Checked 13 Oct 2026 Details →