Working on test systems
Your health records, held safely and read only on your say-so
Your hospital keeps your records safely off-site, but it cannot read them: the copy it holds is sealed.
Your doctor can read them because you said so, even while your own computer is switched off.
Change your mind, and the access stops.
Working on test systemsDesigned for: public services
Show what's asked for, and nothing else
Show you're over 18 without revealing your birthday. Answer the tax office's questions without opening
your whole file. You approve each answer, and each organisation gets the information it needs, rather
than the information it wants. No central directory, no universal identifier, nothing to trawl.
Designed for
Science across institutions, without giving up the lab
Imagine a collaboration on the scale of ITER or CERN: dozens of institutions, each running its own
experiments and building its own analysis. With Strands, every lab keeps its own systems, builds its
analysis from reusable pieces, and shares a chosen piece or dataset with a partner, not its whole
infrastructure. Partners plug what they've been given into their own work, and every grant can be
withdrawn.
Working on test systems: fleetsDesigned for: partners and staff
A company that runs as one, with partners it can trust
Every workstation, server room and office runs the same system, so there is one thing to learn, secure
and update, all from a desk. Install software only from publishers you've chosen to trust, and cut a
machine off the moment you stop trusting it. Give a supplier the one service they need. Let staff bring
their own identity to work, with the company's access ending when the job does.
Working on test systems
A household where you decide who knows what
Keep your medical self, your driving record and your gaming persona apart, with no way to link them
unless you choose to. The family's machines work as one, and each person stays in charge of their own.
Designed for
Sites, sensors and control rooms that react, not poll
Strands is built around events: work happens when something happens, instead of everything checking
constantly. That suits control rooms with many screens and inputs, and edge sites that need to respond
promptly and report only what matters.