compareeHub

YOU CAN BUILD YOUR OWN SUPER-RESOLUTION MICROSCOPE FROM MAGNETIC LEGO-LIKE CUBES

Build a STORM super-resolution microscope from 50mm magnetic cubes, then run it inside an incubator from a laptop.

by Benedict Diederich and the openUC2 team

FULL CAD BOM FIRMWARE DOCS

ScienceOpen-hardware

difficulty
●●●●○
time
several weekends
license
CERN-OHL-S-2.0 (hardware), GPL-3.0 (software)
repo
repo ACTIVE0 stars

WHAT YOU’LL NEED

  • 3D printer + filament — printable parts — files are in the repo
  • Electronic parts — full list with part numbers in the repo BOM
  • Dev board / microcontroller — runs the project firmware

Partner

Show off your build — Record and edit your build video by editing the transcript, not the timeline.Try Descript
1

COMPAREE VERDICT

openUC2 is a modular microscopy platform from Leibniz IPHT and Uni Jena, published in Nature Communications and OSHWA-certified. The core concept is brilliant: 3D-printed 50mm cubes with embedded magnets snap together on a shared optical grid, and you can reconfigure a microscope in minutes instead of machining a new optical bench. People have built everything from a basic brightfield scope to a STORM super-resolution rig that resolves single fluorescent molecules. The limitation is that the project traded a single repo for modularity — there are 50+ repositories, each one a subsystem (ESP32 firmware, REST API, ImJoy plugins, the BOX incubator enclosure), and no single walkthrough that says 'buy these parts, print these files, load this firmware, done'. The GitBook docs are comprehensive but assume you already know which modules you need. If you are familiar with microscopy and want to prototype a custom imaging setup without a 40 dollarsk commercial frame, this is exceptional. If you have never aligned an objective before, start with the SimpleBOX or Matchbox tutorials and budget time to learn optics alongside the build. The one thing most likely to go wrong is underestimating the alignment step — magnets make assembly fast, but a 2µm error in the optical path is the difference between an image and a blur.

NOT IN THE REPO

  • —Organisation account with 50+ repos, not a single build guide — each repo (UC2-ESP, UC2-REST, ImJoy, TheBOX) is a modular subsystem.
  • —CAD files are FreeCAD and STEP, BOMs are spreadsheets per module, firmware is ESP32 Arduino sketches.
  • —Documentation is scattered across readme files, a GitBook site, and linked tutorials — no one linear path from zero to working microscope.
  • —CERN-OHL-S for hardware, GPL-3.0 and MIT for software — all open-source, commercial use allowed.
  • —Nature Communications paper and OSHWA certification confirm it works, but the paper is not a build manual.
  • —The simplest starter is a basic brightfield scope; STORM super-resolution is an expert branch requiring a laser, precise alignment, and fluorophore chemistry.

Can I build this?

PrintCore cube system plus inserts for lenses, mirrors, and sample stages — files are modular FreeCAD and STEP per subsystem repo.
BuyMagnets, M3 hardware, optics (objectives, tube lenses, mirrors), ESP32 dev boards, stepper drivers, camera — BOM varies wildly by which microscope configuration you build.
Tools3D printer, soldering iron, Allen keys, and optical alignment tools (or patience and shims) — FreeCAD for tweaking cube inserts if needed.
SkillsIntermediate to advanced — printing and assembly are straightforward, but optical alignment, firmware flashing, and integrating the control software require real troubleshooting. STORM builds require fluorescence microscopy experience.
TimeA basic brightfield scope is a long weekend if the parts are ready; a STORM super-resolution build is several weekends plus alignment and calibration.
Cost$$$ — magnets and hardware are cheap, but optics (objectives, filters, cameras) and lasers dominate the cost. A basic scope fits in low $$$, STORM pushes mid-to-high $$$.
SafetyLaser safety is the real hazard if you build a fluorescence or STORM variant — class 3B or 4 lasers require goggles, interlocks, and proper enclosures. Basic brightfield builds have no safety concerns beyond standard electronics.

Build at your own risk. Projects involve tools, electronics and sometimes mains voltage — follow the creator’s safety notes.

A desktop 3D printer that prints in full colorPartner · Kickstarter
A desktop 3D printer that prints in full color

HeyGears G1: 10M+ colors and transparent parts in one print, plus UV printing on flat objects. Figures, parts and labels — no painting.

See how it prints

Gallery

https://raw.githubusercontent.com/openUC2/UC2-STORM-and-Fluorescence/main/IMAGES/SetupImages_2.jpeg
https://raw.githubusercontent.com/openUC2/UC2-STORM-and-Fluorescence/main/IMAGES/microscope_1.jpeg
https://raw.githubusercontent.com/openUC2/UC2-STORM-and-Fluorescence/main/IMAGES/IMG_20200807_181322.jpg

Start here

