Enterprise DNA

Instead of LabArchives

Stop renting LabArchives. Own your research notebook.

We build your notebook around how your research team works, bring your LabArchives archive across and run your version for you. Start with experiments, evidence and review routines in a database you own.

LabArchives Professional Corporate lists US$575 per user per year. Corporate ELN + Inventory lists US$675 per user per year. Enterprise pricing is quoted privately.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

The notebook bill grows with the team

LabArchives sells hosted notebooks by paid seat, with separate plans for inventory and scheduling. Compare the records your team needs with the package you renew.

paid

Annual notebook seats

Professional Corporate is US$575 per user per year. Each paid seat adds to the annual notebook subscription.

inventory_2

The inventory bundle

Corporate ELN + Inventory is US$675 per user per year, combining notebook and inventory access.

cloud

Hosted storage and file limits

Storage and attachment limits vary by plan. Your required file sizes influence the plan you choose.

calendar_month

Resource scheduling

Scheduler is a separate product with its own free, paid and enterprise plans.

verified_user

Enterprise access controls

Enterprise adds organisation-wide controls and single sign-on under a custom quote.

description

The notebook interface

You pay for a hosted workspace to organise pages, entries and attached files. Your scientific records remain the reason it exists.

Your version

The experiment record is the centre of the work

Research week

Find the next experiment that needs attention

Start with unfinished work and the evidence behind it, across your projects.

  • check Active experiments grouped by researcher and due date
  • check Overdue work beside its missing source evidence
  • check Follow-up actions with owners and recorded resolutions
  • check A weekly review drafted from waiting reviews, evidence gaps and overdue work

Protocol and review

Keep the exact version behind each result

A protocol change and a correction leave a record that the next reviewer can follow.

  • check A fixed protocol version attached to every experiment
  • check Corrections linked to the original observation
  • check Independent review recorded against a specific revision
  • check Reopened work requires acceptance of its new revision before closing

History you keep

Preserve the notebook you already paid to create

Bring your offline LabArchives archive across, retain its original files and find text from older work.

  • check Original archive files stored with integrity fingerprints
  • check Search across new observations and archived page text
  • check Missing local file links listed for reconciliation
  • check A complete export of your records and retained notebook files

Research handover

Prepare the records the next person needs

Turn the recorded work into a readable experiment record and project handover in your business name.

  • check Experiment records with observations and evidence references
  • check Project handovers with unresolved actions
  • check Archive reconciliation records with file inventories
  • check Retention decisions and recorded backup checks beside the research they cover

Make it yours

Design your own LabArchives replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from LabArchives. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your LabArchives replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your LabArchives data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Actual answers from the fictional research records included in the free version. Names, dates and findings below are demonstration data.

forum

Research Notebook for Claude Code

Connected to your own database

Which research records need attention this week?

FIBRE-01

Owner
Noah Patel
Issue
No activity in 14 days
Due_date
2026-10-09

COAT-01

Owner
Mira Chen
Issue
Experiment overdue
Due_date
2026-10-10

ACT-01

Owner
Mira Chen
Issue
Action overdue
Due_date
2026-10-14

FIBRE-01

Owner
Noah Patel
Issue
Experiment overdue
Due_date
2026-10-16

FIBRE-01

Owner
Noah Patel
Issue
Retired protocol in active work
Due_date
2026-10-16

DEMO-ARCHIVE

Owner
Demo operator
Issue
Imported archive needs reconciliation
Due_date
2026-10-19

Ask it anything

Questions to ask across your research records

These questions run on the fictional example today. They demonstrate your own combined records, without claiming that LabArchives cannot produce equivalent analysis.

chat_bubble Which overdue experiments also lack raw evidence?
chat_bubble Whose review queue still contains open actions?
chat_bubble Which active experiments use retired protocols?
chat_bubble Which projects have no documented retention decision?
chat_bubble Which experiment records contain deviations?
chat_bubble Which researchers have overdue work and unresolved actions?
chat_bubble Which archived notebooks still need reconciliation?
chat_bubble Which exported pages refer to missing files?
chat_bubble Which projects combine evidence gaps with an overdue backup check?
chat_bubble Which closed records lack acceptance of their current revision?

Switching

How to switch from LabArchives

