Skip to content
MBiotech.
All apps

Educational tool · Preview

Drybench Cell.

A guided 3D tour of how a human cell turns a gene into a working protein: DNA packed in chromatin, transcription, splicing, export from the nucleus, the ribosome, the exit tunnel, a folding chaperonin and haemoglobin at work. Each step is a real structure from the Protein Data Bank with its primary paper, the sizes and counts in the text were measured from the deposited coordinates, and the whole tour runs in your browser.

Example data: Step 5: the ribosome. PDB 6Y0G (CC0 1.0). Bhaskar V et al. Cell Rep 2020;31:107473.

Free during the preview · Runs in your browser · v0.1.0 · stills 50 to 130 KB each; the 3D view about 1.5 MB, on request

See it before you open it

Open the full app

stills 50 to 130 KB each; the 3D view about 1.5 MB, on request

Features

What you can do with it

  • 8-step guided tour

    Chromatin, transcription, splicing, export, translation, the exit tunnel, folding and haemoglobin, in order, with one colour scheme throughout.

  • Real human structures

    Eight PDB entries checked against the RCSB PDB, Europe PMC and UniProt, each shown with its method, resolution and primary paper.

  • 3D plus Blender stills

    A still rendered in Blender appears at once; the Mol* 3D view loads when you ask and keeps the same colours, cutaway and camera.

  • Sizes on one scale

    All eight structures on one nanometre scale, so a nucleosome can be set against a ribosome.

  • Measured from the structures

    Sizes and counts in the text were measured from the deposited coordinates by a reproducible pipeline.

  • What you are looking at

    Each step names the parts on screen against a colour key, and the 3D labels and tooltips use the same words.

  • An address for every step

    Each step has its own pre-rendered page, so a shared link opens on that step's text and picture.

  • The whole tour as text

    All eight steps as plain text, for reading straight through, printing or a screen reader.

How it works

Where it runs and what it sends

  1. Open a stepEach step loads its text and a still rendered from the structure. Nothing is installed, and no request goes to any other service.
  2. Load the 3D view when you want itMol* (about 1.5 MB) and the step's trimmed structure file (25 to 240 KB) come from this site only, and stay loaded as you move on.
  3. Read what you are looking atThe text, the colour key and the 3D labels name each part of the machine, with the structure's PDB entry and paper beside it.
  4. Move on, or read it allMove with the arrow keys or the step list, or open the whole tour as text.

What it shows

A guided tour of how a human cell turns a gene into a working protein, in eight steps: DNA packed in chromatin, transcription by RNA polymerase II, splicing, export from the nucleus, translation on the ribosome, the new chain in the exit tunnel, folding inside a chaperonin, and a finished protein, haemoglobin, at work.

Each step is a real structure from the Protein Data Bank, determined by X-ray crystallography or cryo-electron microscopy, with its primary paper. The colours mean the same thing in every step: DNA, messenger RNA, other RNAs, the protein machinery, the protein being made and small molecules.

How it works

The page ships the tour text and a still image for each step. The 3D view loads only when you ask for it: first the Mol* viewer (about 1.5 MB compressed), then, for each step, a gzipped BinaryCIF structure file of 25 to 240 KB (60 to 420 KB unzipped) and a MolViewSpec scene that sets the representation, colours, labels, cutaway plane and camera. The page downloads and unzips each file itself, so a download for a step you have already left is cancelled, and a stalled one ends with a message and a retry.

The structure files are cut down from the PDB entries by the build pipeline to the atoms shown, with no water or hydrogens. For the five biggest complexes by atom count, the spliceosome, TREX, the two ribosomes and TRiC, with about 36,000 to 215,000 atoms each, the machinery keeps one atom per residue and is drawn as a backbone trace, while the RNAs and chains the step is about keep every atom. That keeps them usable on a phone.

How it was built

A Python pipeline checks every PDB entry against the RCSB Data API (title, organism, method, resolution, year), checks each primary citation against Europe PMC, and checks UniProt accessions. It then reads the structures with Biotite, confirms each coloured entity is what the scene says it is, measures the numbers the text quotes with NumPy and SciPy (sizes, resolved residues, base pairs, how far the chain in the tunnel reaches from its tRNA), works out the camera and cutaway plane, and writes the trimmed, gzipped files and the scene data, noting which revision of each entry they were cut from.

The stills were rendered headless in Blender 5.2 with the Molecular Nodes add-on, using Cycles on the CPU with 32 samples and denoising. The render script reads the same scene data as the 3D viewer, so each still shows the same structure, colours, cutaway and viewing direction. The stills are the step images before the 3D view loads, and the fallback where WebGL is not available.

Methods, parameter defaults and references are on the methods page. Read the methods

Keyboard and accessibility

Built for the keyboard and for screen readers

Everywhere in the app

Show every keyboard shortcut
?
Go to the search field
/
Open the command palette
ControlK
Open Settings
Control,
Close the innermost panel, menu or dialog
Escape

