We Raised $8M Series A to Continue Building Experiment Tracking and Model Registry That “Just Works”

Read more

Neptune vs DVC

neptune ai blue horizontal 1
vs
dvc logo
Commercial Requirements
Standalone component or a part of a broader ML platform?

Standalone component. ML metadata store that focuses on experiment tracking and model registry

Standalone component

Is the product delivered as commercial software, open-source software, or a managed cloud service?

Managed cloud service

Open-source and managed cloud service

SSO, ACL: does the vendor provide user access management?
General Capabilities
What are the infrastructure requirements?

No special requirements other than having the neptune-client installed and access to the internet if using managed hosting. Check here for infrastructure requirements for on-prem deployment

DVC studio requires DVC initalized github/gitlab/bitbucket repo created and access to the internet if using managed hosting. Contact them here for more information for infrastructure requirements for on-prem deployment

How much do you have to change in your training process?

Minimal. Just a few lines of code needed for traking. Read more

Minimal. Just a few lines of code needed for tracking. Read more

Does it integrate with the training process via CLI/YAML/Client library?

Yes, through the neptune-client library

Yes, via .dvc and .json files

Does it come with a web UI or is it console-based?

Both Web UI and console-base

Serverless UI

No

No

Customizable metadata structure

Yes

Yes

How can you access model metadata?

– gRPC API

No

No

– CLI / custom API

Yes

CLI

– REST API

No

No

– Python SDK

Yes

Yes

– R SDK

Yes

No

– Java SDK

No

No

– Julia SDK

No

No

Supported operations

– Search

Yes

Yes

– Update

Yes

Yes

– Delete

Yes

Yes

– Download

Yes

Yes

Distributed training support

Yes

Yes

Pipelining support

Yes

Yes

Logging modes

– Offline

Yes

Yes

– Debug

Yes

No

– Asynchronous

Yes

No

– Synchronous

Yes

Yes

Live monitoring

Yes

No

Mobile support

No

No

Webhooks and notifications

No

Yes

Experiment Tracking
Dataset
– location (path/s3)

Yes

Yes

– hash (md5)

Yes

Yes

– Preview table

Yes

No

– Preview image

No

– Preview text

Yes

No

– Preview rich media

No

– Multifile support

Yes

Yes

– Dataset slicing support

No

No

Code versions

– Git

Yes

Yes

– Source

Yes

Yes

– Notebooks

Yes

Yes

Parameters

Yes

Yes

Metrics and losses

– Single values

Yes

Yes

– Series values

Yes

Yes

– Series aggregates (min/max/avg/var/last)

Yes

No

Tags

Yes

Yes

Descriptions/comments

Yes

Yes

Rich format

– Images (support for labels and descriptions)

Yes

No

– Plots

Yes

Yes

– Interactive visualizations (widgets and plugins)

Yes

No

– Video

Yes

No

– Audio

Yes

No

– Neural Network Histograms

No

No

– Prediction visualization (tabular)

No

No

– Prediction visualization (image)

No

No

Hardware consumption

– CPU

Yes

No

– GPU

Yes

No

– TPU

No

No

– Memory

Yes

No

System information

– Console logs (Stderr, Stdout)

Yes

No

– Error stack trace

Yes

No

– Execution command

No

No

– System details (host, user, hardware specs)

Yes

No

Environment config

Files

– External file reference (s3 buckets)

No

Yes

Table format diff

Yes

Yes

Overlayed learning curves

Yes

Yes

Parameters and metrics

– Groupby on experiment values (parameters)

Yes

No

– Parallel coordinates plots

Yes

No

– Parameter Importance plot

No

No

– Slice plot

No

No

– EDF plot

No

No

Rich format (side by side)

– Image

Yes

No

– Video

No

No

– Audio

No

No

– Plots

No

No

– Interactive visualization (HTML)

No

No

– Text

Yes

No

– Neural Network Histograms

No

No

– Prediction visualization (tabular)

Yes

Yes

– Prediction visualization (image, video, audio)

No

No

Code

– Git

No

Yes

– Source files

