Apr 27, 2026
OmnyraCloud
Emilin Mathew
🏆 Track 3 Winner: AI Biosecurity Tools
OmnyraCloud is protocol level biosecurity screening for cloud lab workflows. Today's tools screen DNA sequences at order time — but cloud labs run workflows, and a chain of individually benign steps (serial passage, split orders, surface obfuscation) can pursue a dangerous objective without a single flagged sequence. That's the gap we close.
OmnyraCloud ingests any lab protocol (Autoprotocol, Opentrons, JSON, or free text) and runs a 5-stage pipeline: decompose the workflow → score 5 risk dimensions → ground every flag in retrieved biosecurity literature → audit with LLM-as-judge → cross-check sequences via IBBIS commec. Output: an auditable risk report with citations, not a black box.
IBBIS flagged 1/3 dangerous protocols. Two sequences were screened but returned no HMM matches, but protocol level reasoning caught all three.
Protocol level screening isn't just complementary to sequence screening. It's essential.
Live at https://omnyra-cloud.vercel.app/
Fantastic idea. Best of luck with Omnyra.
As you said, the data size was sufficient for a proof-of-concept. This could have actual legs once a statistically significant number of protocols are evaluated.
The threat model is formally defined, the problem is real and underaddressed, and the retrieval-grounded reasoning chain is exactly the right design choice for a tool that needs to be auditable by human biosafety reviewers.
The evaluation is the ceiling. Five protocols; three of the most canonical DURC examples in the literature, two of the most obviously benign controls, is the easiest possible test set. Perfect F1=1.0 on that basis proves the system works in principle, not that it works in practice. The harder questions are false positive rate on ambiguous legitimate research and false negative rate on novel techniques outside the current threat taxonomy. Neither is tested, and both matter more for deployment than catching H5N1 and SARS-CoV-2.
The multi-protocol correlation gap is worth flagging beyond future work. An adversary who knows protocols are evaluated in isolation will simply split a dangerous workflow across multiple low-risk submissions. That's not a limitation to address later, it's a fundamental constraint on the current system's deployment value that should be stated more prominently.
Solo project, weekend build, live deployment, formally grounded threat model. This is the kind of work that should be developed further.
I'm not convinced that cloud labs are (as yet) a significant area of risk, but this tool might also be useful to CROs. The way that the tool is constructed seems robust and comprehensive, though. Also, just a small note, the table and graph says 'H7N9' but it should be 'H5N1'.
Cite this work
@misc {
title={
(HckPrj) OmnyraCloud
},
author={
Emilin Mathew
},
date={
4/27/26
},
organization={Apart Research},
note={Research submission to the research sprint hosted by Apart.},
howpublished={https://apartresearch.com}
}


