About
About Lablate
Lablate comes out of a problem encountered at the bench: recording an experiment, plotting the data, and writing it up are three separate jobs in three separate applications, and nothing connects them.
Why it exists
A single experiment usually means writing notes in OneNote, working the numbers in Excel, and assembling the report in PowerPoint or Word. Every time a figure changes you export it again, screenshot it, and paste it in again. That copy-and-paste time eats into the research itself.
Lablate puts writing, data, plots, and the report on one screen, so that when the data changes the figure and the report change with it. The goal is a practical tool that matches how bench work actually happens.
Who builds it
- Name: Atsushi Sakurai (桜井 惇)
- GitHub: Atsushisaku
- Background: a working researcher who handles experimental data day to day
- Contact: lablate.app@gmail.com (expect a reply within 3–4 business days)
Formal business-operator details are set out in the Terms of Service.
Product principles
- The data belongs to the person who made it
No research data is ever stored on Lablate's servers. It lives on your own machine or in your organization's cloud storage, such as OneDrive. Your institution's security policy stays in force, unchanged.
- No vendor lock-in
Everything is saved in standard formats — Markdown, CSV, JSON, PNG. If you stop using Lablate you can take the files straight out of the folder and open them elsewhere. Not being tied to the product is the point.
- Your data outlives the service
Because no research data is held on the operator's servers, the files in your folder stay exactly where they are even if Lablate shuts down one day. Copy the folder and you have already migrated. The design itself is the answer to “what if this service goes away?”
Where things stand
Lablate is currently a free beta. It is developed continuously alongside feedback from people doing research. If something is off, or there is something you need, please get in touch.