Enterprise DNA

Instead of Nested Knowledge

Stop renting Nested Knowledge. Own your literature review system.

We build your version around your review methods, bring your Nested Knowledge records across and run it for you. Your criteria, your evidence pack and a database you own.

Nested Knowledge lists Business Essentials at $295 and Enterprise at $695 per user per month. Enterprise is $8,340 per user over twelve months at the monthly rate, before tax. Annual checkout terms can differ.

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 buys

The review method is yours. The seats keep renewing.

Nested Knowledge packages review workflows and synthesis in recurring plans. Compare the parts your practice uses with the work your own version needs to cover.

groups

A licence for each reviewer

Business Essentials is $295 per user monthly. Collaboration requires licensed or piloting users, so team access belongs in the comparison.

layers

A higher plan for more automation

Enterprise is $695 per user monthly. Its additional automated review features sit above Business Essentials. Decide which work your reviewers actually delegate.

database

The study register

Titles, authors, identifiers and report history are records your team curates. Keep their original source alongside your working review.

task_alt

Screening and disagreement handling

The platform holds screening decisions and reviewer identities. Your own version can retain decisions and require a recorded resolution before work moves forward.

description

Extraction and reporting

Nested Knowledge offers extracted-data and appraisal exports. Your version can check source references and produce the evidence pack your practice uses.

autorenew

An ongoing subscription decision

Enterprise Plus is quoted separately. Academic terms also exist. Bring your actual plan and invoice so the comparison reflects your practice.

Your own review operation

Ask about the evidence, then record the next human decision.

Screening

A clear decision queue

See unfinished screening and disagreements by report, owner and deadline.

  • check Two recorded reviewers at each stage
  • check A separate resolver for disagreements
  • check Full-text screening follows a retrieved report
  • check Changed decisions clear the checks that depend on them

Evidence

Values with a source and a checker

Keep extracted values beside their report references and the people who checked them.

  • check A source location for each extracted value
  • check A different person records the check
  • check A revised value clears its earlier check
  • check See unchecked values across all reviews in one answer

Reporting

Your handover paperwork

Prepare a protocol record, exclusion log and draft evidence pack in your own business identity.

  • check Report exclusions with decision reasons
  • check Group multiple reports under a study key
  • check Flag missing appraisal records before handover
  • check Use reporting checks tied to the PRISMA guidance and your own policy

Ownership

Records you can inspect and adapt

Keep original imported fields, current decisions and the history of changes in your database.

  • check Preview an import before saving it
  • check Reject conflicting repeat records without a partial import
  • check Track search refresh dates using your chosen interval
  • check Combine owner workload and review deadlines around your own process

Make it yours

Design your own Nested Knowledge replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Nested Knowledge 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 Nested Knowledge data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Literature Reviews for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Literature Reviews for Claude Code

Connected to your own database

Which reviews are due, and where are decisions still waiting?

REV-ACCESS

Name
Library access evidence review
Owner
Mara Chen
Due_on
2026-11-19
Records
6
Included
1
Conflicts
1
Waiting
2

Ask it anything

Questions Nested Knowledge cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which reviews have deadlines but unresolved screening disagreements?
chat_bubble Who has overdue screening work across our reviews?
chat_bubble Which reports need another reviewer before full-text retrieval?
chat_bubble Which included reports have an unchecked extracted value?
chat_bubble Which searches have passed our own refresh interval?
chat_bubble Which report requests have stalled with each owner?
chat_bubble How many reports sit at each decision stage, with study groupings kept separate?
chat_bubble Which reviews still need appraisal or study-link evidence?
chat_bubble What changed when a reviewer revised an earlier decision?
chat_bubble Which review packs are ready for a human methodology check?

Switching

How to switch from Nested Knowledge

