LabSpace is where labs and their people live, from finding the lab, to running the work, to publishing the result. Built for PhD students, postdocs, research staff, and principal investigators.
Most research software begins after you already have a lab, a PI, and a budget. LabSpace begins with lab discovery and applications, then carries the same people and the same work through projects, experiments, compute, and manuscripts.
Labs publish a real profile: principal investigator, institution, department, focus, topics, methods, team, and outputs. Researchers browse labs and open positions, save what fits, and apply with a structured profile instead of a cold email.
Inside the lab workspace, projects carry members, tasks, files, meetings, channels, and an attached environment. Experiments are named lines of inquiry, and each run records what would otherwise be lost.
A manuscript editor with templates, author lists, and LaTeX compilation sits next to the work that produced the result. Venues and submissions track a paper from target selection to decision.
Find labs and open positions in one place, apply with context, and keep your work in a workspace that survives the move from one project to the next.
Publish a lab profile that attracts the right applicants, review applications in a pipeline, and run the lab with its projects, experiments, files, and manuscripts together.
Organizations, departments, SSO connections, audit logs, retention policies, and data subject request records exist as product controls. They are not compliance certifications.
An electronic lab notebook is a system of record: it keeps the protocol and the observation. LabSpace is a system of work that also covers the two moments most lab software leaves out — finding the lab, and turning the work into a publication.
| Question | Electronic lab notebook | LabSpace |
|---|---|---|
| Where it starts | Your first day at the bench | Before you have a lab: discovery and applications |
| Who it is built for | Institutional procurement and compliance | The researcher, the PI, and the lab |
| Run provenance | Notes and attachments | Code commit, dataset version, environment image, parameters, metrics, artifacts, and logs on every run |
| After the experiment | Export and move on | Manuscripts, LaTeX, venues, and submission tracking |
| Compute | Separate cluster and cloud accounts | Bring-your-own-cloud environments with quotas and cost ceilings |
| Regulated GxP and clinical use | Purpose-built, certified vendors | Not a LabSpace use case |
A lab can keep an institutional notebook for the record it is required to keep and use LabSpace for the work itself.
Browse labs and open positions. Create a free account when you are ready to apply or run a lab.
