Weights & Biases Reviews

My main use case for Weights & Biases is tracking metrics for my models when I'm training or testing new models.

I can give a quick specific example of how I use Weights & Biases to track metrics during my model training or testing by setting up the script to send my metrics when I'm training models in my Jupyter Notebook.

In addition to tracking metrics, I also track down errors, precisions, and recalls.

In my opinion, the best features Weights & Biases offers are that they are easy to adapt and navigate through inside their UI, and I can check the model artifacts by versions. Sometimes when it throws errors, I can check them easily, and it has access control that's a good fit for corporate usage.

What I like about the UI and the access control features is that they are just easy to navigate, easy to understand, and finding is also easy.

Weights & Biases has positively impacted my organization a lot because many users are using Weights & Biases for tracking models and seeing metrics. I believe it places a lot less weight on setting up this tracking method.

I can share specific outcomes or metrics since using Weights & Biases. For example, I can check each epoch's model artifacts and see how effectively it worked on my evaluation set, and it can be fetched by the unique ID.

I think Weights & Biases can be improved by being more stable because sometimes we have a lot of network issues and it's hard to debug. Also, there are some minor UI bugs where some graphs in specific formats don't show.

I would add that their documentation is not easy to go through, and when I'm trying to deploy to Kubernetes, their examples are huge and really difficult to understand.

I have been using Weights & Biases for three years.

Weights & Biases is stable.

Since Weights & Biases is running on AWS on our side, I think it's pretty scalable for now, but I want to expand it to Kubernetes.

Their customer support is great because they have 24/7 support and created separate Slack channels for our company users.

I didn't previously use a different solution; I was just using a notebook.

Before choosing Weights & Biases, I wasn't in a position to evaluate other options, but somebody did.

My advice to others looking into using Weights & Biases is to try it out first and also look at the other options, as it's hard to switch when you are used to Weights & Biases's UI. Other than that, I think it's just about trying to understand the real metrics and concept.

I would rate this product a 7 out of 10.

My main use case for Weights & Biases is as a platform to understand machine learning experiments, including tuning model evolutions and managing data. I use it heavily when I need to write ML scripts for my data processing and data analyst responsibilities. It primarily functions as a research tool for tracking and visualizing, serving as a framework to support my data work.

To provide a specific example of how I have used Weights & Biases in my work, I have a script in my current process that involves code I want to write in Python and PyTorch. I install Weights & Biases, log in to the website, and run queries by configuring it. I have used it to create graphs of the accuracy for the process I'm working on, specifically for a customer prediction model that uses Python scripting.

When I used Weights & Biases for my customer prediction model in Python, it helped me not only with the visualization aspect but also in managing datasets and collaborating with my team members during model development and deployment. It compares the model and visualizes the metrics we want to derive from it by running ML scripts, helping us understand the project in a deeper way through image classifications and NLP models, monitoring accuracy and utilization, and managing hyperparameters while sharing experiments and comparing results.

I have used Weights & Biases mainly for predictions, as it generates automated predictions based on the LLMs we create and stores those predictions, providing data with accuracy and creating charts to help us compare the data and run against future experiments.

Weights & Biases offers several best features including tracking, visualization, the registry part, datasets, dataset versioning, and monitoring framework integrations.

Out of tracking, visualization, registry, dataset versioning, and monitoring, I find myself relying on data versioning the most because it stores changes in datasets for reproducibility, and the model registry keeps track of which prediction model is currently deployed, along with real-time monitoring during training. It also provides accuracy scores, functioning as an experimental tracking tool.

These features help in ML engineering, comparing models, and collaborating with the team while maintaining reproducibility throughout the ML lifecycle.

Weights & Biases has positively impacted my organization by improving the processes we build for the client, particularly in prediction projects. It has improved our datasets and metrics, resulting in faster model comparisons. It provides tracking and model management that helps maintain reproducibility throughout the ML lifecycle.

Weights & Biases can be improved in areas such as user experience, user interface, cost, and features.

Regarding needed improvements, I believe the storage cost should be addressed because we want to store larger datasets and more items, so it can be enhanced in that aspect.