No

Yes

– Notebooks

Yes

Yes

Environment

– pip requirements.txt

No

Yes

– conda env.yml

No

Yes

– Docker Dockerfile

No

Yes

Hardware

– CPU

Yes

No

– GPU

Yes

No

– Memory

Yes

No

System information

– Console logs (Stderr, Stdout)

Yes

No

– Error stack trace

Yes

No

– Execution command

No

No

– System details (host, owner)

Yes

Yes

Data versions

– Location

Yes

Yes

– Hash

Yes

Yes

– Dataset diff

No

Yes

– External reference version diff (s3)

No

Yes

Files

– Models

No

No

– CSV

No

No

Custom compare dashboards

– Combining multiple metadata types (image, learning curve, hardware)

Yes

No

– Logging custom comparisons from notebooks/code

Yes

No

– Compare/diff of multiple (3+) experiments/runs

Yes

Yes

Experiment table customization

– Adding/removing columns

Yes

Yes

– Renaming columns in the UI

Yes

No

– Adding colors to columns

Yes

No

– Displaying aggregate (min/max/avg/var/last) for series like training metrics in a table

Yes

No

– Automagical column suggestion

Yes

No

Experiment filtering and searching

– Searching on multiple criteria

Yes

– Query language vs fixed selectors

Query language

Fixed selectors

– Saving filters and search history

Yes

No

Custom dashboards for a single experiment

– Can combine different metadata types in one view

Yes

No

– Saving experiment table views

Yes

No

– Logging project-level metadata

Yes

No

– Custom widgets and plugins

No

No

Tagging and searching on tags

Yes

Yes

Nested metadata structure support in the UI

Yes

No

One-command experiment re-run

No

Yes

Experiment lineage

– List of datasets used downstream

No

No

– List of other artifacts (models) used downstream

No

No

– Downstream artifact dependency graph

No

No

Reproducibility protocol

Limited

Yes

Is environment versioned and reproducible

Yes

Yes

Saving/fetching/caching datasets for experiments

No

Yes

Sharing UI links with project members

Yes

Yes

Sharing UI links with external people

Yes

Yes

Commenting

Yes

No

Interactive project-level reports

No

No

Model Registry
Code versions (used for training)

Yes

Yes

Environment versions

No

No

Parameters

Yes

Yes

Dataset versions

Yes

Yes

Results (metrics, visualizations)

Yes

Yes

Explanations (SHAP, DALEX)

No

Model files (packaged models, model weights, pointers to artifact storage)

No

Yes

Models/experiments created downstream

No

Yes

History of evaluation/testing runs

No

Yes

Support for continuous testing

No

Yes

Users who created a model or downstream experiments

No

Yes

Main stage transition tags (develop, stage, production)

No

No

Custom stage tags

No

No

Locking model version and downstream runs, experiments, and artifacts

No

No

Adding annotations/comments and approvals from the UI

No

No

Model compare (current vs challenger etc)

No

No

Compatibility audit (input/output schema)

No

No

Compliance audit (datasets used, creation process approvals, results/explanations approvals)

No

No

Webhooks

No

Yes

Model accessibility

No

Yes

Support for continuous testing

No

Yes

Integrations with CI/CD tools

No

Yes

Registered models

No

No

Active models

No

No

By metadata/artifacts used to create it

No

No

By date

No

No

By user/owner

No

No

By production stage

No

No

Search query language

No

No

Native packaging system

No

No

Compatibility with packaging protocols (ONNX, etc)

No

Yes

One model one file or flexible structure

No

No

Integrations with packaging frameworks

No

No

Integrations and Support
Java

No

Yes

Julia

No

Yes

Python

Yes

Yes

REST API

No

No

Catalyst

Yes

Yes

CatBoost

No

Yes

fastai

Yes

Yes

FBProphet

No

Yes

Gluon

No

Yes

HuggingFace

Yes

Yes

H2O

No

Yes

lightGBM

Yes

Yes

Paddle

No

Yes

PyTorch

Yes

Yes

PyTorch Ignite

Yes

