Paul Yang

Despite the hype around LLMs, we contend that even very large and sophisticated LLMs cannot replace ML training done over your first-party data. 

Will LLMs Replace ML Training (No, here's why)

Donny Greenberg

Machine learning development is stuck in slow, fragmented cycles, far removed from the fast-paced, iterative nature of traditional software development. This blog will explore how we got here, define the essential requirements for a modern ML platform, and conclude by introducing Runhouse as a solution that was built to accelerate ML development.

AI Platforms: Past, Present, and Future

In this Lean Orchestration Manifesto, we advocate for a more streamlined approach to ML pipelines by narrowing the scope of orchestrators. Orchestrators should be used to schedule, log, and retry tasks, but should not be the primary runtime of your production ML pipelines.

The Lean Orchestration Manifesto: Narrowing Orchestrator Scope Creates Better ML Development 

Matt Kandler

An overview of Meta Llama 3 and detailed guide on how to run the LLM on your own cloud compute or locally with simple Python.

How to Use Llama 3 Self-Hosted

Elijah ben Izzy

Plus: A nimble, composable example with Github Actions, Hamilton, and Runhouse

Lean Data Automation: A Principal Components Approach

Parallelizing work across cloud compute is clunky and manual. It doesn't have to be.

Scaling Batch Processing on Cloud Compute with Runhouse and SkyPilot

What if we made building and deploying FastAPI apps even faster? 🤯

“LudicrouslyFastAPI:” Deploy Python Functions as APIs on your own Infrastructure

Lean, ergonomic, multi-cluster dispatch for high-velocity AI teams

Better GPU Cluster Scheduling with Runhouse

Caroline Chen

Josh Lewittes

You deserve better than pasting API keys into environment variables

Simple, Secure Secrets Management for AI

Deploy and Run Your Code on SageMaker in 10 Minutes with Runhouse

The Quickest AWS SageMaker Deployment in Existence

Denis K

Get started with multimodal conversational models using the open-source LLaVA-1.5 model, Hugging Face Transformers, and Runhouse.

Create a Visual Chatbot on AWS EC2 with LLaVA-1.5

Machine Learning's hellish developer experience and research-to-production drag are largely due to widespread over-packaging - coupling systems rigidly together through misuse of containers and pipelines. There's finally an end in sight.

Please separate orchestration and execution (Or: Packaging hell is dragging ML)

Buckle up, this is less a release blog post and more a wild ride through the Infra API Wonka Factory. We’ll talk through the innocent motivations which turned into upending half of Runhouse’s core execution model, and the gaggle of awesome new features which fell out.

Runhouse 0.0.12: rh.Module, Streaming, and too much more

Platform overhead occupies 50-75% of ML engineers’ and researchers’ time. Runhouse is a PyTorch-like unified interface to solve that.

A PyTorch Approach to ML Infrastructure

Part 1 of a series on data pipelines for the modern ML stack

Supercharging Apache Airflow with Runhouse

Reproducible, cloud-agnostic GPU setup and remote code deployment using Runhouse, a walkthrough of Hugging Face’s Keras Dreambooth Event

Runhouse Blog