In this app

Previous step
Left arrow
Next step
Right arrow
First step
Home
Last step
End
Go to step 1
1
Go to step 2
2
Go to step 3
3
Go to step 4
4
Go to step 5
5
Go to step 6
6
Go to step 7
7
Go to step 8
8
The whole tour as text
t
Reset the 3D view
r
Zoom in
+
Zoom out
-

Single-key shortcuts work outside text fields and can be turned off in Settings.

Commitments

  • Controls work from the keyboard, with focus always visible.
  • One polite live region announces what changes, for screen readers.
  • Reduced motion is honoured, from your system setting or the app's own switch.
  • Works at 375 px wide.

Docs and methods

Data sources and licences

Where every number comes from

Sources and licences

  • RCSB Protein Data BankCC0 1.0

    Atomic coordinates (BinaryCIF, trimmed by the pipeline) and entry metadata for all eight structures

    PDB entries 3AFA, 8XSO, 6QDV, 7ZNK, 6Y0G, 6OLE, 7TUB and 2DN1; each step cites its primary paper

  • UniProtCC BY 4.0

    Protein names, lengths and function notes behind the text; accessions for the protein explorer links

    The UniProt Consortium. UniProt: the Universal Protein Knowledgebase in 2025. Nucleic Acids Res 2025;53:D609-D617.

  • Europe PMCEMBL-EBI terms of use (no added restrictions)

    Checking each citation's title, authors, year and DOI, and the background abstracts behind a few facts (PMIDs 21195232, 24459735, 24196718 and 20118940)

  • RNAcentralCC0 1.0

    Identifying the tRNA sequence in PDB 6Y0G as Escherichia coli tRNA-Phe (URS00005AA258)

  • PDB-101 Molecule of the MonthArticles © RCSB PDB and authors; background reading only, no text reused

    Background on nucleosomes, RNA polymerase, spliceosomes, the nuclear pore, ribosomes, tRNA, chaperones and haemoglobin

    David S. Goodsell and the RCSB PDB

  • Mol* 5.11.0MIT

    The 3D viewer and MolViewSpec scenes

    Sehnal D et al. Mol* Viewer: modern web app for 3D visualization and analysis of large biomolecular structures. Nucleic Acids Res 2021;49:W431-W437.

  • Blender 5.2 (bpy 5.2.2)GPL-3.0-or-later for Blender binaries such as bpy (source GPL-2.0-or-later); build-time tool only, no code shipped

    Rendering the step stills (Cycles, headless); the outputs are not covered by the GPL

    Blender Foundation

  • Molecular NodesGPL-3.0-or-later; build-time tool only, no code shipped

    Loading and styling the structures in Blender for the stills

    Brady Johnston

  • BiotiteBSD-3-Clause

    Reading, measuring and trimming the structure files in the build pipeline

  • NumPy and SciPyBSD-3-Clause

    Measuring sizes (convex hull) and camera axes in the build pipeline

Everything here runs in your browser, and the app contacts no host but its own.

Anything in the address bar before the # (a search, a SMILES, an accession or a step) is sent to this site's host when a page loads or a link is opened; anything after the # is not sent.

Not used, by licence:

  • AlphaFold 3 outputs. Their terms allow non-commercial use only; every structure in the tour is experimental.
  • DrugBank. Its licence is non-commercial; drug names come from the PDB entries and the primary papers.

Third-party notices

Limits

What it does not do

  1. 1. The steps are separate experiments on different molecules, from different laboratories and years. They illustrate the stages of gene expression; they are not one gene being followed through the cell.
  2. 2. Structures are snapshots. Flexible parts, such as histone tails and most of the mRNA held by TREX, are missing from the models, and the machines move between many states that one structure cannot show.
  3. 3. For the spliceosome, TREX, the two ribosomes and TRiC, the 3D view draws the machinery as a backbone trace (one point per residue) to stay light on phones. The key RNAs and chains keep every atom, and the full entries are one click away on the RCSB PDB.
  4. 4. Some complexes were trapped with a drug or assembled from synthetic parts: step 5 has the drug cycloheximide, a synthetic poly(U) message and tRNAs with a bacterial sequence, and step 6 has the stalling molecule PF-06446846.
  5. 5. Cutaways and camera angles were chosen to show the step's subject; they hide parts of each complex.
  6. 6. This is an educational illustration, not a research or clinical resource.

Regulatory position

Use in regulated work

Regulatory position

Drybench Cell is off-the-shelf software for research and education. It has not been validated for use in a regulated (GxP) environment, and we make no claim of compliance with FDA 21 CFR Part 11, EU Annex 11 or any GxP requirement; no software can be certified as "Part 11 compliant" on its own. Responsibility for compliance, including any validation of the software in your environment, lies with the organisation that uses it. Its price, when set, will not include validation services.

