Browser-Local AutoML for Private CSV Model Training

What browser-local AutoML means

Browser-local AutoML moves the first modeling loop into the browser. Instead of starting with cloud training infrastructure or a Python notebook setup, users can upload a CSV, inspect columns, choose a target, configure preprocessing, train candidate models, compare metrics, and review warnings in one local workflow.

Browser-local is the execution boundary: during normal MLdeck CSV training workflows, raw CSV rows are processed in the browser rather than uploaded to a cloud training job. Browser-based is the broader user experience of doing the workflow in a web browser.

This approach is designed for tabular model exploration and validation-aware review. It helps users compare models, inspect metrics, review data-quality warnings, generate local Advisory Playbooks, and export ONNX-oriented packages with schema, manifest, and parity-review context.

When browser-local AutoML fits

Browser-local AutoML is a strong fit for early CSV exploration, education, privacy-sensitive review, baseline comparison, and export package testing. It helps users answer practical questions before committing data to heavier infrastructure.

Start with Data Quality for Machine Learning when a CSV may contain missing values, leakage risk, identifier-like columns, or target imbalance. After training, review AutoML validation evidence and AutoML export artifacts before using results outside the browser-local workflow.

How MLdeck keeps raw CSV workflows local

Core CSV profiling, preprocessing, browser-side model training, model comparison, and local Advisory Playbook generation are designed to run in the browser during normal workflows. Raw CSV rows do not need to be uploaded to a cloud training job just to assess whether a dataset has signal. One network dependency exists at training start: the browser ML runtime may be downloaded from a third-party CDN. This is a code download — raw CSV rows and file bytes are not sent to it. See the privacy-first page for details.

Privacy-first does not mean risk-free. Users remain responsible for local device security, browser extensions, downloaded artifacts, internal data policies, and any external systems used after export. Derived artifacts such as reports, schemas, and model files should be handled carefully when source data is sensitive.

Validation-aware model review

MLdeck surfaces baseline-aware model comparison, data-quality warnings, leakage-risk review, feature importance, and evidence labels so users can interpret results with context. Exploratory and prequential metrics are useful for initial review, but they are not independent holdout evidence.

If the best model does not beat the baseline, MLdeck makes that visible so users can improve data quality, feature selection, target definition, or model quality. For important decisions, users can pair browser-local evidence with stricter holdout, temporal, group-aware, or external validation review.

Local Advisory Playbooks and optional AI Copilot

MLdeck’s Advisory Playbook has two layers. Sections 1-10 are generated locally in the browser from the current run metadata. Optional AI Advisory Notes can be added only when the user enables Optional AI Features and grants metadata-sharing consent.

Optional AI Copilot features can explain metrics, validation limits, feature importance, export readiness, and next experiments. AI guidance uses sanitized metadata only after consent and does not inspect raw rows or model binaries. Metadata that may be sent includes dataset name, column names, target name, model names, metrics, preprocessing steps, feature-importance names, validation/export status, and the user’s Copilot question. Raw CSV rows, row samples, uploaded file contents, ONNX/PKL/model binaries, Docker/package binaries, prediction curves, and large artifacts are not sent by those optional AI features.

Playbooks and Copilot answers are snapshots of a run context. If the dataset, target, features, model, validation status, or export status changes, older Playbooks or Copilot answers may be marked as previous-run or stale.

ONNX-oriented export packages for external validation and testing

MLdeck can generate ONNX-oriented export packages from supported browser-local training workflows. These packages include schema and metadata context for external validation, schema review, parity testing, and runtime experiments.

ONNX artifact availability is reported alongside export metadata so users can distinguish artifact creation from parity evidence, runtime behavior, and downstream validation status.

Limits and responsible use

MLdeck is a live browser-local AutoML product for practical CSV-based machine-learning workflows. Browser CPU and memory limits apply, and large or high-dimensional datasets may require dedicated infrastructure. Use MLdeck to profile, train, compare, validate, report, and export from a local-first workflow that keeps raw CSV data in the browser during normal training.