nanalLabs BlogSearch "electronic lab notebook comparison" and most of what comes back is a feature table for commercial ELNs (Electronic Lab Notebooks) like SciNote and LabArchives, or Korea-specific tools like Goono and RNDNote. The problem is that every one of these comparisons assumes the same situation: an institution budgeting to roll a system out across an entire team. A lot of the people actually searching for this are individual graduate students, or researchers who need to meet regulatory requirements — immediacy, preserved correction trails, verified authorship — at the level of a single lab, before any institutional purchase happens. This post splits the two situations apart and walks through what to weigh in each.
What institutional ELNs sell is "collaboration," not "compliance"
SciNote, LabArchives, Goono, and RNDNote all sell roughly the same thing: experiment protocol templates, cross-team sharing, inventory and reagent management, and electronic approval workflows. Most of them do satisfy, as a baseline, what research-note guidelines for government-funded R&D actually require — immediacy, a preserved record of corrections, verified authorship and review, tamper-evidence — but that compliance angle is rarely the headline feature being sold. Whoever is signing the contract has to check for it directly, because the vendor pitch usually won't lead with it.
| Institutional ELN (SciNote, LabArchives, etc.) | Korea-specific (Goono, RNDNote, etc.) | National infrastructure (Research Notebook Portal · IRIS) | |
|---|---|---|---|
| Primary user | Institutional / corporate research teams | Institutions running Korean government R&D projects | Researchers on government-funded R&D projects |
| How it's adopted | Paid subscription, institutional contract | Paid subscription, institutional contract | Government system, tied to project registration |
| Timestamp integration | Vendor's own timestamp (varies by vendor) | Some link to KISTA's research-note portal timestamp service | Timestamp service linked to Korea's GTSA (government time-stamp authority) |
| Collaboration / approval workflow | Strong | Strong | Bound to the project reporting structure |
| Usable solo | Effectively not — assumes a team contract | Effectively not | Not available outside a registered project |
| Cost | Per-seat, needs institutional budget | Per-seat, needs institutional budget | Free within project budget |
We've covered the relationship between institutional ELNs and this national infrastructure — the research-note portal's timestamp service — in more detail in an earlier post on the research-note timestamp service. The short version: that timestamp service only reaches an individual researcher if their institution has integrated with it, so private corporate labs and individual researchers outside government R&D aren't eligible to apply for it in the first place.
Before an institution adopts one, what do individuals and small labs actually use
Institutional ELN contracts are usually priced per head and take time to work through internal approval. But what the guidelines actually require isn't a named system — it's a property: immediate recording, a structure where the original survives any correction, and time-of-record proof a third party can verify. If a setup satisfies that property, there's no need to wait for a commercial ELN contract to close.
Combinations commonly suggested for the pre-adoption stage include:
- A local-first note app (like Obsidian) plus file version control:
records accumulate as markdown files, and the edit history lives in the file system or a sync tool. No institutional approval workflow or team collaboration, but sufficient for individual record-keeping.
- A habit of preserving correction trails: turning on track changes in
Word or Hangul documents instead of deleting and rewriting, or using a tool like Obsidian where the whole file keeps a version history.
- An external timestamp-proof service as a supplement: if your
institution isn't integrated with the government timestamp service, a service that proves the time of a given file — RFC 3161 timestamps or Bitcoin anchoring — without requiring institutional membership can fill the gap. nanalStamp targets exactly this segment (individuals and small labs not integrated with an institutional system) — though the point of this post isn't any one product, but knowing that "not an institutional ELN" doesn't mean you can't meet the requirements.
A checklist for choosing
Before picking a system, work through these in order:
- [ ] Are you on a government-funded R&D project? If so, check first
whether you're eligible for the research-note portal / IRIS timestamp service — confirm the integration status through your institution's administrator.
- [ ] Is team collaboration the core requirement? If several
researchers need to share the same protocols and route them through approval, that's a real case for an institutional ELN.
- [ ] Does the system structurally preserve correction trails? If a
tool allows deletion or overwriting, check whether that conflicts with the guideline's requirement to leave the original visible under a strike-through with a signature and date.
- [ ] Whose responsibility is the timestamp proof? Check whether your
institution's system timestamps automatically, or whether the researcher has to handle timestamp proof separately. If it's the latter, using a timestamp service at the individual level before adoption closes the gap in the meantime.
- [ ] **When does the institutional budget/approval process actually
finish?** If adoption takes time, records from that interim period still need to meet the guideline's requirements to hold up under an audit.
The more accurate question isn't "which electronic lab notebook system is best," but "given my actual situation — institutional affiliation, team size, whether I'm on a government project — what's the fastest way to meet the guideline's requirements right now." Before applying any of this, it's worth checking your own institution's or project's research-note policy as well.