What we provide to help you qualify it yourself: a dated changelog and release notes for every version; a methods page naming each algorithm, parameter default, data source and version; a verification dataset with expected outputs for each release so you can run your own checks; exports and reports that carry the data versions, parameters, limits and a timestamp needed to reproduce a result; and a security overview.

What the app does not do: it does not keep a server-side record of who changed what, it has no electronic signatures, it does not control user access and it provides no IQ/OQ package, because it runs entirely in your browser with no accounts. Saved projects stay in your browser only. If you need those controls, the app can sit inside a validated system that provides them; it cannot provide them itself.

Supplier questionnaires: we answer with a short security and architecture summary (see Trust), and we will say plainly which questions do not apply to browser-only software.

Pricing

Pricing, indicative

Indicative · not yet on sale

Indicative pricing, not yet on sale. The tiers on this page are a proposal for how Drybench may be sold. No price has been set, nothing can be bought here, and no licence key exists: during the preview every feature of every app is available to everyone. What each tier would include is shown so the design can be judged; it is not an offer.

  • Free

    Personal, evaluation, classroom and non-commercial use

    No charge

    no licence key

    • Every view, viewer and science feature
    • Sample data and share links
    • Exports with their sources, licences and limits
    • Projects saved in this browser
    • The full limits, regulatory position and privacy statement
  • Academic

    Degree-granting institutions and registered charities

    to be announced

    per seat, billed annually

    • Everything in Pro, for non-commercial research and teaching
    • Eligibility checked by a person when the licence is issued
    • A course licence for a named class, on request
  • Pro

    Recommended

    One named user in industry

    to be announced

    per seat, billed annually

    • Commercial use for one named user
    • Unlimited saved projects and batch work
    • Support by email with a stated response time
    • A licence certificate for software-asset records
  • Team

    Groups buying on one order

    to be announced

    2, 5 or 10 seats

    • Pro for each named user, in packs of 2, 5 or 10 seats
    • One invoice, with purchase orders accepted above a stated minimum
    • Project files that move between colleagues

Tiers and gates follow the norms of comparable tools; prices are set separately and will be published here. Nothing is gated today.

Academic pricing will be a stated fraction of Pro, and a suite bundle will be offered.

An Enterprise tier with central sign-in and governance would need an account layer, which the apps do not have; it is listed so the design is complete.

The pricing design in full

Trust

Security, changes and methods

Security posture

The tour runs entirely in your browser and contacts no host but its own: no scientific service, no analytics, and no fonts or scripts from anywhere else.

  • This app contacts no host but its own.
  • No analytics in the apps
  • HTTPS only
  • Projects and notes are stored only in your browser
  • Anything in the address bar before the # (a search, a SMILES, an accession or a step) is sent to this site's host when a page loads or a link is opened; anything after the # is not sent.
  • We do not currently hold a formal security certification.
  • We do not currently have a formal security questionnaire; we answer supplier questions by email and say plainly which do not apply to browser-only software.

Security overview

Changelog

  1. Released on the mbio.tech Tools page

    Inside a cell went live: an eight-step tour from chromatin to haemoglobin in real PDB structures, with a Blender still for each step, a Mol* 3D view on request and a pre-rendered page for every step.

All changes

Docs and methods

Equations, parameter defaults, references, the verification checks and the security overview.

Docs and methods

Questions

Questions buyers ask

Who is the tour for?

Anyone who wants to see how a gene becomes a working protein: students, people new to biotech and pharma, and colleagues outside the lab. Each step explains its structure in plain words, with the scientific names alongside.

Are these real structures?

Yes. Each step is a structure deposited in the Protein Data Bank, shown with its method, resolution and primary paper. Some complexes were trapped with a drug or assembled from synthetic parts, and the steps concerned say so.

Where do the numbers in the text come from?

Sizes and counts were measured from the deposited coordinates by the tour's build pipeline, and every entry, citation and accession was checked against the RCSB PDB, Europe PMC and UniProt.

Does it need any outside service?

No. The pages, the stills, the trimmed structure files and the Mol* viewer all come from this site, and the tour makes no request to any other host.

Will it work on a phone or a classroom computer?

The steps, stills and text work at phone width. The 3D view needs WebGL and downloads about 1.5 MB the first time you open it; without WebGL the tour shows the stills instead.

Can I use it for teaching or training?

During the preview it is free for everyone to use, and each step links to its PDB entry and cites its paper, so learners can follow the sources. The app is not on sale yet; the indicative pricing shows how training use in companies is expected to be licensed.

Is it a research or clinical resource?

No. It is an educational illustration. The steps are separate experiments on different molecules, from different laboratories and years, so the tour illustrates the stages of gene expression rather than following one gene through the cell.

Next step

Want this tuned to your pipeline?

Email m.beale@me.com with what you need, or use the contact page.

Available from September 2026 for full-time roles and selected freelance projects.