I have been using Weights & Biases for a year.

Weights & Biases is a stable platform.

In terms of scalability, it can support individuals and small teams effectively.

Previously, we used MLflow, ClearML, and TensorBoard, but they lacked the experimental tracking and model management features that Weights & Biases offers, so we switched to it for its end-to-end ML platforms and storage capacity. It stands out from others due to its open-source nature and stronger model registry with good deployment support.

In terms of return on investment, it has helped reduce manual efforts, especially in areas such as fraud detection. It provides accuracy and validation by giving us precision metrics, regression models, and more.

I evaluated various options including MLflow, Neptune.ai, and TensorBoard before settling on Weights & Biases.

My advice to others considering Weights & Biases is to leverage its storage registry and track all important metrics while using the model registry and production monitoring accurately. It maintains proper experiment tracking and is very useful for versioning and comparing features to make data-driven model decisions.

Regarding Weights & Biases' AI capabilities, I believe it has solid governance and security measures.

I find that audit logging is stronger than in other tools, but we still need to examine perspectives regarding unauthorized access and similar concerns.

As for accuracy and reliability of outputs from Weights & Biases, it does not directly help with model accuracy but improves model development through experiments and comparisons, making it easier to identify which models deliver the highest accuracy indirectly, as it optimizes the data in a better way.

I have given Weights & Biases an overall rating of 7 out of 10.

My main use case for Weights & Biases is for tracking runs for protein investigation to drug target discovery targets.

As the administrator with Weights & Biases, I think it's an incredible piece of software. We have used it to track an incredible amount of data, and we've been able to refer back to runs that have been critical in investigating new drugs.

It's extremely easy to administer. It has an incredible API for provisioning of users and groups and the various teams. The support has been stellar. They have been extremely responsive and they have been a real joy to work with.

I would say the best feature Weights & Biases offers is ease of use. They have been able to work the use of Weights & Biases for tracking checkpoints easily into their workflows which are varied. They use it from the command line, they use it from dag flows via Argo. It's just been a piece of software that people have depended upon and sometimes take for granted, but it's one of those things that's always there, always available, and easy to use.

The ease of use of Weights & Biases impacts my team's day-to-day work significantly because before they were not doing very much checkpointing at all. We had jobs that would run for days and would crash and then would be unable to return back to an earlier point in the analysis, and with the use of Weights & Biases, that's easy. Any kind of work that has to be done that gets interrupted can go back easily to a previous iteration and begin from that point rather than having to redo the entire job. This saves days and weeks of redoing work.

Weights & Biases has positively impacted my organization in that the support is excellent both for us as administrators and for our teams. They frequently run webinars for people to get better use out of it and expand the features, and that's been helpful.

I don't really know how Weights & Biases can be improved; that would have to come from one of the researchers.

From an administrator's perspective, I think one of the difficulties that we are experiencing is we have a lot of historical data, and I think we don't understand how best to easily take care of that, but I don't know if that's a Weights & Biases problem.

There are no improvements needed for Weights & Biases that I haven't mentioned.

I have been using Weights & Biases for about the last four years.

Weights & Biases is very stable.

Weights & Biases handles increased workloads or more users easily.

The customer support is stellar. We have an open channel with them in Slack that we can ask questions, both researchers and admins. Someone is always available to us there. The migration from self-hosted to cloud was seamless. We had parts that we had to do, and there were parts that they had to do. We had a clear roadmap, we had clear delineation of tasks on who had to do what and on which side, whether it was our side or their side. That was one of the smoothest migrations I've ever had in my software and administrative career.

We started out doing everything by hand and writing things to disk; it was homemade and not a good option. Weights & Biases came along and filled a real need.

Weights & Biases started out with us on-premises, but we are now in public cloud with Amazon for our deployment.

I didn't purchase Weights & Biases through the AWS Marketplace; we have a private contract.

My experience with pricing, setup cost, and licensing was that we received very favorable terms. The licensing was easy. The setup cost and the migration were minimal in comparison to what we got. They helped us migrate from our on-prem to cloud with just a small fee. It was amazing. They did a great deal of work.

