Myelin · Brief
External R&D data — clean, governed, AI-ready
Your own data is catalogued and governed. What your CROs, genomics and imaging partners send you is not — it arrives as files in a folder. Myelin holds every partner delivery to the same standard as your own: checked at the source against rules your company owns, reviewed by your team, delivered into your own cloud. Transit and quality review — deliberately not a system of record.
What it is for
The clock
Interim analysis dates are set by a committee and do not move. A new partner means an approved transfer method, an IT ticket and a queue — a package can sit idle for weeks, and no budget line buys the wait away.
The round-trip
The data lands, and two or three weeks later a bioinformatician finds the samplesheet short. Then the email, the re-export, the re-upload. Two of those and the interim is at risk.
The wrong answer
A samplesheet that disagrees with what arrived does not throw an error. It produces a plausible, publishable, wrong result, found long after the go/no-go decision it informed.
The record
What was checked, by whom, against which version of which standard, gets reconstructed from mailboxes when someone asks.
What a delivery has to answer
Is it all here?
Automated
Names, structure, sizes, checksums, samplesheet contents — most of it before a byte is uploaded.
Is this the right data?
Your reviewer · blocking
Checked against the IRB-approved analysis plan and the contracted order: assay, kit, reference build, anatomy imaged, protocol version.
Is it good enough?
Your domain expert
Sign-off against the acceptance criteria contracted for that assay — target coverage, peptide ID rate, image quality.
What a check actually is
One assertion about a delivery, enforced before the data moves. Your quality function authors the library once; a study can add to it but cannot quietly drop a company rule, and the rules in force at submission are frozen onto the delivery. Contracts ship today for scRNA-seq, bulk RNA-seq, WES, DICOM imaging, mass-spec proteomics and clinical metadata — including a privacy check that catches dates and MRN-like identifiers in file and folder paths, before a delivery moves. Two of them:
Consistency · sequencing
The samplesheet must account for every sample folder that arrived — and every sample it lists must actually be there.
✗ fails on samplesheet lists S13 — no S13 folder in the delivery
Consistency · imaging
An imaging samplesheet keys on Series_ID, not Sample_ID. Every declared series must arrive, and every delivered series must be declared.
✗ fails on samplesheet declares 42 series; 39 folders arrived
Most checks need only names, paths and sizes, so a partner’s pipeline settles them before uploading a byte — which is where the round-trip weeks come back.
What everyone asks first
What do our partners have to buy?
Nothing. Partners never pay for Myelin and install nothing to deliver from a browser. Pipelines use the REST API or our CLI, with a key your team can revoke.
96 samples, 8 fail QC. Do the other 88 wait?
Only if you want them to. The batch is the unit you accept and you set its edges: clear the 88 now, take the re-runs as a follow-up delivery to the same dataset.
Why not a transfer tool, or a bucket and a script?
Aspera, Signiant and Globus move bytes fast and ask nothing about them — the bytes were never the problem. A landing zone gets you an ingest path in a sprint; the quarters after it go on partner onboarding, a rule library your quality team can edit without you, and a tamper-evident record.
The facts a reviewer asks for first
Where it runs
EU by architecture — Ireland, Dublin, Belgium
Where data lands
A bucket you own, on Google Cloud or AWS
Delivery scale
Terabytes — whole-genome runs, full imaging series
How long we hold it
Staged copies purged 7 days after verified delivery
Rule library
18 check engines, six quality dimensions, extensible by your team
Record
Hash-chained audit trail, verified daily, exportable as CSV or PDF
Cost to your partners
None — and nothing to install for browser delivery
Company stage
Pre-first-customer. Seeking founding partners.
Where we are
Myelin is built, deployed on EU infrastructure and running end to end — checks, review, delivery into a client-owned bucket, audit trail. What it does not have yet is a first named customer. Certifications and an independent penetration test are sequenced on real triggers rather than claimed; every gap is listed in the vendor assessment pack, along with the DPIA input and a pre-answered security questionnaire.
If Myelin disappeared tomorrow: delivered data is already in your bucket and stays there, a delivery still in flight has never left your partner’s hands, and the audit trail is yours to export in full.
What a pilot is
One real delivery. We set up a Bridge with one of your partners, encode the checks that delivery should have had to pass, and walk it through to your own bucket — your partner, your reviewers, your cloud. Founding partners shape the rule library rather than inherit someone else’s.
hello@myelinbridge.com · myelinbridge.com
Deeper reading: security overview · vendor assessment pack
Print this page (Ctrl/Cmd + P) for a PDF you can attach.