Self-hosted experiment deployment for university labs.
Neurotist is installed on your institution's own infrastructure so researchers can upload browser-based experiments, collect participant data, and export results without maintaining fragile custom servers.
Self-hosted, but not self-managed.
Temporal Decision Task
Stable across experiment version updates.
Every lab solves deployment differently.
Behavioural science labs can usually build the experiment itself. The fragile part is what happens around it — and it rarely looks the same twice.
Personal servers
One PhD student runs a study from a personal server nobody else has access to.
Temporary cloud buckets
Another uploads experiment files to a temporary cloud bucket that expires mid-semester.
Custom endpoints
Another sends participant data to a custom PHP endpoint written for a single project.
No overview for IT
IT has no central view of where studies run, where data lives, or who maintains them.
Inconsistent exports
Data export formats differ across projects, making analysis and auditing harder.
Knowledge walks out
The whole setup breaks when the original student leaves the lab.
Neurotist gives labs a stable deployment layer for browser-based studies — so this work doesn't have to be improvised every time.
From experiment folder to participant data.
Create a study, upload the experiment bundle, preview the task, share the participant link, and export collected responses. Neurotist provides the infrastructure around the experiment without replacing the tools researchers already use to build it.
Create a study
Start a new study in the dashboard. Studies group an experiment, its participant link, collected sessions, and exports in one place.
Upload your experiment bundle
Researchers upload a browser-based experiment folder, such as a jsPsych task or a custom HTML/JavaScript study. Neurotist validates the structure and detects the entry point.
tdt-jspsych-v4.zip
Drop folder or ZIP here · entry point detected: index.html
Run a preview and validate
Open a private preview of the study to check the task flow, data capture, and completion before sharing the link with participants.
Press the spacebar to begin
Generate a participant link
Each study receives a controlled participant URL that can be used in recruitment platforms, email, or internal lab workflows. The link stays stable across experiment updates.
Export collected data
Responses can be exported in structured formats for analysis in R, Python, SPSS, or JASP. Exports are consistent across studies.
Installed on infrastructure your institution controls.
Neurotist runs on university-controlled infrastructure. Your institution keeps control over deployment, data storage, backups, and access policies, while Neurotist provides the software package, installation support, updates, and technical assistance.
Your data stays with you
Participant data, experiment files, and exports remain in the storage environment your institution approves.
Docker-based deployment
Defined services, clear storage configuration, and standard reverse proxy / HTTPS setup that IT can review.
We handle install and updates
Neurotist comes with installation support, update guidance, and technical assistance. The lab doesn't maintain it alone.
A software package with installation and support.
Neurotist is delivered as a complete package — not just an app, but the deployment, configuration, and support around it.
- Neurotist application
- Docker-based deployment
- Database and storage configuration
- HTTPS / reverse proxy setup
- Researcher and admin accounts
- Experiment upload workflow
- Participant data collection
- Export tools (CSV / JSON)
- Software updates
- Technical support
- Installation documentation
- Architecture review materials for IT
Made for labs that already build experiments, but need better infrastructure.
Researchers
Upload browser-based experiments, share study links, collect data, and export results — without touching server configuration.
PIs
Standardize deployment across projects instead of relying on one-off technical setups that disappear with a student.
IT teams
Install a clear Docker-based package with defined services, storage, and update procedures. No black box.
Data protection / ethics
Keep participant data within the approved institutional environment, with a documented deployment to review.
A concrete installation process.
Deployment is handled with your IT team — not handed off as a download link. Here's how it typically proceeds.
Scope and review
We discuss deployment scope, server environment, storage, access policies, and support requirements with your IT and lab contacts.
Provide the package
Neurotist is delivered as a Docker-based package with configuration templates, database setup, and documentation.
Install together
We support installation on your infrastructure, including reverse proxy / HTTPS configuration and storage setup.
Onboard researchers
Researcher and admin accounts are created, and the first study workflow is walked through with the lab.
Updates and support
Ongoing updates, technical assistance, and documentation are included with the license.
Licensed for your institution.
Neurotist is sold as a commercial software license for research groups, departments, and universities. The license includes installation support, updates, and technical assistance. Deployment scope and support requirements are discussed before quotation.
- Institutional software license
- Installed on your infrastructure
- Updates and support included
- No participant credits, no online checkout
Institutional license
Lab · Department · University
Quote provided after scope discussion.
Built from inside behavioural science.
The builder
Behavioural science background. Built Neurotist to solve a problem faced in real labs.
Neurotist was created from the recurring friction of running browser-based experiments in academic labs: researchers can build studies, but deployment, data collection, server setup, and maintenance often become improvised technical work. The goal is not to replace experiment builders such as jsPsych, lab.js, or PsychoPy exports. The goal is to give labs a stable place to deploy, collect, and manage those studies.
Built by someone who has watched too many studies break the week a PhD student hands in their thesis.
See the workflow before proposing it internally.
We can walk through the product, deployment model, and technical requirements with researchers, PIs, or IT staff.
What a demo covers
- 20-minute product walkthrough
- Technical deployment discussion
- Example study workflow
- Quote after scope discussion
Questions researchers, PIs, IT, and DPOs usually ask.
Is Neurotist open source?
No. Neurotist is licensed software that can be installed for an institution-controlled environment. The source is provided to your institution under license for review and maintenance.
Where is participant data stored?
In the institution-controlled deployment, using the storage environment agreed with your university during setup and review. Data does not leave your infrastructure.
What experiment formats are supported?
Any browser-based experiment that runs from static files — jsPsych, lab.js exports, PsychoJS builds, and custom HTML/JavaScript tasks. If it runs in a browser, Neurotist can host and collect data for it.
Can it run jsPsych studies?
Yes. jsPsych is one of the most common formats Neurotist is designed around. Upload the build output and Neurotist handles hosting, links, and data capture.
Does Neurotist replace jsPsych, lab.js, or PsychoPy?
No. Those tools build the experiment. Neurotist is the deployment, data collection, and management layer around them. Researchers keep using the builders they already know.
What does installation require?
A server or VPS your institution controls, Docker, a PostgreSQL database, and object storage. We support the installation process and provide documentation and configuration templates.
Can IT review the architecture?
Yes. We provide architecture and deployment materials during evaluation so IT, security, and data protection teams can review the setup before installation.
Are updates included?
Yes. Software updates, update guidance, and technical assistance are included with the institutional license.
Can we run a pilot first?
Yes. A pilot deployment for one lab or project is a common starting point. We scope it together and discuss the path to a broader institutional license afterwards.
How is pricing determined?
Pricing depends on deployment scope (lab, department, or institution), the number of researchers, the server environment, and support requirements. We discuss scope first, then provide a quote. There is no online checkout.
Tell us about your lab or institution.
Send a message and we'll get back to you about demos, licensing, or the technical review process for your institution.