Softwr

Machine Learning · head to head

DVC vs JMP

DVC logo

DVC

Machine Learning

Git-style versioning for data sets and models, with the files kept in object storage

From
Free
Rated
-
JMP logo

JMP

Machine Learning

Desktop statistical and design of experiments software from a SAS subsidiary

From
Free
Rated
-

The short version

  • Each has a real cost: DVC dVC knows only about files that were added through DVC, so one person copying data in by hand leaves a pipeline that reproduces to a different answer with no error and nothing to indicate which result is the real one.; JMP it is a desktop application holding the working table in memory, so a data set that outgrows the workstation has no in-place upgrade path, only a move to a different tool and a different skill set.
  • They diverge on capability: DVC covers Pointer-file versioning, JMP covers Custom design of experiments.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which DVC and JMP actually diverge.

Attributes where DVC and JMP differ
AttributeDVCJMP
Pricing modelopen-sourcesubscription
PlatformsLinux, Mac, WindowsMac, Windows
Founded20181976

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Machine Learning).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in DVC

  • Pointer-file versioning
  • Remote storage backends
  • Pipeline definitions
  • Stage caching
  • Experiment tracking
  • Metrics and plots comparison
  • Data registry pattern
  • Content-addressed cache

Only in JMP

  • Custom design of experiments
  • Linked interactive graphics
  • Analysis platforms
  • Quality and process tools
  • Graph Builder
  • JSL scripting
  • Scoring code export
  • Predictive modelling in JMP Pro

What people use each for

The jobs each tool is most often brought in to do.

DVC

  • Making a model reproducible by tying the exact data set version, code commit and parameters together in one Git historynot JMP
  • Keeping large training data out of Git while still having a repository that describes it preciselynot JMP
  • Skipping expensive preprocessing stages that have not changed, when iterating on a later stage of a pipelinenot JMP
  • Teams that need reproducibility but cannot get approval or budget to stand up a platform for itnot JMP

JMP

  • Planning a physical experiment where each run is expensive, and the question is which twelve runs to perform rather than how to model data you already havenot DVC
  • Process capability and control chart work in a manufacturing quality function that has to produce evidence for a customer or regulatornot DVC
  • Exploratory analysis by an engineer or scientist who will not write code but needs more than a spreadsheetnot DVC
  • Semiconductor, chemical and pharmaceutical development groups where JMP is already the shared language for reporting resultsnot DVC

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

DVC

  • DVC knows only about files that were added through DVC, so one person copying data in by hand leaves a pipeline that reproduces to a different answer with no error and nothing to indicate which result is the real one.
  • Every tracked revision writes a new pointer into Git and a new copy into the remote cache, so a data set revised daily accumulates full copies in object storage and the storage bill grows with the length of the history rather than the size of the data.
  • Merge conflicts in dvc.lock and dvc.yaml are routine on parallel branches and are unreadable to anyone who has not learned the format, which in practice means the person who introduced DVC resolves all of them.
  • Checking out a large data set materialises it in the working directory, so a laptop working against a repository with several hundred gigabytes tracked needs disk for the workspace and the cache together, and the reflink or hardlink optimisations that avoid doubling that are filesystem-dependent.
  • It has no access control of its own and inherits whatever the remote grants, so a repository everyone can read plus a bucket everyone can read means everyone can reconstruct every historical version of every data set, which is frequently not what was intended.

JMP

  • It is a desktop application holding the working table in memory, so a data set that outgrows the workstation has no in-place upgrade path, only a move to a different tool and a different skill set.
  • There is no Linux build and no server edition for running analyses, so JMP cannot sit in a scheduled pipeline the way an R or Python script can, and recurring reports depend on a named person running them on a laptop.
  • The predictive modelling capability most buyers mean when they call this machine learning software is in JMP Pro, a separate and more expensive licence, so the base product's price is not the price of the thing being evaluated.
  • JSL is proprietary to JMP, so the scripts, add-ins and automation a group accumulates over a decade do not port anywhere and become sunk cost the moment anyone questions the renewal.
  • Deployment ends at exported scoring code with no registry, monitoring or retraining, so a model that runs in production is maintained by another team in another language and steadily diverges from the version the analyst still has open.

