Unpublished work stays in house
Protocol records for work you have not published yet stay on a server your lab controls.
Host the ReplicateScience protocol library on a server your lab controls. Protocol records, evidence quotes and reviews stay on your network, and the library works without internet access.
Researcher computers
Search, review and export protocols
Notebooks and scripts
Query the API from your pipelines
ReplicateScience server
Protocol library, extraction and reviews
Backups
Storage your IT team selects
A protocol library can hold work that is not public yet. Offline, it runs on systems your lab already manages.
Protocol records for work you have not published yet stay on a server your lab controls.
Methods text is processed on your own hardware, or through your organization's own cloud AI account.
Labs on networks without internet access can search, review and export protocols over the local network.
When a collaborator or a data-use agreement asks where methods are kept, you can point to your own server.
Your IT team decides when updates go in, so extraction and completeness scores stay the same through a review cycle.
Notebooks and scripts call the same REST API over your local network.
Your IT team installs ReplicateScience on a server in your lab or data center, or on one workstation.
Researchers and reviewers sign in through your directory or single sign-on. Your IT team manages who has access.
Protocol extraction runs on your own hardware, or through your organization's own cloud AI account.
Updates arrive as signed files. Your IT team installs them when ready and can roll back to the previous release.
The library database is copied on a schedule to storage your IT team selects.
Protocols look and behave the way they do on the public site.
Structured protocols
Each experiment is parsed into steps, parameters, materials and subjects.
Evidence quotes
Every step, parameter and equipment match links back to a source methods quote.
Completeness scores
Scores show which details are missing instead of filling the gaps.
Equipment matching
Equipment mentions are matched against catalog records and never invented.
Reviewer approval
A reviewer checks steps, evidence and equipment matches before a protocol is listed.
API and exports
A REST API with structured protocol JSON, plus JSON and CSV export.
We plan the offline setup with your IT team, including server size, where extraction runs and when you go live.
It suits labs, research cores and institutes that keep unpublished methods on their own network.
No. Searching, reviewing and exporting protocols all work over your own network. If you run extraction through your organization's own cloud AI account, only that step connects out, to your account.
On the server where ReplicateScience is installed, inside your network. Backups go to storage your IT team selects.
No. The offline edition keeps its own library on your server and sends nothing to the public site.
Extraction runs on your own hardware, or through your organization's own cloud AI account if you prefer. A reviewer still checks each protocol before it is listed.
Each update is a signed file. Your IT team installs it after a backup and can return to the previous release. Closed networks can load the file from local storage.
That depends on how many people use the library and whether extraction runs on site. We size it with your IT team.
Your lab or institution holds the license, and it is checked on your own server with no internet connection. Terms are agreed during setup.
Yes. The public library at replicatescience.com stays free to read, with a free API tier for developers.
Tell us about your lab, how many people will use the library, and whether extraction should run on site or in your own cloud account. Our team will map out the install with your IT group.
Or email info@conductscience.com with the subject “ReplicateScience Offline edition”.