I don't think we evaluated other options before choosing Weights & Biases, or if we did, I wasn't here at the company when that was initially made. I think people from other companies had used it and felt like it was a good fit for our organization.

I can't give a quick specific example of how I use Weights & Biases for protein investigations or target discovery because I'm just the administrator for it.

Weights & Biases is an awesome piece of software.

I can't share any specific outcomes or metrics that show how Weights & Biases has helped my organization.

My advice to others looking into using Weights & Biases is to absolutely use it. Figure out in what ways and what options are there in order to be able to take full advantage of it. I think sometimes we don't use all the resources it provides, but certainly, what it does provide as its core business is sufficient for us.

Weights & Biases' governance and security capabilities are very good; we're Okta enabled on it. We don't have any issues, and the infrastructure itself only has a very few set of whitelisted IPs for access, and we're able to do most things through a service account. So it's great.

Weights & Biases' accuracy and reliability of output are very accurate and reliable. We have had no complaints from researchers. It's just part of their everyday day-to-day and they depend on it, so its accuracy and reliability have been sufficient for us enough to move forward and not worry about having to be concerned about reliability or accuracy.

I give this review a rating of eight out of ten.

My main use case for Weights & Biases revolves around experiment tracking and model evaluation.

In my previous job, I used Weights & Biases for experiment tracking, model evaluation, visibility, and collaboration between the different teams that we had at the company, mostly in product and engineering, while we were working on AI-driven workflows and AI features.

Weights & Biases has positively impacted my organization by improving operational efficiency and functional visibility.

After adopting Weights & Biases, I noticed positive outcomes such as reduced time spent on debugging and rerunning experiments, allowing teams to quickly identify what configuration produced the best results.

One of the best features Weights & Biases offers is hyperparameter optimization because it lets us run large-scale hyperparameter searches using random or grid search.

Hyperparameter optimization from Weights & Biases helped my team significantly by reducing the manual trial and error and improving model performance much faster.

For improvement, I would say cost and scalability could be addressed, and visibility could be improved further on AI workflows.

I have used Weights & Biases for around a year in my last job.

Weights & Biases is stable.

Scalability of Weights & Biases has not become a bottleneck in our training workflow.

My experience with customer support for Weights & Biases was good.

Weights & Biases was the first solution I used for experiment tracking and model management, although we were considering Arise AI or BrainTrust at some point.

Before choosing Weights & Biases, I did evaluate other options, including Arise AI and BrainTrust.

Weights & Biases was already in our system and we did not purchase it through AWS Marketplace.

I had a good experience with pricing, setup cost, and licensing, and everything was smooth.

While I cannot share specific metrics due to confidentiality, the return on investment from using Weights & Biases has been really good.

I had a good experience with pricing, setup cost, and licensing, and everything was smooth.

My advice for others looking into using Weights & Biases is that they should use it and experience the benefits of this product. I would rate this review as a 9 out of 10.

I use Weights & Biases primarily for experiment tracking, logging metrics such as loss and accuracy, learning rate, and other parameters. It helps in visualizing training progress in real time, particularly for deeper projects involving dataset modeling, CI/CD pipelines, and similar tasks.

I used Weights & Biases in my personal project involving self-generating adversarial networks, where I tracked generator and discriminator losses over time, logged sample outputs, and compared architectures and hyperparameters. Those losses helped me analyze my model to optimize it so that they became negligible or minimal. Weights & Biases provides real-time dashboards, image logging, experiment comparison, and other useful features.

One thing I appreciate about using Weights & Biases is how it fits into the bigger picture of ML workflows. As a developer, I can integrate end-to-end workflow integrations, which include data pipelines to track, model registry to store and manage, and deployment monitoring, so that I can analyze how models are performing, the losses, and the gains. It also supports hyperparameter tuning and model comparisons, including the comparison of losses and gains. In my opinion, it is a research notebook experiment collaboration tool.

Using Weights & Biases gave me the ability for faster development and also saved my time since analyzing the discriminator and generator losses, which would have taken a lot of time if I did it manually, was done very easily with Weights & Biases. The graphs it provided were also very helpful in analyzing the gains and losses and the accuracy of the generator and discriminator model.

