BrainboxWhat else you could
do with it
Brainbox isolates workloads — not only AI agents. A cell is a small machine you can throw away, and that turns out to be useful far outside software. Sorted by field, so you can find yours.
Read this first. None of these describe an existing installation. They are ideas, collected from documented problems — and where one needs something the box does not have yet, it says so.
Almost all of them are the same three moves: an airlock (open someone else's material in a machine you throw away), two worlds (the sensitive machine never goes online; the internet happens in cells), and a workshop floor (old hardware becomes a queue that grinds through long jobs).
Run other people's code. Share data without giving it away.
Reviewer cells for artifact evaluation
Reviewing an artifact means running a stranger's code — a leap of faith on your own laptop. A cell with its own kernel, its own time budget and no network is the honest way, and long runs queue across the fleet. This is the pattern behind Does It Reproduce? today.
For: artifact evaluation committees, reviewers, research groups
Missing: little beyond packaging.
The small data trust
A collaborator gets a cell that can see the data read-only with no way out to the network, and results leave only through a controlled channel. The UK builds physical SafePods with access control for this; below that threshold, people work with USB sticks and trust.
For: groups with sensitive cohorts, clinical collaborations, industry partners
Missing: the export approval step — four-eyes release and a log — which is what turns this from isolation into a trust arrangement.
Empower your science with AI-driven pipelines
The bottleneck in most labs is not ideas, it is the analysis: someone has to build the pipeline, and the queue for that person is long. Give an agent a cell with the data mounted and a real machine to work on, and it can assemble, run and document the analysis while you sleep — with every step reproducible, because the cell is the record. The wet lab keeps its hands; the dry lab stops being the rate limit.
For: groups without a dedicated bioinformatician, core facilities, PhD students inheriting an undocumented pipeline
Honest limit: an agent drafts and runs analyses — it does not replace the person who decides whether the result means anything. This is the workload Does It Reproduce? already runs at scale, so the mechanism is proven; the domain templates are not.
Keep the machine with patient data off the internet
The practice that browses somewhere else
Patient records live on machines that never touch the open internet. Everything needing the outside world — research, portals, mail, applications — happens in cells on the box. In Germany the statutory IT security directive for practices has required this kind of separation since 2021.
For: medical and dental practices, psychotherapists, care services
Honest limit: practice management software is Windows. The box complements it; it does not replace it.
Dictation and letters that stay in the building
Summarising findings and drafting letters is the AI task clinicians actually want — and the one that sends the most sensitive text to a provider. A cell with a local model and no network does the same job with the text never leaving the practice.
For: practices, medical offices, therapists writing reports
Honest limit: local models are weaker than hosted ones — that is the real trade-off. And this is a text tool, not a medical device.
Confidentiality that does not depend on a provider's promise
One client, one cell
Every mandate gets its own sealed machine, its own credentials and its own network rule. Separation stops depending on folder discipline. Germany's Federal Bar makes the point sharply: for professional secrecy it does not matter whether a provider looks at your data — it is enough that they could.
For: law firms, tax advisors, notaries, auditors, freelancers under NDA
Missing: client-cell templates bundling repository, VPN and credentials.
The confidential translation bench
Most NDAs forbid passing material to third parties — which includes web translators. A cell with a local model and no network lets a sworn translator or court expert work on the material without it ever leaving the desk.
For: specialist translators, court-appointed experts, patent attorneys, editors
Honest limit: local translation quality is the bottleneck, and it is fair to say so before someone switches.
Open what strangers send you
The newsroom airlock
A source hands over a USB stick or a 200-page PDF. You open it in a disposable cell with no network, work with it, then delete the machine. Dangerzone — built by the Freedom of the Press Foundation — proves the need by flattening documents to dead PDFs. A cell lets you actually work with them.
For: local newsrooms, freelance investigative reporters, NGO researchers
Missing: a one-click flow for handing a USB device to a cell.
The tip-line back office — not the tip line
Running a submission channel for whistleblowers safely is genuinely hard, and getting it wrong endangers people. Take the other half: receive through an established service, then do the reading, opening and archiving of unknown files in cells that never touch the network.
For: local newsrooms, small organisations with a reporting duty
Honest limit: we would tell you not to self-build the submission channel. This is the workbench, never a replacement for SecureDrop.
Give people real machines you can take back
Exams on the server, not the student's laptop
Lockdown browsers have one structural flaw: the student is administrator on the very device meant to contain them. Flip it — the exam runs in a disposable cell that can only reach the exam server, and the laptop becomes a screen. The retired PCs in the basement run it.
For: schools, vocational colleges, examination offices
Honest limit: this does not prevent cheating; it defines what is possible inside the environment. A second phone stays invisible. No camera, no proctoring.
Root access that expires
Teaching computing means letting students break things. Give each one a real machine with real administrator rights that disappears at the end of the lesson — no imaging, no re-installing, nothing to repair.
For: computing teachers, training providers, university labs
Missing: a class view, and honest scaling work for thirty cells at once.
The works council's own box
German law makes the employer the data controller for works council records — while the council works confidentially towards that same employer. Hamburg's data protection authority recommends council-held keys and, where possible, separate systems.
For: works councils, staff councils, employee representatives
Honest limit: physical access beats everything — in the company building, isolation protects against the network admin, not a screwdriver. Multi-user roles are still on the roadmap.
Hand over the cell, not the private laptop
The office that survives a change of committee
In most clubs and parishes, the accounts, the mailbox and the member list live on the treasurer's private laptop. Put them in a cell and the handover after an election is a handover of that cell — not a negotiation. For churches it goes further: the Catholic data protection authority now considers compliant Microsoft 365 use possible only in exceptional cases.
For: clubs and associations, parishes, small charities
Missing: handover as one button — key rotation plus a record — and multi-user roles.
The archive's compute shed
Local history societies sit on tens of thousands of pages to transcribe, and per-page cloud pricing puts that out of reach. Donated office PCs become a fleet that grinds through it over weeks, unattended. Your discarded hardware is your data centre.
For: heritage and genealogy societies, small municipal and church archives
Missing: transcription software as a ready-made cell. Expect CPU speeds.
The helper's bench
At a repair café or digital-help desk, a volunteer can open a stranger's suspicious attachment without risking their own laptop — and cast it to the big screen, so the person being helped sees what happens when you click. Teaching, not just fixing.
For: repair cafés, digital literacy volunteers, senior help desks
Honest limit: most attacks on older people are phishing, not malware. A cell shows a fake bank page just as convincingly. It protects the helper's computer, not anyone's judgement.
Where the attachments come in and the old machines never die
The inbox airlock
Every applicant CV, supplier invoice and unexpected attachment opens in a fresh cell. If it is ransomware, it detonates in a machine that exists for a minute. Attachments remain the dominant infection route — one German district's ransomware bill reached roughly €2.5 million.
For: HR, purchasing, back offices, small public administrations
Missing: mailbox-to-cell automation, so nobody has to remember.
The data room that stays in your building
Selling a company means putting the books somewhere buyers can read them — normally a subscription data room costing thousands a year, holding your crown jewels on someone else's servers. Invert it: buyers get a viewing cell on your box, and the room is deleted when the deal closes.
For: owners in succession or sale, M&A advisors, banks before lending
Missing: per-document rights, watermarking and access logs — the feature set buyers expect from a data room.
Quarantine for the machine that cannot be updated
Laboratories and workshops run instruments whose control software was frozen a decade ago, where replacing the software means replacing the machine. The box can put that machine behind a strict network rule, back it up nightly and make it reachable remotely.
For: laboratories, workshops, practices with instrument PCs
Honest limit: the box does not run Windows guests. This is quarantine, backup and remote access — not a second life for the old operating system.
The machine you were going to reinstall anyway
The dependency taster
Run npm install on an unfamiliar package — or that curl | bash installer — in a cell first, and see what it did: which files it touched, where it tried to phone home. In the 2025 Nx supply-chain attack, the damage was that outbound call.
For: developers, anyone installing software they did not write
Missing: a behaviour report worth reading.
Ephemeral CI on hardware you own
GitHub warns against self-hosted runners on public repositories, because any fork's pull request can execute code on your machine. A fresh microVM per job removes the premise of the warning — and the hardware cupboard supplies the capacity.
For: open-source maintainers, small teams with spare machines
Missing: runner registration and autoscaling.
A cage for your personal assistant
Self-hosted personal AI assistants are the software story of the year, and the security reporting on them is grim — tens of thousands of exposed instances, third-party skills caught exfiltrating data. People run them anyway, wired to mail, calendar and messages. Put one in a cell where the network rule is yours and the real credentials never enter the machine.
For: everyone currently running one on a bare home server
Missing: a ready-made recipe with the egress policy already written.
Small machines, thrown away without regret
Compartmentalised browsing
A banking cell, a social cell, a shopping cell — separate browsers that cannot see each other's cookies, reachable from any device in the house. The Qubes model without the Qubes learning curve. When browser extensions were compromised at scale, session tokens were the loot.
For: anyone who banks and browses on the same machine
Missing: named, persistent browser profiles as a first-class feature.
The empty laptop
Travel with a device that holds nothing. The work stays on the box at home; you reconnect on arrival and the session is where you left it. Companies have done this with clean loaner laptops and a corporate data centre for years — the box is that data centre, for one person.
For: researchers, reporters and lawyers who cross borders
Honest limit: data minimisation on the device, not secrecy. If someone compels you to log in, they see more than the laptop ever held.
The family archive that can be handed over
Two moments of the same family. Looking back: put a late relative's drive into a network-less cell as a read-only volume and explore it without risking anything. Looking forward: heirs receive one cell with one way in — not administrator rights over the whole household.
For: anyone who has stood in front of a dead relative's computer
Honest limit: not forensics — software read-only is not a hardware write blocker, and nothing here recovers a failing disk. Keep a cold copy as plain files: an archive that needs a running appliance is a fragile archive.
The television becomes a monitor again
Researchers measured smart TVs fingerprinting what is on screen every few milliseconds and reporting home each minute — including from HDMI sources. Put the browsing in a cell and cast it. For holiday lets, each guest gets a disposable cell deleted at checkout instead of leaving their streaming logins behind.
For: anyone with a smart TV; holiday let and guest room hosts
Honest limit: the TV keeps fingerprinting the HDMI image — this only fully works once the TV has no network. Commercial streaming in a VM means reduced quality or nothing, thanks to DRM.
Where this stops being true
One limit applies to everything above. Hypervisor isolation is far stronger than containers or browser sandboxes — but it is code, and code has bugs: Firecracker itself patched a serious flaw in 2026 that could crash the monitor from inside a guest. The honest claim is a boundary that is much harder to cross and has to be maintained, not one that cannot be crossed.
Anything needing Windows guests, forensic evidence chains, protection from state-level adversaries, or a compliance certificate is outside what this does. We would rather lose the sale than the argument.
Got a better one?
This list came out of a day of research, not a product plan. If you are sitting on a problem shaped like one of these, we would like to hear it — the source opens on 9 August, and what people actually need shapes what gets built next.
Get notified at launch → · support@brainarbeit.com