← Resources / Buyer’s guide2026 edition

Contxt, CatalogIt and CollectionSpace: Three Ways to Manage a Museum Collection

CatalogIt combines accessible subscriptions with mobile cataloguing and included public publishing. CollectionSpace offers available open-source software with managed or self-hosted deployment. Contxt brings Swiss hosting and an emphasis on automated data work and multilingual publishing. The right choice depends on which of those differences matters to your institution.

01 / At a glance

Three distinct operating models.

Scroll horizontally on smaller screens.

Contxt vs. CatalogIt vs. CollectionSpace: Museum Software Compared in 2026
Decision criterion	Contxt	CatalogIt	CollectionSpace
Institution fit	Small–large	Small–mid-size; assess more complex requirements	Small–large, with an appropriate support arrangement
Pricing	Per editing user; enterprise by quote	Published museum subscriptions; add-ons	Free source code; hosting and services cost extra
Authority support	Automated reconciliation suggestions described	Controlled terminology; Getty terms and identifiers	Authority vocabularies and local terms
Automated reconciliation	Vendor-described; staff approval	Equivalent native workflow not established	Equivalent native workflow not established
Public publishing	Integrated multilingual publishing described	HUB included; separate language values not currently supported	Public Browser or API; multilingual implementation to confirm
Hosting location	Zurich; backups at a second Swiss location	Managed cloud; confirm countries for records and backups	Depends on the chosen host; self-hosting available
Open source	Public release pending	No; no self-hosted edition	Yes; application repository uses ECL-2.0

Institution size is an assessment, not a capacity limit. Authority vocabularies, stored external identifiers and automated reconciliation are different features. Prices and implementation requirements should be checked against the actual collection and team.

02 / Institution fit

Choose the operating model your team can sustain.

CatalogIt: affordable shared cataloguing

CatalogIt is a credible museum option, not just a personal inventory tool. Its desktop and mobile access suit teams documenting objects where they are stored. The included HUB provides a straightforward way to publish selected records.

CatalogIt deserves particular attention where the priority is a usable shared catalogue at a modest subscription cost. Ask staff to photograph an object, document its location, connect it to a person and publish an approved entry. Test your specialist fields before assuming that an accessible interface covers every requirement.

CollectionSpace: open source with a choice of support

CollectionSpace can be operated by the institution or supplied through managed hosting. Lyrasis recommends its hosted services for organisations that want help with operation and maintenance. An in-house server team is therefore not a universal entry requirement.

Available source code is a material advantage if the institution needs control over modifications and its operating partner. It still needs somebody responsible for configuration, upgrades, integrations and user support. Compare a managed proposal with a realistic internal operating budget, not with an assumption of free staff time.

Contxt: connect data maintenance with publication

Contxt’s fit spans small through large institutions. It is worth testing when inconsistent names, duplicate records and repeated translation work absorb more staff time than basic data entry. Its appeal rests on connecting those tasks to the collection and the material used to interpret it.

That is a different spending decision from choosing the lowest subscription. Ask whether the demonstrated workflow saves enough work to justify the recurring cost for your editing team. A small museum with straightforward records may gain more from CatalogIt’s pricing; an institution prioritising available source code may prefer CollectionSpace.

03 / Data & publishing

Look beyond a yes-or-no feature checklist.

Authority files and data hygiene

CatalogIt’s museum feature list includes controlled terminology and capturing Getty terms and identifiers. CollectionSpace documents authority vocabularies. Both deserve credit for structured documentation; neither fact alone proves automatic matching of ambiguous names against GND, SIKART, Getty ULAN and Wikidata.

Contxt describes automated reconciliation and cleanup suggestions with staff approval. Give all three the same duplicate person, uncertain attribution and inconsistent date. Check source evidence, preservation of local knowledge and the ability to leave a question unresolved. Do not turn an unverified automation feature into a blanket claim that a competitor cannot use authorities.

Public access and language versions

Public publishing is available in all three approaches. CatalogIt includes its HUB; its FAQ says fields can contain text in different languages but do not currently store separate language values. That is a concrete limitation to examine for a multilingual catalogue.

CollectionSpace’s Public Browser is a WordPress plugin that can be self-hosted or configured and hosted by Lyrasis. Contxt describes integrated multilingual publishing. For each, test a reviewed translation, a visitor’s language switch, search and the handling of an untranslated field. Identify who maintains the public site and what happens when a source record changes.

Migration and the next export

A simple spreadsheet import can still lose relationships or flatten repeated values. Include images, alternate names, accession numbers and restricted fields in the trial. Require a report of anything the new system could not represent.

Then export the sample again. Can a receiving system identify each object, person and relationship? Are media files and their rights information included? Available source code can help with custom extraction, but it does not eliminate the need to test it. Hosted convenience does not eliminate that need either.

04 / Hosting & cost

Make hosting and the full operating cost visible.

Where collection records and backups live

Contxt’s hosted platform specifies Zurich infrastructure and backups at a second Swiss location. This is a clear consideration for museums seeking Swiss hosting.

CatalogIt operates a managed cloud service and does not offer self-hosting. Its reviewed FAQ describes geographically separated data centres but does not name their countries. Request the locations explicitly. With CollectionSpace, the location depends on your host; self-hosting lets the institution select the infrastructure and take responsibility for it. Ask about backup locations, support access and any external processing in every proposal.

Use the published prices accurately

CatalogIt’s paid museum plans list US$540–960 per year, with ten users included and differing record and storage allowances. Additional users are available, so ten is not a hard team limit. Its included HUB should be distinguished from the separately priced API and website integration add-on.

Contxt’s SaaS pricing is CHF 135 per editing user per month billed annually, or CHF 150 billed monthly, excluding VAT. Read-only guests are free. Compare currencies, editor numbers and actual allowances before calculating the difference. CatalogIt can have a substantial subscription advantage for a small team.

Open source removes licence cost, not operating work

CollectionSpace’s application repository is available under ECL-2.0. Hosting, migration, configuration and training still need a budget. Contxt’s public open-source release remains pending and should not be counted as available on the same basis.

Choose CatalogIt when its standard functionality and price meet the requirement. Choose CollectionSpace when available source code and operating choice carry the greatest weight. Consider Contxt when its demonstrated data and multilingual publishing workflows, together with Swiss hosting, justify the cost. Write down those priorities before a polished demo changes the discussion.

05 / Common questions

Does CatalogIt include a public online catalogue?

Yes. CatalogIt includes HUB publishing in its subscriptions. API access and integration into an institution’s own website are separate add-ons.

Is CatalogIt limited to ten users?

No. Paid museum plans include ten users, and additional users can be purchased. Compare the current user, record and storage allowances for the selected plan.

Does CollectionSpace require our own server team?

No. CollectionSpace offers managed hosting through Lyrasis as well as self-hosting. The institution should still plan for data preparation, configuration and staff training.

Which of these products is available as open source?

CollectionSpace is available as open-source software; its application repository uses ECL-2.0. CatalogIt is proprietary. Contxt’s public open-source release is pending.

Which supports a multilingual online collection?

Contxt describes integrated multilingual publishing. CatalogIt currently lacks separate stored language values. CollectionSpace’s public presentation can be implemented through its Public Browser or API; verify the required multilingual workflow.

Which provides Swiss hosting?

Contxt specifies Zurich infrastructure and a second Swiss backup location. CollectionSpace’s location depends on the chosen host. Confirm CatalogIt’s data and backup countries directly before treating it as a match for a Swiss hosting requirement.

Source documentation · Reviewed 8 September 2026