The best features that Weights & Biases offers include experiment tracking to monitor accuracy, loss, and learning rate in real time, visualizing the training process with dashboards. Additionally, it automates testing of hyperparameter configurations for different models through the hyperparameter feature. Weights & Biases has a model registry to version data, models, prompts, and code, ensuring reproducibility by linking experiments. Weights & Biases also has an integration ecosystem that works seamlessly with frameworks like PyTorch and TensorFlow.

Deployment and monitoring stands out as a feature I wish had further improvement. When I used it, it served as a fine-tuned model directly from Weights & Biases, providing automations for CI/CD pipelines and machine learning.

From my perspective, I don't think Weights & Biases needs significant improvement, but areas involving more image tracking and additional integrations with tools like PyTorch or TensorFlow would be beneficial. I would prefer some AI tools to be integrated, such as Vercel or Netlify for deployments, as that would create ease of use for developers.

In terms of Weights & Biases's AI capabilities, I believe improvements can be made regarding governance and security. In the AI world, many organizations struggle with securing their codes effectively, so if Weights & Biases introduced features related to security score levels, it would be helpful in enhancing security and strengthening code in a cohesive manner.

I have been using Weights & Biases since last year.

Weights & Biases is stable.

Before using Weights & Biases, I had only developed in personal projects involving self-generating adversarial networks, where I analyzed the performance of generator and discriminator models along with their gains and losses.

I have seen a return on investment in terms of time saved, with improved accuracy, reduced losses, and increased gains.

I only use the free tier of Weights & Biases, and I do not have any information regarding the prices or setup costs for licensing. The free tier is sufficient for developers who are in college, in my opinion.

I only use Weights & Biases and did not evaluate any other options.

I suggest avoiding making the interview too lengthy, as it is meant for review purposes and should not take up thirty minutes to one hour. My overall review rating for Weights & Biases is eight out of ten.

My main use case for Weights & Biases is data lineage tracking and model registry management, as I use Weights & Biases to keep a complete version history of data sets and models, making it easy to trace every trained model back to the exact data, code, and artifacts used to create it.

Beyond tracking and registry with Weights & Biases, the automated lineage graphs are a huge time-saver for auditability and team collaboration, meaning that if a model ever behaves unexpectedly down the line, anyone on the team can inspect the registry entry and immediately see the exact parameters, data artifacts, and code commit that produced it without having to dig through logs.

The standout feature of Weights & Biases is its Artifacts combined with automated data lineage graphs, which automatically track the exact inputs and outputs for every run, generating a complete directed acyclic graph that maps datasets to models seamlessly. Another top feature is the Model Registry, which gives us an organization-wide centralized hub to manage model lifecycles, assign mutable aliases such as staging or production, and trigger downstream CI/CD pipelines automatically whenever a new model version is promoted.

On the visualization side, Weights & Biases Reports are phenomenal, as you can instantly turn dynamic experiment dashboards into interactive, shareable documents with live plots, text, notes, and code snippets. This completely eliminates the need to take static screenshots for team updates or slide decks, ensuring that anyone on the team can inspect live charts and drill down into the metrics directly.

Weights & Biases has significantly boosted our efficiency and reliability, with the biggest impact being complete reproducibility and traceability, as we no longer waste hours trying to reconstruct how a specific model was trained or which dataset version was used. It has also streamlined our model deployment workflows through the Model Registry, making transitions from training to production much smoother and reducing human error, creating a single source of truth that saves us substantial engineering time and keeps our MLOps processes tight and auditable.

Quantitatively, Weights & Biases has reduced our model audit and debugging time by roughly 50%, as in the past, tracking down the exact dataset commit and hyperparameter set for an older model could easily take half a day, but now it takes under two minutes in the Weights & Biases registry. Qualitatively, it has almost completely eliminated deployment errors caused by model-data mismatch or missing metadata, and having a standardized, automated lineage check before promoting a model to production gives us total confidence and saves us from costly post-deployment headaches.

