ResourceSpace · Open-source DAM
ResourceSpace
Buy it if
You have server administration capability in-house, your library is a few hundred thousand assets or fewer, and an open licence is a genuine requirement rather than a preference.
Do not buy it if
Nobody on your team can debug a broken database migration by hand, or your library is approaching a million-plus assets and you need guaranteed support for the tuning that requires.
Quote it against
Piwigo and Phraseanet for the same open-licence, self-hosted category; ResourceSpace's institutional footprint (Oxford's four museums) suggests comparing it against Orange Logic Cortex for GLAM-sector procurement specifically.
What users actually say
Too thin to quantify on commercial review sites — about 21 reviews on Capterra, last dated 11 Mar 2021. The real evidence base is the vendor-hosted user Google Percentages are the share of reviews raising each theme, not a rating.
Major-version upgrades break things
The single loudest and best-evidenced recurring problem. Reports include a white screen of death moving 10.3 to 10.4, a failed 9.7 to 10.3 upgrade, permissions breaking after 10.7, missing or mis-sized previews post-upgrade, and a migration script (populate_nodes_pre_v10.php) erroring outright. An August 2026 thread about the 11.0 install shows a user stuck with a regenerating lock file, traced to a corrupted resource table — fixed by hand-running SQL through phpMyAdmin. Vendor staff (Dan Huby) answer in-thread, which functions as the de-facto support channel.
What to do about it
Before any major-version upgrade, take a full database and file backup and test the upgrade on a staging copy first — do not run it against the production install directly.
Fragile chain of external binary dependencies
Preview generation depends on ImageMagick, Ghostscript, FFmpeg and Inkscape, each versioned separately from ResourceSpace itself, and version mismatches are a constant source of failure: ImageMagick 7.x installed while the app expects 6.9.x, HEIC needing IM7 specifically, no native preview support for CorelDRAW or Affinity files, install-check reporting an archiver as failed when it is present. PHP 8.1/8.2 compatibility issues (missing php-sodium, gd built without JPEG support) compound this on newer server stacks.
What to do about it
Before deploying, verify exact ImageMagick/Ghostscript/FFmpeg versions against the ResourceSpace compatibility notes for your target release, not just that the binaries exist.
Performance ceiling around one million assets, and it is the app layer, not the database
The clearest data point: a Spanish broadcaster running 1.083 million photos, growing roughly 10,000 a month, on 32GB RAM with a 24GB MariaDB InnoDB buffer pool, reported PHP's array_pad() hitting a 1,048,576-element ceiling on large result sets, roughly seven seconds to page between resources, and a query that ran in 12 seconds at the MariaDB console taking 30 seconds through the app — pointing at the Apache/PHP layer rather than the database as the bottleneck. Guidance given was to lower the default 200,000-row max_results setting and upgrade the PHP version. It reaches large libraries but needs deliberate tuning to get there.
What to do about it
If your library will approach a million assets, budget time for PHP-layer tuning (max_results, buffer sizes) rather than assuming database hardware alone will keep it fast.
You are largely your own support unless you pay for it
A representative case: a August 2026 thread from someone migrating 1.45 million assets / 15TB off Extensis Portfolio, asking specific questions about a hybrid storage architecture and real-world MariaDB search performance at that scale, got zero replies and six views. Day-to-day configuration questions are answered promptly by vendor staff in the group, but open architectural questions at scale are not reliably answered by the community. Real Story Group's independent 2014 evaluation made the same point structurally: free and usable for simpler scenarios, but extending it seriously needs in-house programming talent or paid third-party help, and the small core team means slower innovation than commercial competitors.
What to do about it
For anything beyond a standard single-server deployment, budget for a paid support contract or an in-house developer rather than counting on the community forum for architecture-level questions.
Distribution and packaging read as dated to technical evaluators before they even install it
ResourceSpace still distributes via SVN rather than Git in 2026, and a 2023 Hacker News thread shows a technical evaluator citing exactly that, plus a dated website and no public product demo, as reasons to be put off before ever running the software — despite suspecting the product itself was fine. Separately, the community itself now actively warns people away from the official Bitnami image, calling it unmaintained; one Reddit report described the Bitnami OVA shipping with a disk far too small for real use, and a 2015 poster said the Bitnami/Google Cloud VPS setup effectively demanded full-time IT skills to run.
What to do about it
Skip the Bitnami image; install from the documented SVN/source route directly, and budget an afternoon for first-run friction rather than expecting a five-minute setup.
Free of licence fees is not free of operating cost
The clearest independent evidence — a 1.45-million-asset migration question that got zero replies after six views, and an August 2026 upgrade that required hand-editing the database through phpMyAdmin to recover — is that ResourceSpace's real cost shows up as your own team's time during upgrades and at scale, not as a line item you can see before you commit.
Budget a named person's ongoing time, not just server cost, before choosing self-hosting over a paid alternative.
Checkable facts
Sources
- Pricing page states there is no annual software licence fee and lists four hosted tiers by user ceiling without amounts checked 2026-08-06 — ResourceSpace pricing page
- 21 reviews on Capterra, average 4.3, most recent dated 11 March 2021 checked 2026-08-06 — Capterra
- Upgrade failures (10.3→10.4 white screen, 9.7→10.3, 10.7 permissions, 11.0 corrupted resource table) recur across 2024–2026 checked 2026-08-07 — ResourceSpace Google Group
- 1.083M-photo deployment hitting a PHP array_pad() ceiling and an app-layer (not database) performance bottleneck checked 2026-08-07 — ResourceSpace Google Group, thread R3Df9jG7fg4
- 1.45M-asset migration question from Extensis Portfolio, zero replies, six views checked 2026-08-07 — ResourceSpace Google Group, thread F6q6UDBUpuQ
- Higher-ed self-hosted-to-cloud migration cost discussion checked 2026-08-07 — ResourceSpace Google Group, thread _rwENKjquYw
- SVN distribution, dated website and absent public demo cited as reasons for evaluator hesitation checked 2026-08-07 — Hacker News
- Independent evaluation: usable free for simple scenarios, needs in-house or paid development talent to extend seriously checked 2026-08-07 — Real Story Group
- Live in production at all four Oxford museums as of the DAMS project, Natural History Museum went live December 2025, run as vendor-managed SaaS checked 2026-08-07 — Oxford University GLAM
- Bitnami OVA ships with a disk size too small for real use; community advises against the Bitnami image checked 2026-08-07 — Reddit r/selfhosted (search snippet, page not directly readable)