Navigation into the creator’s own docs — we don’t rewrite the guide, we route you to the source.

  1. 1.Read the overview at the GitBook documentation site to understand which microscope configuration matches your goal.(The docs are linked from the GitHub org page — no single starting repo.)
  2. 2.Clone the UC2-GIT repo for cube CAD files, then identify which optical module repos (e.g. UC2-MicronStage, UC2-Hackathon) you need for your build. (Each module is a separate repo — expect to pull from 3-6 of them.)
  3. 3.Print the base cubes and inserts, source the magnets and M3 screws, and order your optics from the per-module BOM spreadsheets.(Magnets and screws are cheap and standard; optics are where lead time and cost vary.)
  4. 4.Flash the UC2-ESP firmware if your build includes motorized stages or LED control, then integrate with the UC2-REST API or ImJoy for computer control.(Basic builds can run manually; automated imaging requires this step.)
  5. 5.Align the optical path — this is the hardest step and the GitBook has alignment tutorials, but expect iteration.(A 3-axis stage and a test slide make this much faster.)

KNOWN ISSUES

  • The GitHub org has 50+ repos and no 'start here' repo — you will spend the first hour figuring out which ones you actually need. The GitBook is the real index.
  • Optics are not plug-and-play — a cheap objective from eBay might not match the tube lens focal length, and infinity-corrected optics require exact spacing. Budget time to learn the optical design before ordering.
  • The BOM is per-module and spread across repos — there is no single 'buy this list' unless you pick a pre-defined build like SimpleBOX. Expect to consolidate spreadsheets.
  • Alignment is manual and iterative — magnets make assembly repeatable, but 'repeatable' is not the same as 'aligned'. If you have never collimated a beam, watch alignment tutorials first.
  • STORM super-resolution is not a weekend add-on — it requires a stable laser, precise XY stage control, fluorophore chemistry, and post-processing software. The Nature paper proves it works, but it is an expert-level branch.
  • No official project video exists for a full build — community walkthroughs are scattered and the reel shows assembly but not the complete process. Plan to read docs, not watch a video.

Which microscope should I build first?

Start with the SimpleBOX or Matchbox brightfield scope — they are fully documented, require basic optics, and teach you the cube system without laser alignment or fluorescence complexity.

Can I actually build the STORM super-resolution microscope from the Nature paper?

Yes, but it is an expert build. The paper describes the optical design and the repos have the files, but you need fluorescence microscopy experience, a stable laser source, precise stage control, and post-processing software to reconstruct super-resolved images.

What optics do I need and where do I buy them?

Each module repo has a BOM spreadsheet with part numbers. Objectives, tube lenses, and cameras vary by build — cheap ones exist on eBay and AliExpress, but quality matters for resolution. The GitBook has a guide to optical specifications.

Do I need the ESP32 firmware or can I build a manual microscope?

A basic brightfield scope works entirely manually — no firmware required. Motorized stages, automated Z-stacks, and LED control require the UC2-ESP firmware and REST API.

Is the licence safe for commercial use?

Yes — hardware is CERN-OHL-S, firmware is GPL-3.0 and MIT. All allow commercial use, though GPL requires source disclosure if you distribute modified firmware.

Community builds

No community builds yet — be the first, we feature the best ones.

Discussion1

FROM THE COMPAREE TEAM

People have built STORM rigs that resolve single molecules and run them inside incubators — what would you image first if you had sub-diffraction resolution on your bench?

CompareeTEAM1mo agoedited

Practical notes from our verification: the GitHub org has 50+ repos and no single entry point — the GitBook (linked from the main org page) is the real starting guide, but the URL was not in the payload so we cannot link it directly here. The Nature Communications paper proves the STORM build works, but it is a methods paper, not a tutorial. The reel shows cube assembly, but there is no official project video — the walkthroughs are community-made and scattered. The single biggest decision is picking your first build: SimpleBOX or Matchbox are the documented on-ramps, STORM is the deep end. If you are new to microscopy, treat the cubes as a prototyping platform, not a turnkey microscope — the modularity is the entire point, but it means you design your own optical path.

Benedict Diederich and the openUC2 team

Benedict Diederich at Leibniz IPHT and Uni Jena leads the openUC2 project, which published the modular cube microscopy platform in Nature Communications. The project is OSHWA-certified and designed for labs that need custom imaging setups without commercial vendor lock-in.

GitHub

Star the project on GitHub

DISCLAIMER

  • Comparee is not the author of the projects featured here. All rights to each project belong to its creator — every page links to the original source, and we never host creators’ files.
  • Information is provided without warranty and may become outdated as projects evolve. Prices are indicative bands only — always check the creator’s parts list for current costs.
  • Building and operating any project is at your own responsibility. Protective equipment, safe workshop practice and compliance with local regulations are the builder’s responsibility.
GitHub repo