Coursework figure
Import a lab CSV, create named variables, build an X&Y card, set log axes if the data needs them, annotate, and export a vector PDF.
Built for
A thesis figure due Friday, a manuscript panel that has to survive peer review, or an experiment that can't leave the building - one native Mac app covers all three. Pick the one that's yours.
The fast path
Import a messy lab CSV, name the variables that matter, and build an X&Y plot or a fitted histogram - without rebuilding the pipeline in pandas every time you reopen it.
Vector PDF export with embedded fonts at journal DPI is in the Free tier, so the first submission-ready figure is never behind a checkout.
Three ways in
Import a lab CSV, create named variables, build an X&Y card, set log axes if the data needs them, annotate, and export a vector PDF.
Save the project, reopen it weeks later, adjust the card, and export again - without hunting for the notebook cell that made the old plot.
Get the analysis shape right in the app, then read the Python execution trace - the exact code Autoplot ran - when you want to understand or modify the pipeline.
FAQ
Yes - and that is the point. It matters to understand the first principles of the analysis, not just the figure that comes out.
Autoplot is not a replacement for learning Python; it is a replacement for losing an afternoon to pandas documentation when the real task is a deadline figure. Every operation the assistant runs leaves a Python execution trace you can open, read, and copy - so you can study the exact code that produced your result.
Usually, yes. Free is permanent - not a trial - and covers:
Plus opens the heavier surfaces - CDF and CCDF, scaling, heat maps, correlations - if your work grows into them.
Yes. Autoplot exports vector PDF with embedded fonts at journal DPI, plus PNG and JPG. Annotations live with the figure and move when you restyle, so the version you hand in matches the one you tuned.
Yes. A project file preserves your imported files, variables, cards, annotations, and chart appearance. Reopen it, adjust a card, and re-export - you are editing the analysis, not reconstructing it from memory.
Pricing is uniform at launch, with no academic discount yet - but a student discount is coming soon. In the meantime, Free is permanent and covers what most coursework needs.
The app follows the steps you would take anyway: import, name variables, build a card, fit, annotate, export. When you are unsure how to express an analysis, describe it to the assistant in plain language - it proposes a structured operation and waits for you to confirm before anything runs.
CSV, TSV, and text files, with a parsing preview before you commit. Inspect delimiters, headers, and skipped rows, then promote columns to named variables.
Why scientists
Power-law fits with MLE exponents and KS-selected x_min, log-binned distributions, CDF and CCDF, E-S scaling, heat maps, and correlation matrices - built in, not assembled by hand from a Python package each time.
Project files preserve variables, cards, workspaces, annotations, and appearance, so a result you found last month reopens exactly as you left it.
Three workflows
Build X&Y and CDF/CCDF cards, inspect tails on log axes, add Xmin diagnostics, compare candidate fits, and export the figure - or copy the Python the assistant generated.
Move from selected variables into correlation matrices or heat maps when the problem is inherently 2D or many-variable, without flattening it into one generic chart.
Use Compose to assemble X&Y, histogram, CDF, heat-map, E-S scaling, chart, and correlation sources into paper-backed multi-panel boards, exported as a single figure.
FAQ
Yes, in two practical ways:
Free covers the core; Plus opens the advanced surfaces.
Power-law fits estimate the exponent by maximum likelihood with an x_min selected by KS distance, alongside log-binned distributions and CDF/CCDF views. It is the analysis you would otherwise assemble from the powerlaw package and Matplotlib - here it is a card that stays part of the saved project, with the generated Python available to inspect.
Your intent and your dataset's schema - column names, types, and sizes - never the raw values. It proposes a structured operation; nothing mutates the project until you confirm. The operation then runs locally and leaves a Python execution trace, so you can see exactly what produced the result. Data privacy
An open-weights model - currently QWen 3.6 35B, hosted on deepinfra.com - chosen because it does not train on your inputs. It is a narrow analysis assistant gated behind your confirmation, not a frontier chatbot you paste data into.
WaveMetrics ended Mac support at Igor Pro 10: version 9.05 is the last Mac release, and on Apple Silicon it runs only through Rosetta.
Autoplot is honestly not at feature parity - Igor's macro language and waveform model have no like-for-like replacement here. What it is: a native Mac scientific workstation built around modern fitting, plotting, reproducibility, and a conversational assistant Igor does not have. CSV and text imports work today; .ibw and .pxp import remain roadmap items.
Native SwiftUI for Apple Silicon, with document-based projects that open and save like any Mac file. Numerical work runs through a persistent in-app Python engine - NumPy, SciPy, Matplotlib, pandas - so the stack underneath is the one you already trust.
Most working scientists will.
Local-first
The local toolkit - import, variables, workspaces, fits, plots, Compose, and export - runs entirely on the Mac. By default, nothing remote touches the data.
The hosted assistant is opt-in and account-based; turning it off removes no part of the non-AI feature set.
SwiftUI shell
Persistent Python engine
Local project documents
Apple Silicon focus
Three situations
Analyze tabular results without uploading files to a shared dashboard or an external AI workspace. The boundary is a single, explainable line.
Use a native Mac app rather than a per-seat BI platform when the job is scientific plotting - an experiment, a curve, a figure - not a dashboard rollout.
Intent plus schema may leave for the hosted assistant; raw values stay local, behind a confirmation gate. Simple enough to put in front of compliance.
FAQ
Yes - and by default the answer is reassuring. The local toolkit imports, transforms, fits, plots, and exports entirely on the machine; nothing remote touches the data unless you turn on the hosted assistant.
If hosted AI is off-limits in your environment, disable it and the workstation stays fully useful. The boundary is one explainable line, not a diagram nobody can follow.
Your intent and the dataset's schema - column names, types, and sizes - never the raw values. The assistant proposes a structured operation that waits behind a confirmation gate; once you approve it, it runs locally and leaves a Python execution trace you can inspect.
Yes. The non-AI toolkit works without a network connection. Only the optional hosted assistant, account, and billing paths reach out, and disabling the assistant costs you no local features.
No. Raw values never reach the AI layer, and the open-weights model behind the assistant does not train on inputs. There is no cloud workspace accumulating your experiments.
No. Project files are local and portable, so the analysis is never held hostage in a vendor's cloud. Autoplot is a tool you run, not a platform you rent a seat on.
Yes. The hosted assistant on Apple Private Cloud Compute is upcoming, for on-device-grade privacy without giving up the conversational layer.
It is not a business-intelligence tool, not a notebook environment, and not a general chat AI. It is a native Mac workstation for scientific plotting and analysis. If the job is a dashboard rollout or an enterprise ML platform, this is the wrong tool - and we would rather say so.
Download it directly or from the Mac App Store and assess the local toolkit and the Plus feature set without any cloud onboarding. The data path needs no review unless you choose to enable the hosted assistant.
Join the waitlist for the launch build and the first honest changelog.