Ask HN: Do you understand what a product with this description does for you?
Hi,<p>What follows is a description of a product. I&#x27;d like to get some feedback. Does it confuse you? Do you understand problems it solves? Thank you.<p>Description:<p>$PRODUCT_NAME offers real-time collaborative notebooks to train, track, package, deploy, and monitor your machine learning models. It enables you to work as if you had the help of a team of experts.<p>No-setup notebook:<p>You can just start a fresh notebook server from several Docker images that just work. You don’t need to troubleshoot environments, deal with NVIDIA drivers, or lose hours or days fixing your laptop. For people without strong systems skills, they become autonomous instead of relying on others to fix their system.<p>Real-time collaboration<p>You can share a notebook with other users and collectively edit it, see each others’ cursors and selections. This is ideal for pair-programming, troubleshooting, tutoring, and a must when working remotely.<p>Long-running notebooks that don&#x27;t lose output, executed in the background<p>Regular notebooks lose computation results when there is a disconnection, which often happens in long-running training jobs. You can schedule your notebooks in a fire and forget fashion, right from the notebook interface, without interrupting your flow, and watch their output stream from other devices.<p>AppBooks<p>You can run or have others run your notebooks with different values without changing your code. You can click “Publish” and have a parametrized version without changing cell metadata or adding tags. One use case is having a subject-matter expert tweak some domain specific parameters to train a model without being overwhelmed by the code, or the notebook interface. It becomes a form on top of the notebook with the parameters you want to expose.<p>Bring your own Kubernetes clusters<p>You can use your own existing Kubernetes clusters from Google, Amazon, Microsoft, or DigitalOcean on $PRODUCT_NAME which will use them for your notebook servers, your scheduled notebooks, and different other workloads. You don’t have to worry about metered billing in yet another service. You can control access right from your cloud provider’s console or interface, and grant your own customers or users access to your clusters. We also shut down inactive notebooks that have no computation running automatically, to save on cloud spend.<p>Bring your own S3 buckets<p>You do not need to upload data to $PRODUCT_NAME to start working, you can just add an external S3 bucket and be able to access it as if it were a filesystem. As if your files were on disk. This is ideal not to pollute your code with S3 specific code (boto3, tensorflow_io), and reduces friction. This also ensures people work on the same data, and avoids common errors when working on local copies that were changed by accident.<p>Automatic Experiment Tracking<p>You can’t improve what you cannot measure and track. Model training is an iterative process and involves varying approaches, parameters, hyperparameters, which give models with different metrics. You can’t keep all of this in your head or rely on ad-hoc notes. Your experiments are automatically tracked on $PRODUCT_NAME, everything is saved. This makes collaboration easier as well, because several team members will be able to compare results and choose the best approach.<p>One-click model deployment<p>You can deploy your model by clicking a button, instead of relying on a colleague to do it for you. You get a REST endpoint to invoke your model with requests, which makes it easy for developers to use these models without knowing anything about machine learning. You also get a convenience page to upload a CSV and get predictions, or enter JSON values and get predictions from that model. This is often needed for non-technical users who want a graphical interface on top of the model. The page also contains all the information of how that model was produced, which experiment produced it, so you know which parameters, and which metrics.<p>One-click model packaging<p>You don’t need to worry about sending pickles and weights or using ssh and scp. You can click a button and $PRODUCT_NAME will package your model in a Docker image and push it to a registry. You can then take your model anywhere. If you have a client for which you do on-premises work, you can just docker pull your image there, and start that container and expose that model to other internal systems.<p>Model monitoring<p>For each model you deploy, you get a live dashboard that shows you how it is behaving. How many requests, how many errors, etc. This enables you to become aware as soon as something is wrong and fix it. Right now, we’re adding data logging so you can have access to data distribution or outliers. We’re also adding alerts so you get an alert when something changes above a certain threshold, and are exposing model grading, so you can note your model when it gets something wrong or right, and visualize its decaying performance. Automatic retraining is on the short term roadmap.<p>Integrations with Streamlit, Voilà, and Superset<p>You can create dashboards and applications right from the notebook interface, as opposed to having someone provision a virtual machine on GCP, create the environment, push the code, start a web server, add authentication, remember the IP address for a demo. You can also create Superset dashboards to work on your data.<p>APIs everywhere<p>You can use most of these features with an HTTP request, as opposed to going through the web interface. This is really important for instrumentation and integrations. We’re also adding webhooks soon, so $PRODUCT_NAME can emit and get events to and from other external systems. One application of this is Slack alerts, for example, or automatic retraining based on events you choose.