Open your data locally
Start with CSV, Excel, experiment files, or a SQL database already available from your computer. There is no need to paste hundreds of rows into a chat window.
sales.xlsx · customers.csv · experiment-results.csv
Local-first AI data analysis
Analyze your data with AI without giving up control of your files.
Ask questions in plain English, run AI-generated Python locally, inspect every step, and keep the complete workflow in a reproducible notebook. MLJAR Studio currently supports local models through Ollama.
Your files
CSV · Excel · SQL
MLJAR Studio
Desktop workspace
Local LLM
Understands and writes code
Python
Calculates the real result
Reproducible notebook
Question + code + output + chart
The basic idea
A language model running on infrastructure you control works alongside Python, pandas, visualization libraries, and statistical packages.
Instead of asking an LLM to calculate everything in a text response, the model helps decide what analysis to perform and generates the Python code needed to do it. Python then runs against your actual data.
The distinction matters
The LLM handles reasoning, instructions, and code generation. Python performs transformations, statistics, visualizations, and machine learning.
In MLJAR Studio, generated Python is visible and every executed step can be preserved in the notebook, making the analysis inspectable and reproducible.
Your data
Files or SQL
Local LLM
Plans and writes Python
Notebook
Code, output, explanation
Verifiable answers
An LLM can translate an analytical question into a plan and code. Python makes sure the answer is calculated from the real data.
“Which customers increased their spending the most compared with last year?”
You usually do not want the language model to guess the answer. You want it to create code that reads the data and calculates the result. The AI makes Python easier to use; Python makes the analysis verifiable and repeatable.
From question to notebook
The language model and Python have separate jobs, and every stage stays available for inspection.
Start with CSV, Excel, experiment files, or a SQL database already available from your computer. There is no need to paste hundreds of rows into a chat window.
sales.xlsx · customers.csv · experiment-results.csv
Describe the result you need: compare groups, highlight a decline, merge files, clean records, or create a visualization.
“Show revenue by month and highlight the three largest declines.”
The model interprets the request, plans the analysis, and writes Python using pandas and the data-science libraries suited to the task.
Readable code remains available for review and editing.
Python executes against the real dataset and produces a table, statistic, chart, cleaned file, or machine learning model.
The result comes from computation, not a language-model guess.
Questions, generated code, outputs, charts, and follow-up analysis stay together in a notebook that can be reopened and rerun.
Inspectable · editable · reproducible
monthly = (
df.groupby("month", as_index=False)["revenue"]
.sum()
.sort_values("month")
)
monthly["change"] = monthly["revenue"].pct_change()
monthly.nsmallest(3, "change")Python groups the actual data, calculates month-over-month change, and returns the three largest declines.
Use cases
Use the same conversational workflow for everyday data preparation, rigorous analysis, and predictive modeling.
Clean spreadsheets, merge files, find duplicates, summarize columns, calculate KPIs, create charts, and detect unusual values.
Combine natural-language questions with SQL and Python, then continue the analysis after the selected data is loaded.
Use visible Python for t-tests, ANOVA, correlations, regression, confidence intervals, and outlier detection.
Ask for trends, distributions, comparisons, or relationships and let Python create the visualization from your data.
Prepare features, train models, evaluate results, and continue experimenting without moving the data to another tool.
Privacy and control
The biggest difference between a local and cloud LLM is where inference happens.
With a local model, inference can run on your computer or infrastructure you control. That gives you more control over model choice and can be useful when data cannot be uploaded to a third-party AI service.
Know the tradeoffs
Cloud models provide capable inference without requiring powerful local hardware. A local model needs enough RAM or GPU memory for the model you want to run, plus memory for Python and your dataset.
Your hardware defines the practical model size
Smaller models are easier to run; larger models often improve analysis quality but demand more memory.
Two separate choices
First choose the neural network that will generate responses. Then choose the software that loads and serves it.
The model is the neural network that understands your request and generates the response. Families such as Qwen and Gemma are examples used in current MLJAR Ollama documentation.
The runtime loads the model and makes it available to applications. These tools solve model serving; MLJAR Studio turns the served model into a practical Python data-analysis workflow.
A straightforward way to download and run models locally. It is the local provider currently documented and supported by MLJAR Studio.
Runs models locally and can expose local REST and OpenAI-compatible API endpoints.
Includes a local OpenAI-compatible API server powered by llama.cpp.
Provides an OpenAI-compatible server for serving models from GPU infrastructure.
Choosing a model
There is no single best model for every computer and every analytical task.
A small model may run comfortably on a laptop but produce weaker code. A larger model may perform better but require considerably more memory. Model selection should be based on real data-analysis tasks, not only generic chatbot benchmarks.
MLJAR LLM benchmark
Every model receives the same multi-step analytical prompts. The complete interaction is saved as a notebook, so you can inspect prompts, generated Python, outputs, errors, charts, final answers, and scores.
Local resources
The practical answer depends mainly on the model, but the language model is only part of your memory budget.
System memory used by the model, Python environment, and your dataset.
GPU memory available for acceleration when your machine has a compatible GPU.
Larger models generally need more memory and compute, but may provide stronger results.
Reduced-precision model versions lower memory requirements and can improve local speed.
Long conversations and substantial notebook context can increase memory requirements.
Remember to leave memory for Python and the dataset—not only the language model.
Flexible by project
You do not have to choose one provider for every notebook. Match the model location to the project and task.
Sensitive project
Local LLM
Everyday analysis
Local or cloud model
Difficult reasoning task
Powerful cloud model
Offline environment
Local LLM
MLJAR Studio supports different provider configurations. Current documentation includes MLJAR AI, OpenAI, Ollama Local, and Ollama Cloud, giving you control over which setup fits each project.
One desktop workspace
MLJAR Studio puts the AI conversation and local Python execution environment in one application.
MLJAR Studio runs on your computer and is designed around local Python execution and reproducible notebooks. With Ollama configured, the language model can run locally too.
Your files
CSV · Excel · SQL
MLJAR Studio + Local LLM
Conversation and reasoning
AI Data Analyst
Generates visible Python
Python results
Tables · charts · models
Notebook
Saved and reproducible
From analysis to application
After cleaning or analyzing the data, turn the useful workflow into something other people can use.
Let someone explore metrics and charts interactively.
Give users a conversational interface for a specific dataset or workflow.
Create an interface for files, cleaning, calculations, or reports.
Expose the useful part of an analysis without asking users to run a notebook.
MLJAR Studio integrates with Mercury for turning notebooks into interactive dashboards, chat apps, internal tools, and web applications.
FAQ
Yes. A local LLM can understand analytical questions and generate Python code, while Python performs calculations and transformations against the actual dataset.
Not necessarily. A more reliable approach for structured data analysis is to let the model generate Python and let Python perform the calculations against the real data.
Yes. MLJAR Studio is a desktop application and executes the analysis in the local Python environment. Generated code is visible and can be inspected and reused.
Yes. MLJAR Studio currently supports and documents local LLM connections through Ollama.
No. You can ask questions in plain English. Knowing Python gives you additional control, but the AI Data Analyst can generate and execute Python for you.
It depends on your hardware and the complexity of the analysis. Coding quality, reasoning, memory use, speed, and the ability to complete multi-step data-analysis tasks are all important.
Yes. MLJAR Studio’s AI Data Analyst can work with local structured files, including CSV and Excel, as well as SQL database connections.
Yes. Notebook-based analysis in MLJAR Studio can be turned into an interactive web application using Mercury.
Start analyzing locally
MLJAR Studio gives you a desktop environment for AI-assisted Python data analysis with visible code, reproducible notebooks, and support for local LLMs through Ollama.
Keep the code, data, and workflow under your control.