Contxt vs. Gallery Systems (TMS): features and operation compared
TMS has a substantial museum community and mature tools for loans, exhibitions and collection documentation. TMS provides established museum operations and eMuseum publishing; Contxt connects collection and curatorial workflows. Compare publication, licensing, data exchange and the work required from your team.
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. |
| Gallery Systems (TMS) | Collection records, people, media, loans and exhibitions; eMuseum for public publishing. | Proprietary licensing quoted by configuration and concurrent users. Scope hosting and export services. | Established loan, exhibition and documentation procedures. Clarify automated research and cleanup. | Getty vocabulary support documented. Clarify the required authority sources and automated matching. |
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.
Gallery Systems (TMS)
TMS has a substantial museum community and mature tools for loans, exhibitions and collection documentation.
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
TMS links collection records, people, media and museum operations. Public publication runs through eMuseum, with Prism transferring data between the products. Contxt’s proposition is one connected collection and editorial environment that also publishes the approved content.
Licensing & operation
Gallery Systems quotes according to the proposed configuration and concurrent users. This makes the scope of licences and services part of procurement. Contxt publishes hosted rates and has announced its MIT core modules. Ask both suppliers for a complete exit export.
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
Mature loan and exhibition workflows are a real TMS strength. The reviewed material does not establish the complete research, deduplication and record-linking automation defined here. Compare which of those steps staff perform themselves and which the proposed system automates.
Authority data & vocabularies
TMS documents standards and Getty vocabulary support. That does not establish automatic matching across GND, Wikidata and Getty ULAN. Contxt describes that cross-authority workflow with staff approval; request a demonstration using ambiguous names and inspect the stored identifiers.
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
Gallery Systems (TMS)
Include eMuseum, integration work and concurrent-user licensing in the TMS proposal. Compare those responsibilities with the publishing and automation included in the proposed Contxt service.
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 Gallery Systems (TMS) strongest?
TMS has a substantial museum community and mature tools for loans, exhibitions and collection documentation.
How does Contxt differ from Gallery Systems (TMS)?
TMS provides established museum operations and eMuseum publishing; Contxt connects collection and curatorial workflows. Compare publication, licensing, data exchange and the work required from your team.
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