ANYinstrument
We don't keep an instrument list. You don't need one with ANYinstrument.
If an instrument exports a data file, Uncountable can import it. Describe the file to Bodie in plain English once, and every result after that lands next to the samples and experiments that produced it.
Plain-English setup
describe the export to Bodie once
Same result every time
saved imports run with no AI step
Results in context
attached to the sample and experiment
Deployed by 175+ enterprise product development teams
Deployed by Enterprise R&D and Innovation Teams
A supported-instruments list is out of date the day you buy a new one
Most labs run a mix of instruments: a rheometer bought last year, a particle size analyzer from 2009, a spectrophotometer whose export changed with the last firmware update. A vendor's supported list covers some of them. The rest get re-typed or left in a folder nobody searches, so their results can't be compared with past work, used in a model, or found when a customer asks why a batch behaved differently.
Set it up once in plain English. It runs the same way every time.
Upload one export from the instrument and tell Bodie which values matter. Bodie builds the pipeline and shows a preview before anything is saved. Every file after that runs through the same steps, with no scripting and no AI involved.
Anyone your admins give pipeline access to can set one up.
Pipelines read CSV, TXT, XLS, XLSX and XML exports, tables in Word documents, and ZIP archives, so most instruments work from the file they already produce.
Results land on the experiment and sample they belong to, ready to compare with past work, chart or use in a model.
Adding an instrument becomes a setup task for the lab instead of a software project.
One import per instrument. Results that stay usable.
ANYinstrument removes the question of whether an instrument is supported. Uncountable imports from the instrument you have, including the ones no list will ever name.
The old way
Check the vendor list, wait for a connector, or re-type the results
Results copied from exports into spreadsheets, then into the notebook
Transcription mistakes found weeks later, if at all
Past results found by file name and date on a shared drive
With ANYinstrument
Describe the export to Bodie and save the import the same day
Results imported and attached to the sample or experiment they belong to
A file that doesn't match stops the import instead of writing bad data
Results searchable alongside the formulations and conditions behind them
Instruments labs import from: examples, not a limit
Chromatography
HPLC, UHPLC, GC, GC-MS, LC-MS, GPC/SEC
Peak areas, retention times, purity and molecular weight distribution.
Spectroscopy
FTIR, UV-Vis, NIR, Raman, NMR, ICP-OES, XRF
Spectra, absorbance and elemental composition.
Thermal and rheology
DSC, TGA, DMA, rheometers, viscometers
Glass transition, weight loss, viscosity curves and yield stress.
Particle and mechanical
Laser diffraction, DLS, BET, tensile and hardness testers
Particle size distribution, surface area, strength and elongation.
Color and appearance
Spectrophotometers, colorimeters, gloss and haze meters
Lab values, delta E, gloss and haze.
Electrochemistry and QC
Battery cyclers, potentiostats, pH meters, Karl Fischer titrators
Capacity, cycle life, pH and moisture.
Describe it once, import every file
Watch an instrument pipeline get built from a plain-English description. Upload a sample export from any instrument, tell Bodie what the file contains and where each value belongs, and it builds the pipeline for you. Every file that instrument produces after that comes in the same way: parsed into structured results and attached to the right sample and experiment, with nobody retyping values. The same approach works for any instrument in your lab.
Your instrument data should outlive the project that created it.
When every instrument feeds the same record, results stay ready for comparison, modeling and investigations long after the project that produced them ends.
FAQs
If the instrument exports a data file, yes. Pipelines read CSV, TXT, XLS, XLSX and XML files, tables in Word documents, and ZIP archives. Uncountable doesn't rely on a fixed list of supported models: you describe the export to Bodie once and save it as the pipeline for that instrument.
No. You explain in plain English which values matter and where they sit in the file. Bodie builds the import and shows a preview before you save.
No. Bodie helps build the import once. After that, each file runs through the saved steps, so the same input always gives the same output.
The preview stops with an error and nothing is written, so mismatched data never lands in your records. Fix with Bodie finds the cause and updates the pipeline.
Anyone your admins give pipeline creation access. Everyone else uploads files to the saved pipelines, previews the values and imports them.
Bring us the instrument you're worried about
Send an export from your hardest instrument. We'll show it importing on your demo call.
