Read the show’s notes in full
PixRay was one of the first models being built on Replicate, and it quickly started taking over the community. Chris Dixon has a famous 2010 post titled “The next big thing will start out looking like a toy”; image generation would have definitely felt like a toy in 2021, but it gave Replicate its initial boost.
2022: Stable Diffusion
In August 2022 Stable Diffusion came out, and all the work they had been doing to build this infrastructure for CLIP / GANs models became the best way for people to share their StableDiffusion fine-tunes:
And like the first week we saw people making animation models out of it. We saw people make game texture models that use circular convolutions to make repeatable textures. We saw a few weeks later, people were fine tuning it so you could put your face in these models and all of these other ways. […] So tons of product builders wanted to build stuff with it. And we were just sitting in there in the middle, as the interface layer between all these people who wanted to build, and all these machine learning experts who were building cool models. And that's really where it took off. Incredible supply, incredible demand, and we were just in the middle.
(Stable Diffusion also spawned Latent Space as a newsletter)
The landing page paved the cowpath for the intense interest in diffusion model APIs.
2023: Llama & other multimodal LLMs
By 2023, Replicate’s growing visibility in the Stable Diffusion indie hacker community came from top AI hackers like Pieter Levels and Danny Postmaa, each making millions off their AI apps:
Meta then released LLaMA 1 and 2 (our coverage of it), greatly pushing forward the SOTA open source model landscape. Demand for text LLMs and other modalities rose, and Replicate broadened its focus accordingly, culminating in a $18m Series A and $40m Series B from a16z (at a $350m valuation).
Building standards for the AI world
Now that the industry is evolving from toys to enterprise use cases, all these companies are working to set standards for their own space. We cover this at ~45 mins in the podcast. Some examples:
* LangChain has been trying to establish "chain” as the standard mental models when putting multiple prompts and models together, and the “LangChain Expression Language” to go with it. (Our episode with Harrison)
* LLamaHub for packaging RAG utilities. (Our episode with Jerry)
* Ollama’s Modelfile to define runtimes for different model architectures. These are usually targeted at local inference.
* Cog (by Replicate) to create environments to which you can easily attach CUDA devices and make it easy to spin up inference on remote servers.
* GGUF as the filetype ggml-based executors.
None of them have really broken out yet, but this is going to become a fiercer competition as the market matures.
Full Video Podcast
As a reminder, all Latent Space pods now come in full video on our YouTube, with bonus content that we cut for time!
Show Notes
* Ben Firshman
* Replicate
* Free $10 credit for Latent Space readers
* Andreas Jansson (Ben’s co-founder)
* Charlie Holtz (Replicate’s Hacker in Residence)
* Fig (now Docker Compose)
* Command Line Interface Guidelines (clig)
* Apple Human Interface Guidelines
* arXiv Vanity
* Open Interpreter
* PixRay
* SF Compute
* Big Sleep by Advadnoun
* VQGAN-CLIP by Rivers Have Wings
Timestamps
* [00:00:00] Introductions
* [00:01:17] Low latency is all you need
* [00:04:08] Evolution of CLIs
* [00:05:59] How building ArxivVanity led to Replicate
* [00:11:37] Making ML research replicable with containers
* [00:17:22] Doing YC in 2020 and pivoting to tools for COVID
* [00:20:22] Launching the first version of Replicate
* [00:25:51] Embracing the generative image community
* [00:28:04] Getting reverse engineered into an API product
* [00:31:25] Growing to 2 million users
* [00:34:29] Indie vs Enterprise customers
* [00:37:09] How Unsplash uses Replicate
* [00:38:29] Learnings from Docker that went into Cog
* [00:45:25] Creating AI standards
* [00:50:05] Replicate's compute availability
* [00:53:55] Fixing GPU waste
* [01:00:39] What's open source AI?
* [01:04:46] Building for AI engineers
* [01:06:41] Hiring at Replicate
This summary covers the full range of topics discussed throughout the episode, providing a comprehensive overview of the content and insights shared.
Transcript
Alessio [00:00:00]: Hey everyone, welcome to the Latent Space podcast. This is Alessio, partner and CTO in Residence at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol AI.
Swyx [00:00:14]: Hey, and today we have Ben Firshman in the studio. Welcome Ben.
Ben [00:00:18]: Hey, good to be here.
Swyx [00:00:19]: Ben, you're a co-founder and CEO of Replicate. Before that, you were most notably founder of Fig, which became Docker Compose. You also did a couple of other things before that, but that's what a lot of people know you for. What should people know about you that, you know, outside of your, your sort of LinkedIn profile?
Ben [00:00:35]: Yeah. Good question. I think I'm a builder and tinkerer, like in a very broad sense. And I love using my hands to make things. So like I work on, you know, things may be a bit closer to tech, like electronics. I also like build things out of wood and I like fix cars and I fix my bike and build bicycles and all this kind of stuff. And there's so much, I think I've learned from transferable skills, from just like working in the real world to building things, building things in software. And you know, it's so much about being a builder, both in real life and, and in software that crosses over.
Swyx [00:01:11]: Is there a real world analogy that you use often when you're thinking about like a code architecture or problem?
Ben [00:01:17]: I like to build software tools as if they were something real. So I wrote this thing called the command line interface guidelines, which was a bit like sort of the Mac human interface guidelines, but for command line interfaces, I did it with the guy I created Docker Compose with and a few other people. And I think something in there, I think I described that your command line interface should feel like a big iron machine where you pull a lever and it goes clunk and like things should respond within like 50 milliseconds as if it was like a real life thing. And like another analogy here is like in the real life, you know, when you press a button on an electronic device and it's like a soft switch and you press it and nothing happens and there's no physical feedback of anything happening, then like half a second later, something happens. Like that's how a lot of software feels, but instead like software should feel more like something that's real where you touch, you pull a physical lever and the physical lever moves, you know, and I've taken that lesson of kind of human interface to, to software a ton. You know, it's all about kind of