The main area for improvement in Weights & Biases is cost predictability and pricing scaling, since as logging frequency and artifact storage scale up across larger teams, expenses can climb surprisingly fast. Therefore, more granular cost control toggles or sampling controls directly in the SDK would be a huge help. Additionally, self-hosted or air-gapped enterprise deployments can still be quite complex to configure and maintain compared to their managed SaaS version, so streamlining the Kubernetes Helm installation for private clouds and making self-hosted setups lighter on resources would make a big difference for security-conscious MLOps environments.

On the developer experience side, the Python SDK documentation could benefit from clearer, production-grade examples, as while basic getting-started guides are great, finding detailed code patterns for advanced edge cases such as complex multi-model artifact tracking or custom orchestration setups often requires digging through community forums. Regarding integration, expanding native connectors for certain Kubernetes-native tools and GitOps pipelines would make automated model production feel more seamless out of the box, without needing as many custom webhook scripts.

I have been using Weights & Biases for approximately two years in my current project.

Weights & Biases is highly stable, as it serves as an established, enterprise-grade industry standard for MLOps that reliably handles large-scale production workloads, high-frequency logging, and complex data tracking across large engineering teams.

Weights & Biases' scalability is exceptional, as it seamlessly scales from individual local prototypes to enterprise workloads with millions of logged metrics, large artifact storage, and distributed multi-node GPU training clusters. Its architecture is built to ingest high-frequency logging from parallel training runs without choking, and features such as Artifacts and Model Registry scale effortlessly as data volumes and team sizes grow.

The customer support experience with Weights & Biases has been very reliable, as for routine development and edge cases, their traditional documentation, API references, and active community forums such as Slack and GitHub are thorough and quickly answer most technical questions. When enterprise-level support is needed, such as troubleshooting pipeline integrations or deployment issues, their dedicated support engineers are responsive, technically competent, and work directly with MLOps teams to resolve issues efficiently.

Previously we relied on MLflow along with custom in-house scripts for tracking, but we switched to Weights & Biases because MLflow required significant effort to maintain, customize, and scale on our own infrastructure. Weights & Biases provided a much smoother user experience out of the box, especially around automated data lineage visualization, a more polished Model Registry UI, and seamless interactive reporting, drastically reducing our setup overhead and improving team collaboration.

During our evaluation phase for Weights & Biases, we specifically looked at MLflow, Neptune.AI, and TensorBoard, ultimately selecting Weights & Biases because of its superior automated data lineage tracking, a more refined Model Registry UI, and effortless interactive reporting, which gave us the best combination of feature completeness and low developer overhead.

We use an on-premise deployment of Weights & Biases, which is managed for us by an external third-party vendor, allowing our team to leverage Weights & Biases locally while ensuring strict data privacy and security compliance within our environment.

I'm not directly involved in the purchasing, setup, or licensing of products for Weights & Biases, as this side of things, including vendor negotiations and infrastructure management, is handled entirely by the external company managing our on-prem deployment. My focus is purely on the engineering side and hands-on usage of the platform.

We've seen a solid return on investment with Weights & Biases, mainly in engineering time saved and risk reduction, as quantitatively, it saves our team about 30 to 40% of time on experiment tracking and auditing. Finding past datasets or model versions now takes minutes instead of hours. Qualitatively, having an automated lineage in the registry prevents costly deployment errors from mismatched models, while also making team collaboration and handovers effortless.

From an MLOps perspective, Weights & Biases plays a central role in both AI governance and security, as its features such as Artifacts and the Model Registry provide an immutable audit trail. They automatically track end-to-end data lineage, mapping exact dataset versions, code commits, and hyperparameters directly to deployed models, making model compliance, internal audits, and reproducing past results straightforward. Additionally, Weights & Biases offers role-based access control to restrict access to sensitive datasets or production models across teams, and for enterprise setups, it supports single sign-on, encryption at rest and in transit, SOC 2, ISO 27001 compliance, and flexible deployment options such as private cloud or air-gapped VPC instances to keep proprietary data and model weights secure.

