[ Workshop sign-up ]

Run your own resilient, sovereign data storage infrastructure

A hands-on workshop at IOSP 2026.

[ The event ]

IOSP 2026

The Institute of Open Science Practices is a four-day working event in Leiden, Oct 12–15, 2026. It is free to join, and most of the time goes on building rather than talks. This workshop opens the Resilient Data & Sovereign Infrastructure track, one of four alongside Modular Research Components, VOWELS, and Funding Open Science & Open Source.

Signing up for this workshop also registers you for IOSP 2026.

Full programme · Register for the event only

[ The workshop ]

Build a sovereign data node as part of a resilient data cluster

We’re running a hands-on workshop where up to 20 participants each stand up their own sovereign data-archive server, link them together to form a researcher-owned network, and load them with at-risk datasets from their own fields, in collaboration with the data-rescue workshop that follows directly after. There are two ways to take part:

  • Take-home Raspberry Pi (10 of the 20 seats) — we provide a Raspberry Pi with 200–500GB of storage, furnished by the IPFS Foundation’s Implementations Fund. A Pi is a silent computer the size of a small, delicious block of Vermont cheddar cheese. It is designed to stay on, draw minimal power, and serve as a maintenance-free node in a network. The 10 Pi nodes will link together to form Resilient Network #1.
  • Laptop node (everyone else) — you set up your personal laptop as a member of Resilient Network #2, using the same software, the same knowledge, and the same skills as the Pi network.
A Raspberry Pi 5 in its white case beside a block of Cabot Vermont sharp cheddar of roughly the same size
For scale: the node, beside the block of Vermont cheddar.

Both networks are practically and nearly technically identical, and both hold identical copies of the data rescued later in the track. The only difference is the hardware: a Pi can be set up as a single-purpose unit, and left on a desk or in a closet for years on end; a laptop is your laptop… it moves with you, experiences regular hibernations and resets, and is used for multiple purposes.

Because the Pi machines are limited, we ask anyone taking one to commit ahead of time to setting it up at home after the workshop. For most people home setup means plugging it in, and running a command or two on your laptop to get it set up. You will be shown these steps at the workshop, provided with detailed instructions to follow, assisted by robust agent-skills, and have open communication with the workshop facilitators for months after the workshop to help you set your Pi up at home. Once the Pi is running at home, it is hands-off from then on.

The laptop network will also have these things! Though they will be slightly different.

This workshop is limited to 20 participants. Pis will be distributed based on sign-up responses. While the room is not first-come-first-serve, earlier sign-up will be a consideration should the room be over-booked.

[ Sign-ups closed ]

Sign-ups for this workshop have closed.

Email contact@scios.tech to ask about a waitlist spot. You can still recommend a dataset for the network below; that stays open.

Recommend a dataset

What should this network be storing? Only the first question needs an answer.

Anything public that could vanish qualifies, whether a shuttered project’s archive, data on a retiring server, a collection whose funding ended, or a government dataset being taken down. A sentence is plenty.

A link if you have one, whether a landing page, a repository record, an FTP directory, or even a search result. Anything that points at where the data sits today.

Data nobody can fetch isn’t rescued yet, so this answer decides what we go after first. “Not sure” still tells us the pointer needs a person on it.

Anything you know helps. A bulk-download endpoint or API, the name of someone to ask, a licence that matters, a deadline before it disappears, or a warning that the server falls over above two connections.

A guess is fine; it tells us whether the current network can hold it.

Optional, but it helps us triage what to rescue first.

You

All optional. Leave it blank and the recommendation still counts. We ask for an email only so we can tell you when the data lands on the network.

For example “marine ecology”.

Note: every node from both networks broadcasts a small heartbeat (“I’m alive, here’s my free disk space, here’s the files I’m serving”), and the networks’ anchors run regular spot-checks that fetch a random piece of the archive from a random node, confirming the data is there and being served. You can see what this looks like on the live network dashboard. We record this data and will publish an aggregate study of how researcher-run infrastructure survives in the real world, including which type of network is still standing three months after the workshop. The study sees node uptime, free space, and whether each node still holds and serves the archive’s own datasets; it never sees your files, your browsing, or anything else on your machine.

Questions? Email contact@scios.tech.