Contxt vs. Lucidea Argus: features and operation compared
Argus offers a configurable museum platform with an integrated public portal and connected multimedia content. Argus offers an integrated public portal and configurable museum workflows; Contxt connects collection and curatorial work. Compare relationships, editing, automation and operating scope.
Published by Contxt, one of the suppliers included. Based on the linked product documentation; this is not an independent product test or a ranking.
Approaches compared.
Scroll horizontally on smaller screens.
| Vendor / product | Collection & publishing | Licensing & operation | Workflows & automation | Authority data & vocabularies |
|---|---|---|---|---|
| Contxt | Objects, people, curatorial content and publishing in a connected platform. | SaaS with public pricing and open import/export. Core Open Source: Announced¹. | Research, deduplication and record-linking with staff review, according to Contxt. | Contxt describes automated suggestions for GND, Wikidata and Getty ULAN. |
| Lucidea Argus | Collection records, related content and an integrated public portal with live updates. | Proprietary; pricing on request; CSV import/export and API documented. | Configurable workflows, bulk search-and-replace, research requests and API imports. | Clarify external authority connectors, matching and review; scope is not established by the reviewed page. |
Products appear alphabetically, without scores or an overall ranking. Entries summarise the linked vendor documentation; they are not independent hands-on test results. Additional components and configuration are described without treating them as inherently inferior. “Clarify” identifies information to request from the supplier, not a proven absence of functionality.
¹ Core Open Source is announced. The public release and download are pending; no release date is confirmed. Hosted automation is not implied to be included in every core module. Contxt pricing and release status
Product profiles and requirements.
Lucidea Argus
Argus offers a configurable museum platform with an integrated public portal and connected multimedia content.
Questions for the shortlist
Start with the work your museum needs to do: document collections, manage loans and exhibitions, maintain relationships, publish information and exchange data. The four areas below help structure a shortlist. They are not a complete requirements catalogue: conservation, rights, accessibility, security, migration and support also belong in the assessment.
Collection work, data and operation.
Collection & publishing
Argus describes collection records, related content and a public portal in one platform, with live updates rather than exports or connectors. It deserves credit on this pillar. Compare its editorial relationships with Contxt’s objects, people and reusable curatorial content.
Licensing & operation
Lucidea documents CSV import/export and an API. The product is proprietary and the reviewed page asks prospective customers to contact sales rather than providing a tariff. Contxt publishes hosted pricing and has announced its MIT core; licence openness remains distinct from useful data access.
Contxt offers a hosted service and open import/export. Core Open Source is announced, with core modules intended for release under the MIT licence. Once released, the core will enable independent operation and extension; managed automation and hosting are part of the SaaS offering.
Workflows & automation
Argus documents configurable workflows, bulk search-and-replace, research requests and API imports. These are practical automations. The reviewed material does not establish native automatic deduplication and research matching with the full review process used in this comparison.
Authority data & vocabularies
The Argus product documentation reviewed does not describe automated GND, Wikidata and Getty ULAN matching. Contxt explicitly names these authorities. Ask for the connectors, provenance and ambiguity handling included in each offer; absence of documentation is not proof of a technical limitation.
Use the same demonstration brief for every supplier
Give each supplier a representative object, related people, an image, a curatorial text and a sample loan. Ask the team to import and link them, handle a duplicate, prepare a publication and export the result. Record which steps are included, which need configuration and which remain manual. Include permissions, accessibility and staff training in the discussion.
Compare responsibilities as well as capabilities
Lucidea Argus
Ask Lucidea to scope the portal, configuration, integrations and ongoing service. An integrated portal can reduce recurring publication work; compare the data tasks and editorial responsibilities that remain.
Compare total costs over the same period and for the same scope: software, editing and read-only users, hosting, migration, training, interfaces, public access, maintenance and support. Published prices are a starting point; quotations can cover different services. Open-source licensing does not remove operating costs, and a bespoke quote does not establish that a product is more expensive.
For each offer, establish hosting location, access rights, backups, updates, service levels and a usable export for a later move. A hosted product and self-hosted software assign these responsibilities differently. Have suppliers state which responsibilities remain with your institution.
Choose by requirements, not by institution size alone
Document what every shortlisted system meets, what needs configuration and what remains unresolved. Request a written scope for migration, publishing, interfaces, support and ongoing operation. The most suitable choice is the one your team can use and maintain with confidence.
Common questions
Where is Lucidea Argus strongest?
Argus offers a configurable museum platform with an integrated public portal and connected multimedia content.
How does Contxt differ from Lucidea Argus?
Argus offers an integrated public portal and configurable museum workflows; Contxt connects collection and curatorial work. Compare relationships, editing, automation and operating scope.
When will the MIT core be available?
Core Open Source is announced, with core modules intended for release under the MIT licence. No public release date is confirmed. Open import/export and the hosted service are available; the pricing page will link to the source when it is published.
Does “not documented” mean a competitor cannot do it?
No. It means the sources reviewed do not establish the complete criterion. Configuration, optional products or newer releases may add capabilities. Ask for the specific workflow and its licensing in the written proposal.
Sources and product documentation · Reviewed 9 September 2026