PyTorch Lightning

Yes

Yes

Scikit Learn

Yes

Yes

Skorch

Yes

Spacy

No

Yes

Spark MLlib

No

Yes

Statsmodel

No

Yes

TesorFlow / Keras

Yes

Yes

XGBoost

Yes

Yes

Hyperopt

No

Yes

Keras Tuner

Yes

Optuna

Yes

Yes

Ray Tune

No

Yes

Scikit-Optimize

Yes

DALEX

Yes

Netron

No

Yes

SHAP

No

No

TensorBoard

No

JupyterLab and Jupyter Notebook

Yes

Yes

Google Colab

Yes

Yes

Deepnote

Yes

Yes

AWS SageMaker

Yes

Yes

Airflow

No

No

Argo

No

No

Kedro

Yes

No

Kubeflow

No

No

MLflow

No

Sacred

Yes

No

TensorBoard

No

GitHub Actions

Yes

Gitlab CI

No

Yes

CircleCI

No

No

Travis

No

No

Jenkins

No

No

Seldon

No

No

Cortex

No

No

Databricks

No

No

Seldon

No

No

Fiddler.ai

No

No

Arthur.ai

No

No

This page was updated on 18 August 2021. Some information may be outdated.
Report outdated information here.

What are the key advantages of Neptune, then?

  • Stable and scalable API
  • Hardware consumption monitoring
  • More connection modes available (offline and synchronus, but also asynchronous, read-only, and debug)
Explore features
Use computational resources

See these features in action

1. Create a free account
Sign up
2. Install Neptune client library
pip install neptune-client
3. Add logging to your script
import neptune.new as neptune

run = neptune.init('Me/MyProject')
run['params'] = {'lr':0.1, 'dropout':0.4}
run['test_accuracy'] = 0.84
4. Or see how it works in a notebook (no registration)
Try live notebook

Already using DVC?

You can display DVC files in the Neptune UI and have all metadata in one place.

You just need to specify which DVC files you would like to log:

# Snapshot all .dvc files from any directory
run = neptune.init(...,
                   source_files=["**/*.dvc"])
Learn more
Dataset metadata Neptune

Thousands of ML people already chose their tool

(…) thanks for the great tool, has been really useful for keeping track of the experiments for my Master’s thesis. Way better than the other tools I’ve tried (comet / wandb).

I guess the main reason I prefer neptune is the interface, it is the cleanest and most intuitive in my opinion, the table in the center view just makes a great deal of sense. I like that it’s possible to set up and save the different view configurations as well. Also, the comparison is not as clunky as for instance with wandb. Another plus is the integration with ignite, as that’s what I’m using as the high-level framework for model training.”

Klaus-Michael Lux
Data Science and AI student, Kranenburg, Germany

“Previously used tensorboard and azureml but Neptune is hugely better. In particular, getting started is really easy; documentation is excellent, and the layout of charts and parameters is much clearer.”

Simon Mackenzie
AI Engineer and Data Scientist
This thing is so much better than Tensorboard, love you guys for creating it!
Dániel Lévai
Junior Researcher at Rényi Alfréd Institute of Mathematics in Budapest, Hungary

While logging experiments is great, what sets Neptune apart for us at the lab is the ease of sharing those logs. The ability to just send a Neptune link in slack and letting my coworkers see the results for themselves is awesome. Previously, we used Tensorboard + locally saved CSVs and would have to send screenshots and CSV files back and forth which would easily get lost. So I’d say Neptune’s ability to facilitate collaboration is the biggest plus.”

Greg Rolwes
Computer Science Undergraduate at Saint Louis University
Such a fast setup! Love it:)
Kobi Felton
PhD student in Music Information Processing at Télécom Paris

For me the most important thing about Neptune is its flexibility. Even if I’m training with Keras or Tensorflow on my local laptop, and my colleagues are using fast.ai on a virtual machine, we can share our results in a common environment.

Víctor Peinado
Senior NLP/ML Engineer
Load more

It only takes 5 minutes to integrate Neptune with your code.

Don’t overthink it.

Sign up now