AI News

Databricks Releases Guide to Running Tabular Foundation Models, Comparing Five Models and Fine-Tuning Workflows

Unite.AIUpdated Nov 17 03:10

AI summary

On November 16, 2026, Databricks released a technical guide explaining how to run tabular foundation models on AI Runtime, along with a public repository for comparing five models—TabPFN, TabFM, TabICL, Nori, and KumoTabular—and testing fine-tuning workflows. The guide notes that these models use labeled rows as context during zero-shot inference, predicting without updating parameters, but GPU memory grows with the number of rows and features, and the cost per prediction is higher than XGBoost on CPU; the main savings come from engineering and maintenance time. Regarding licenses, TabICLv2, Mitra v2, and KumoTabular are commercially usable, while the weights of TabFM and TabPFNv3.5 are non-commercial.

Why read this

AI score 52

Databricks' guide compares the architectures, GPU costs, and licenses of five tabular foundation models under a single evaluation framework, making it easier for teams to assess deployment conditions.

Topics

Tags

Body

Databricks published a technical guide on November 16, 2026 for running tabular foundation models on AI Runtime, accompanied by a public repository for comparing five model providers and testing fine-tuning workflows.

The public solution accelerator supplies notebooks and a shared test harness for TabPFN, TabFM, TabICL, Nori and KumoTabular. Its target is a persistent enterprise workload: predictions from tables used for credit risk, customer churn, demand forecasting and predictive maintenance, where conventional development can create a separate training and retraining pipeline for every task.

Tabular foundation models (TFMs) instead arrive pretrained on millions of diverse synthetic datasets. In zero-shot inference, labeled rows become context for rows needing predictions; transformer attention relates the new rows to those examples and returns predictions in one forward pass without parameter updates. Fine-tuning remains an option for teams that want to update the pretrained weights on a proprietary dataset.

Architecture, GPU Costs and Licensing

Specialized tokenizers map numerical, categorical and boolean features into a shared representation. TabPFNv2 alternates attention within rows and columns to learn interactions, but its computational cost rises rapidly as samples and features increase.

The TabICL research paper takes a different route, building fixed-dimensional row embeddings through column-then-row attention before dataset-level in-context learning. Its authors report handling up to 500,000 samples and 500 features, matching TabPFNv2 in their classification benchmark evaluation, running as much as 10 times faster, and surpassing both TabPFNv2 and CatBoost on 53 datasets with more than 10,000 samples. The evaluated version was limited to classification, while the benchmark’s holdout-tuned single models did not capture potential gains from cross-validated ensembles.

Memory remains an operational constraint even with row compression. Because in-context learning supplies the training set with each prediction, GPU memory demand grows with the number of rows and features. Databricks recommends testing accuracy, inference latency, memory use and cost on an organization’s own data, and says GPU inference costs more per prediction than running XGBoost on a CPU. The potential saving is engineering and maintenance time; the continuing expense is accelerated compute.

Licensing is another deployment filter. The guide classifies TabICLv2 under BSD 3-Clause, Mitra v2 under Apache-2.0 and KumoTabular under OpenMDW-1.1 as commercially permissive. TabFM and TabPFNv3.5 weights are listed as non-commercial, with commercial use subject to agreements with their creators. The repository separately distinguishes TabPFN’s commercial hosted API from its non-commercial weights.

Shared Evaluation and Production Deployment

The reference implementation gives model comparisons a common basis. Every supported implementation reads the same synthetic retail and consumer-packaged-goods datasets, uses identical training and test splits, and logs common metrics and scikit-learn baselines to one results table. Examples cover classification, regression, outlier detection and lag-based forecasting where the individual model supports them.

Compute requirements differ. Self-hosted TabFM, TabICL, Nori and KumoTabular can run on serverless CPUs, but the repository recommends GPUs for practical performance. Its TabPFN example calls a hosted API, for which CPUs are sufficient, while a TabICL example lets CPU pipelines offload inference to a dedicated GPU serving endpoint.

AI Runtime predates the guide: Databricks introduced it in public preview on March 19, 2026, as a serverless stack for distributed GPU training. Databricks says its on-demand H100 GPUs can support TabPFN-3 at up to 1 million rows by 200 features. Notebooks, Lakeflow Jobs, MLflow experiment tracking and GPU-utilization observability sit alongside native Docker support and remote SSH through the Databricks CLI.

A KumoTabular fine-tuning demonstration exposes GPU usage and MLflow metrics in a notebook and registers the resulting model in Unity Catalog. For production, the guide describes high-throughput batch pipelines or auto-scaling real-time REST endpoints through Model Serving, with Unity Catalog managing model versions and governance.

The result is a repeatable route for testing whether TFMs can reduce per-task ML work without moving data into separate GPU tools. The business case still rests on measurements the repository cannot supply universally: accuracy on an organization’s own tables, usable license terms, and whether lower engineering overhead offsets the continuing cost of GPU-backed predictions.

Source

Unite.AI