What makes Weights & Biases stand out is its seamless developer experience with Artifacts and the Model Registry, which automatically builds end-to-end data lineage graphs and provides an intuitive, interactive dashboard without adding heavy code overhead. The aspects that keep it from being a perfect 10 are the pricing scaling at high data volumes and the complexity of managing self-hosted or air-gapped enterprise setups on Kubernetes.

In terms of accuracy and reliability, it's important to clarify that Weights & Biases isn't generating model outputs itself; it acts as the system of record and evaluation infrastructure. From an evaluation perspective, its reliability is top-tier. Through toolsets such as Weights & Biases Weave, it provides a structured framework for evaluation and observability, letting you implement custom metrics and LLM-as-a-judge scoring while running standardized benchmarks to measure hallucination rates, factual accuracy, and context relevance deterministically. What makes it so reliable is traceability, as instead of giving you vague scores, every single evaluation metric or trace is tied directly to the exact model version, dataset commit, and prompt template used, eliminating guesswork and ensuring that when you measure model accuracy or failure modes in production, the data you're looking at is 100% reproducible and verifiable.

My biggest advice for others looking into using Weights & Biases is to adopt Artifacts and standard logging conventions right from day one, as you should not treat it as a basic dashboard for plotting loss curves. Truly leverage the Model Registry and dataset lineage capabilities early on, and establish clear naming conventions for your runs, artifacts, and projects across your team, as setting up these MLOps best practices from the start saves a massive amount of cleanup time later, ensuring full reproducibility and smooth collaboration as your projects scale.

I provided this review with an overall rating of 9 out of 10.

My main use case for Weights & Biases is experiment tracking.

Weights & Biases is a very handy library when I want to track experiments and find the optimal parameters for training models or determine which model is the best when experimenting with multiple models. This library is very useful.

When I need to find the optimal hyperparameter, I can use Weights & Biases to track different hyperparameters for training a model. Weights & Biases offers experiment tracking, hyperparameter optimization, and model artifact versioning.

I rely the most on hyperparameter optimization in my daily work because it is very useful for training models.

Weights & Biases is very useful when I need to review the past and see which model performed better or which parameters were the best. It provides good versioning and history, which is a feature I use frequently.

I think it provides easier collaboration. Even if I want to share my model with someone, they can see the metrics that I am getting in that model.

I think there are not enough tutorials or training available for Weights & Biases. That would be much more beneficial. A better integration with cloud providers would also help.

I have been using Weights & Biases for three years.

Weights & Biases is stable in my experience.

Weights & Biases is scalable.

I evaluated MLflow and TensorBoard before choosing Weights & Biases.

I chose a rating of 8 out of 10 for Weights & Biases because it is easy to use and a very good library for machine learning engineers. Weights & Biases is a very useful library if you want to track training experiments.

My main use case for Weights & Biases was for my end-of-studies project with the Ministry of the Economy and Finance.

As part of my end-of-studies project with the Ministry of the Economy and Finance, we used Weights & Biases mainly to track and compare our machine learning experiments in a structured way.

The main goal of our project was to choose the best possible embedding model for the Ministry of the Economy and Finance, and through metric visualization and quick comparison, we were able to decide in a smooth and helpful way which was the best model.

In my opinion, the best features that Weights & Biases offers are the most useful ones, such as experiment tracking, metric visualization via dashboards, and quick comparison between multiple runs.

Weights & Biases had a positive impact on my organization in that it allowed us to centralize our research, specifically centralizing our results, metric tracking, and visualization.

Weights & Biases allowed each person to run their tests and then we could decide directly what decision to make next.

In my opinion, Weights & Biases could be improved by enhancing the tool with artificial intelligence to allow for faster research and a more intuitive experimentation process.

I have been using this solution for a year.

Regarding the pricing, setup cost, and license management of Weights & Biases, we stayed on the free plan, which allowed us to explore this tool and test all the features.

My experience with Weights & Biases was very interesting and very intuitive. I do not have anything else to add about the features I appreciated in Weights & Biases. I do not have any other ideas or details about improvements that could be made to Weights & Biases. I have been able to cover everything, and I do not see any other areas for improvement for Weights & Biases. I would rate this product a 9 overall.