In practice, the move is a staged data transfer and verification, with the work depending on your field mapping and how much history you choose to bring across.

  1. 1

    Export your Studies

    In Study Inspector, remove filters and download your Studies as an XLSX spreadsheet. Include Title and a stable reference such as Ref ID, DOI or PubMed ID, and retain Author and Publication Year. A CSV saved from that spreadsheet also works. If you cannot access this export, check with Nested Knowledge about what your account allows.

  2. 2

    Test, then load records

    First preview the import as a dry run so it checks the spreadsheet without saving records. Review the result before running the import for real. The importer accepts a plain-value, single-sheet XLSX or CSV and keeps every original column. Imported records start as pending, not approved, so you still need to verify and record decisions in the new system.

  3. 3

    Review import flags

    Check the import results and reconcile the records against your export. Look for columns that need mapping, conflicting repeated rows, and any records the import rejected. Identical repeated rows do not create duplicates, but a conflicting repeat rejects the whole import. Confirm that key fields and historical decision text came through as expected before relying on the new database.

  4. 4

    Run both systems briefly

    Keep Nested Knowledge available while you test the new workflow with your team. Compare key records and decisions, and confirm that your review process works with the imported data. Separate reviewer histories, attached PDFs, tags, appraisals, access permissions and statistical analyses are not recreated by the importer, so verify or map any of that history you need before ending the overlap.

  5. 5

    Switch off Nested Knowledge

    Once you have checked the records and are ready to work in the new setup, move your team to it and stop using Nested Knowledge for active review work. Keep an appropriate copy of your export and confirm that any history you decided to retain is available in the new process. Do not assume the import recreates every part of your former workflow.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding which history matters enough to bring across. The Studies import preserves original columns, but separate reviewer histories, attached reports, tags, appraisal and statistical work need their own mapping and verification. If you have Enterprise DNA run the setup, they scope that work with your team before switching.

Not ready for a call?

Get your Nested Knowledge switch plan by email

We will send you the step-by-step plan for moving your business off Nested Knowledge, 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 run it

Do it yourself, customise it, or have it run for you.

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /weekly-review and inspect the synthetic records
  4. 4 Import your Nested Knowledge Studies export, reconcile it and connect your database
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your review criteria, fields and exclusion reasons
  • check Your Nested Knowledge records mapped and reconciled
  • check Your documents and review process, with a web front end if you want one
  • check A different stack if it suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Connected to the systems your practice uses
  • check Your access, backups and review process set up for your team
  • check Ongoing changes as your evidence work changes
Talk to Sam

Questions

Instead of Nested Knowledge, answered

Does this replace our research judgement? expand_more

No. People decide eligibility, record appraisal and verify extracted values. The free version manages those records and checks their completeness. Your own version is scoped around your methods, including a separate blind-review process where required. It does not certify the research.

Will all our Nested Knowledge history move automatically? expand_more

The free import reads the Studies spreadsheet or a saved CSV and preserves every original column. It starts records as pending. Separate screening histories, tags, attached reports, appraisal and statistical work need their own mapping and verification. Enterprise DNA scopes that work with your team before switching.

What are we comparing on price? expand_more

The published business plans are $295 or $695 per user monthly, with separate Enterprise Plus and academic terms. Compare your actual invoice and the features you use. Our offer is a setup fee followed by a retainer for your own version. Hosting and agent use still have costs.

Can you build the report-reading and reviewer screens we need? expand_more

Yes. Enterprise DNA can build the web front end, document workflow and access controls around your team. We agree the scope with you, including blind review, source access and any statistical tools you need to keep connected.

What does the demonstration prove? expand_more

It shows real command results from synthetic library-review records: a disagreement, missing checks and review deadlines. It proves those workflows run. The reporting checks flag missing evidence for human review; they are not a complete PRISMA assessment or a regulatory approval.

Bring a review export and your Nested Knowledge invoice

Spend 30 minutes with Sam. We will look at your review process, the records you need to keep and the parts of Nested Knowledge you use. Then we can describe your own version and the work involved in moving it.

Book 30 minutes with Sam Get the free version

Literature Reviews for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Nested Knowledge?

Get your version built