A move usually involves exporting an offline notebook, importing it as a read-only archive, and reconciling gaps before you change over.

  1. 1

    Export the notebook

    In LabArchives, create an Offline Notebook and download its ZIP, then extract it for import. Export the notebooks and content you want to retain, including records you still need to access. The export includes only content your account can access, and vendor exports omit attachments over 250 MB. Check with LabArchives about anything your account cannot export or any oversized files.

  2. 2

    Run a test import

    Have the destination project created first, then run a test import on the extracted archive before committing it. The import keeps original files and indexes HTML text, but it does not convert old pages into structured experiments or recreate signatures, sharing permissions, or revision history. Use the test to understand how the archive will be recorded before you load it for real.

  3. 3

    Review import gaps

    Check the import results for missing local links, then compare the archive with what you expect from LabArchives. Identify files or content absent from the export, including oversized attachments, and decide how to handle them. Review signatures, permissions, and editing history separately because the import does not recreate them. Keep original evidence files in your controlled archive.

  4. 4

    Run both systems briefly

    Keep LabArchives available while your team uses the new notebook for a short, agreed period. Compare active work and the imported archive against LabArchives, and make sure people can find the records and files they need. Decide which system is authoritative during this period, and record any differences that still need resolving before you cut over.

  5. 5

    Switch off LabArchives

    When reconciliation is complete and owners agree, move new non-clinical research work to Research Notebook for Claude Code and stop entering new work in LabArchives. Keep the exported archive and original files in your controlled archive. Do not move validated or clinical workflows into this base. Confirm your retention and account closeout requirements before ending LabArchives access.

construction

Where the real effort goes

Most effort is not the import. It is mapping your own fields and review rules, and deciding which history should remain as an archive versus become working data. The importer keeps the supplied archive read-only, rather than turning old pages into structured experiments. If Enterprise DNA runs the move, it handles this scoping and reconciliation with you.

Not ready for a call?

Get your LabArchives switch plan by email

We will send you the step-by-step plan for moving your business off LabArchives, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install the dependencies
  2. 2 Run npm test and npm run demo; open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export and extract a LabArchives Offline Notebook, then run import labarchives with --dry-run
  4. 4 Reconcile the archive, import it and start with /experiment-week
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your experiment fields, review rules and retention policy
  • check Your LabArchives archive brought across and reconciled
  • check A web front end, shared access or a different stack where your team needs it
  • check Your research connections and branded handover documents
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed in a database your business owns
  • check Agreed connections, backups and routine checks operated for you
  • check Your research review routines and reports maintained
  • check Run through Omni by Enterprise DNA with someone responsible for the system
Book a call with Sam

Questions

Instead of LabArchives, answered

What is free, and what do we pay Enterprise DNA for? expand_more

The base is open source. Your own hosting and chosen assistant remain separate costs. Enterprise DNA charges one setup fee, then a retainer to customise or operate your agreed version. LabArchives lists Professional Corporate at US$575 per user per year; compare that with your actual renewal and the work your team needs.

Does all our LabArchives history move across? expand_more

The importer preserves and indexes the offline notebook archive you provide. It checks missing local links and retains original files. Vendor exports omit oversized attachments and only include content you can access. We reconcile those gaps with you. Existing signatures, permissions and editing history need separate review; they are not recreated automatically.

Can this replace our validated research system? expand_more

The free base is for non-clinical research records. It records human review decisions, but it does not provide regulated electronic signatures or certify compliance. Keep validated and clinical workflows in their approved system. We scope a suitable non-clinical installation around your actual requirements.

How would our scientists use it together? expand_more

The free base is operated by one trusted person. We can build your shared screens, individual access and file connections into your custom version. We agree those controls before your team starts using real research records.

What happens when someone changes a result after review? expand_more

Observations are corrected by adding a linked correction, preserving the original. Reopening an experiment makes its previous acceptance historical. Its current revision needs an independent review before it can close again.

Bring the notebook bill and one research workflow

In a 30-minute call, Sam will walk through your current LabArchives setup, the records you need to keep and the version Enterprise DNA would build and run for you.

Book a call with Sam Get the free version

Research Notebook for Claude Code is free and open source, published by Enterprise DNA.

Done paying for LabArchives?

Get your version built