Most digital archives are built for archivists. The problem is they're supposed to be for everyone else.
We're building with cultural workers, creators, and institutions. Get early access or partner on a pilot.
Partner with usMost digital archives are built for archivists. The problem is they're supposed to be for everyone else.
For decades, the UK cultural sector has been digitising. Photographs scanned. Documents indexed. Oral histories uploaded. On paper, the archive is open. In practice, the community it was built to serve can't find anything in it. The digital catalogue exists. The community bounces off it and leaves.
The failure is rarely technical. It's structural. Community archive software is designed around the needs of curators and information professionals: people who already know how an archive is organised, what the controlled vocabulary looks like, and which collection to search first.
When a community can't find itself in an archive, it stops looking. And when it stops looking, the archive quietly ceases to matter.
Consider a Windrush heritage group in south London that has spent years gathering testimonies, photographs, and handwritten letters from community elders. They need somewhere to put it all. The digital archive software they can actually afford is either too basic to handle the nuance of their collection, or too complex to operate without a dedicated archivist on staff.
The more sophisticated platforms are priced for institutions: museum IT budgets, university libraries, national collections. Community organisations don't have those resources. So the material sits on a hard drive, or gets handed over to a larger institution that digitises it and then controls access to it. The community contributed the history. Someone else holds the keys.
This is not a fringe case. It is the recurring pattern, across community organisations, cultural venues, and grassroots heritage projects across the UK. And it raises an uncomfortable question: when a digital archive is built for a community but governed by an institution, who does it actually serve?
Most archive search is keyword-based. You type a word, the system finds documents that contain that word. This sounds reasonable until you realise communities don't always know the right words. A family looking for records of their grandmother's work in the garment trade might search "Caribbean seamstresses in Hackney" and find nothing, even if the archive is full of relevant material filed under terminology a curator chose decades ago.
Semantic search changes this fundamentally. Rather than matching what you typed, it understands what you meant: surfacing material by concept and intent, not by literal string. A community member searching in plain language can find material that keyword search would bury. This isn't a marginal improvement. It's the difference between an archive that works and one that gatekeeps.
The catch is that semantic search has historically required significant infrastructure. Which is to say, it has been available to large institutions, not to the community organisations that need it most. Until now, that gap has been almost impossible to close with community budgets.
Material gathered from communities, rehoused somewhere the originating community can no longer easily access, recatalogued in institutional terms, used in applications the community never consented to. The pattern is well-documented and it is still happening. Archives built on that legacy carry the weight of it, regardless of current intentions.
Communities have good reason to be wary of institutions that hold their history. Extraction isn't a historical artefact: it's a current practice.
When a digital archive can't show you who contributed something, why it was collected, and who controls access to it, trust breaks down. And trust, once broken around heritage and history, is very difficult to rebuild.
Citable provenance isn't just a metadata question. It's an accountability structure. An archive that tells you where something came from, who contributed it, and what conditions govern its use is an archive that can be trusted. One that can't is asking communities to take institutional good faith on faith. Most communities have learnt not to.
The most misleading word in heritage technology is "preservation." It implies neutrality. But every decision about what gets preserved, how it is described, and who can access it is a political decision. Archives governed by institutions will reflect institutional priorities, however well-meaning those institutions are.
Community-controlled archives aren't a nice-to-have feature. They are a structural requirement if an archive is going to mean something to the people whose history it holds. This means communities deciding what goes in. Communities describing their own material, in their own terms. Communities setting access conditions. And communities retaining the right to say no: to extraction, to datafication, to institutional use cases that were never theirs.
Control and access are not the same thing. Institutions have been offering communities access to their own history for a long time. That's not the same as giving them ownership of it.
The Black Cultural Archives in Brixton is one of the UK's most significant repositories of Black British history, and it has spent years navigating exactly these tensions. Balancing professional archival practice with genuine community access is not straightforward, and the institution has had to be honest about where those two imperatives diverge.
Newer community-led projects are experimenting with participatory models: communities describing their own material, setting their own access terms, contributing ongoing context. Rainforest Studio's own Threads of Memory project takes this further, using RAG technology to let communities actually talk to their own history, not just browse it.
From the ecosystem · Studio Note
How RAG technology makes cultural archives come alive
Your grandmother's voice is recorded. Your community's textile patterns are photographed. All of it exists. None of it is findable.
These are meaningful experiments. But most are being done by working around existing community archive software, not with it. The sector knows what good looks like. The platforms haven't caught up with the ambition.
Before a community invests time, material, and trust in building a digital archive, there are questions it should be able to demand answers to: not as a buyer's checklist, but as a baseline expectation.
Can the community search the archive in its own language and its own terms, without knowing how a curator has organised it? Does provenance appear in every record, so the community's contributions stay credited and traceable? Who controls what goes in, and who has the right to correct how material is described? And is the platform built for community governance from the start, or retrofitted to allow it?
These are not technical questions. They are questions about power and ownership. A community building an archive deserves clear answers to all of them.
The alternative is a Living Archive: built on principles that put communities in control from the ground up.
From the ecosystem · Studio Note
What Is a Living Archive? Meaning, Examples & Why It Matters
Most archives are beautifully organised cemeteries. A Living Archive is something else entirely.
From the ecosystem · Studio Note
Living archives vs traditional digital archives: what's the difference?
Most digital archives are graveyards with good lighting. A living archive is something different entirely.
If you're building a community archive, or rethinking one that isn't working the way it should, we'd love to hear from you.