Pricing, plan by plan

DVC

Free
  • Open SourceFree
    • Data versioning
    • Pipeline management
    • Experiment tracking
  • DVC StudioFree
    • Web UI
    • Team collaboration
    • Visualizations

JMP

Free
  • TrialFree
    • 30-day trial
    • Full features
  • JMP$1785/year
    • Core JMP
    • Standard features

Which should you pick?

Choose DVC if

  • You need pointer-file versioning.
  • You want to start without paying.
  • You work on Linux, Mac, Windows.
  • You also want remote storage backends.

Choose JMP if

  • You need custom design of experiments.
  • You want to start without paying.
  • You work on Mac, Windows.
  • You also want linked interactive graphics.

Questions people ask

Is DVC or JMP better?
Neither clearly leads. DVC starts at Free and JMP at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DVC or JMP?
DVC starts at Free and JMP at Free.
Does DVC or JMP run on more platforms?
DVC runs on Linux, Mac, Windows. JMP runs on Mac, Windows.
Can I use DVC for free?
Both have a free tier, so you can try either at no cost before committing.
What is DVC best used for?
DVC is most often used for making a model reproducible by tying the exact data set version, code commit and parameters together in one git history, keeping large training data out of git while still having a repository that describes it precisely, skipping expensive preprocessing stages that have not changed, when iterating on a later stage of a pipeline, teams that need reproducibility but cannot get approval or budget to stand up a platform for it. Of those, making a model reproducible by tying the exact data set version, code commit and parameters together in one git history and keeping large training data out of git while still having a repository that describes it precisely are not what JMP is typically brought in for.
What can DVC do that JMP cannot?
DVC covers Pointer-file versioning, Remote storage backends, Pipeline definitions, Stage caching. JMP covers Custom design of experiments, Linked interactive graphics, Analysis platforms, Quality and process tools.

Answered from the vendors’ own pages

DVC: Does DVC put my data in Git?

No. Git gets a small pointer file containing a hash. The data goes to a cache on disk and to a remote you configure, such as an S3 bucket.

JMP: Is JMP the same thing as SAS?

No. JMP is a separate desktop product from a SAS subsidiary, with its own interface, its own scripting language and its own licence. Knowing SAS does not transfer to it beyond the statistics.

DVC: Do I need to run a server?

No, and that is most of its appeal. It is a command line tool plus storage you already have. DVC Studio, the hosted web interface, is optional and separately paid.

JMP: Do I need JMP Pro?

If you want cross validation, penalised regression, boosted trees or neural networks, yes. The base edition covers classical statistics, graphics and design of experiments well and stops short of predictive modelling.

DVC: How is it different from Git LFS?

Git LFS versions large files and stops there. DVC also defines pipelines, tracks which stage produced which output, records metrics and lets you compare experiments, and it works with ordinary object storage rather than an LFS server.

JMP: Does it run on Linux?

No. Windows and macOS only, as an installed application.

DVC: Is it free?

The tool is Apache 2.0 and free. You pay for the object storage that holds the data, and optionally for DVC Studio.

JMP: Can I put a JMP model into production?

Only by exporting the scoring formula as SQL, C, Python or similar and running it in another system. JMP itself does not serve, monitor or retrain models.

DVC: Can several people work on the same data set?

Yes, through the shared remote, but only if all of them use DVC for every change. The tool cannot enforce a discipline it does not own, and a single manual copy silently breaks the guarantee.

JMP: Who actually uses it?

Process and quality engineers, and scientists in R&D, particularly in semiconductor, chemicals, pharmaceutical and medical device work. It is not usually chosen by data engineering or platform teams.

Share

Related pages

Other head to heads