You've built your FastAPI app. It's running great locally. Now you want to share it with the world. But then reality hits. Containers, load balancers, HTTPS certificates, cloud consoles with 200 options. What if deploying was just one command? That's exactly what Sebastian Ramirez and the
FastAPI cloud team are building. On this episode, we sit down with Sebastian, Patrick Arminio, Savannah Ostrowski, and Jonathan Ewald to go inside FastAPI cloud, explore what it means to build a Pythonic cloud and dig into how this commercial venture is actually making FastAPI, the open source project, stronger than ever. This is Talk Python To Me, episode 536, recorded January 13th, 2026. Talk Python To Me, yeah, we ready to roll. Upgrading the code, no fear of getting old.
Async in the air, new frameworks in sight, geeky rap on deck. Quark crew, it's time to unite. We Welcome to Talk Python To Me, the number one Python podcast for developers and data scientists. This is your host, Michael Kennedy. I'm a PSF fellow who's been coding for over 25 years. Let's connect on social media. You'll find me and Talk Python on Mastodon, BlueSky, and X. The social links are all in your show notes. You can find over 10 years of past episodes at
Talk Python.fm. And if you want to be part of the show, you can join our recording live streams. That's right, we live stream the raw uncut version of each episode on YouTube. Just visit talkpython.fm/youtube to see the schedule of upcoming events. Be sure to subscribe there and press the bell so you'll get notified anytime we're recording. This episode is brought to you by CommandBook, a native macOS app that I built that gives long-running terminal commands a permanent home.
No more juggling six terminal tabs every morning. Carefully craft a command once, run it forever with auto-restart, URL detection, and a full CLI. Download it for free at talkpython.fm/command book app. And it's brought to you by the Talk Python in Production Book, an inside look at 10 years of the real-world DevOps behind the Talk Python sites and apps. Check it out at talkpython.fm/DevOps book. Before we dive in, I have something excellent to announce.
A few episodes back, I told you about our new AI integrations, the Talk Python MCP servers, and our llms.txt file, so that AI tools can tap into our over 550 episodes and 7.5 million words of info around the Python community and history. Well, I'm building on that now. Talk Python now has an open source CLI tool. You can search episodes, transcripts, guests, and even our courses right from your terminal. No browser required.
It's fast too, backed by our optimized APIs, taking about five milliseconds of response time, plus, you know, whatever the internet ping time is. It supports rich text for humans, JSON for programs, and markdown output for AIs. You just install it with uvtoolinstall talk-python-cli, and check it out on GitHub. The link is in the podcast player show notes. I also wrote up a blog post on the hows and whys of it. Check that out over on the Talk Python blog at, well, talkpython.fm/blog.
The full link to the exact article is in the show notes. All right, let's jump in. Hello, everyone. Sebastian, Patrick, Savannah, and Jonathan. Awesome to have you all here. Excited to talk about FastAPI Cloud. Welcome. Yes.
Thanks for having me. Thank you. We're also ahead, Mike. What a project.
It's been going on for a while. I've heard stuff from Sebastian that maybe something was brewing and all these things, but not too long ago, you all announced it. And I heard that FastAPI, some people have been using it recently. Some of the surveys show that some people use it for websites. I'm not sure.
Rumors.
Yeah, yeah. Rumors. Rumors. Oh, my gosh. I mean, congratulations on that. But before we dive into FastAPI and FastAPI Cloud, let's just do a quick introduction. Who are you? We'll just go around the Brady Bunch squares of our live stream here and start with Sebastian. You've been on the show a few times. In fact, you've been on the show just recently for a really fun episode, Sebastian.
Who are you? In real, that was super fun. So, hello, everyone. I'm Sebastian Ramirez, or Tiangulo. I created FastAPI. That is this Python framework for building web APIs and backend.
In case you've been living in a hole and haven't done any Python for 10 years. You also are famous for really pointing out the ridiculousness of modern tech recruiting. You know what I'm talking about?
Yeah, you know, like it's fun. This is probably the thing that I am known for. It's for writing a tweet saying, yeah, what was it? that I saw a job asking for five years of experience in FastAPI, and I only had 2.5 since I created the thing. So you didn't qualify for the FastAPI job? I didn't qualify for that, yeah.
And then the funny thing is, you know, like people sometimes, even people in Python itself, and tell me like, oh, wait, like you're, and I say like, oh, yeah, I created this thing called FastAPI. Oh, wait, okay, so what is FastAPI? Oh, wait, you are the guy from the meme, the meme about FastAPI. Are you serious? Yeah, you know, like suddenly that is super important that I am the guy for the meme about FastAPI. Not the guy from FastAPI, the guy from the meme.
Oh my gosh, I saw you on TikTok. It was amazing.
It was a live achievement. I wrote a viral tweet. So yeah, nice to meet you all.
You know what? Sometimes your moment in the sun is not the one you expected. No, congratulations on how good FastAPI is. On the tweet. Exactly. You really nailed it. Patrick, welcome to the show.
Nice to be here. Yeah, I'm Patrick. I guess the main thing I'm kind of known for in the community is like this library called Storary, which is similar to FastAPI, but instead of REST is for GraphQL. Other than that, I help organize PyCon Italy and I used to also do EuroPython as well, but I stopped because of way too many things. Yeah, that's pretty much me. How do you see GraphQL these days? Is it still popular? I think it's mostly popular in the enterprises, unfortunately.
I'm a bit, to be honest, I'm a bit annoyed about the companies that do tooling around GraphQL because I don't know, I feel like they're not really pushing it forward. They're just, I don't know, trying to work with enterprises and that's it. Or maybe people think to AI.
Yeah. It feels a little bit like the soap, soap, wisdom, XML, modern version. Savannah. Yeah.
You like tapping out of being an organizer for EuroPython is like, you know, the classic open source oversubscribed doing all the things very relatable.
Yeah.
Yeah. But yeah, I'm Savannah. What can I say? I am on the Python Steering Council for 2096, which is very exciting.
Congratulations.
Oh, thank you. I am also the release manager for the upcoming version of Python, Python 3.16. And so that'll kick off later this year, which is really cool and very exciting. I work on CPython stuff, the JIT, arg parse, basically whatever needs help. It's kind of where you'll find me.
Awesome. Congratulations on the Steering Council. And yeah, that's a lot of cool stuff. Hopefully we don't get a Python 4.0 right after 3.16 because then your job will never end, is what I've learned.
Yeah, yeah. Benjamin Peterson, Python 2.7 forever kind of situation. Yeah, yeah. I mean, release management is still, I mean, it's still quite a commitment. It's like seven-ish years when you think about all the staggered releases because you're a release manager 2.0 and then you have the five-year maintenance cycle. So yeah, it's Python forever is what I only said.
Yeah, it's probably not a fad. It's probably going to stick around, this Python thing. No, that's awesome. Congratulations. Also, cool with arg parse. I feel like that's making a strong comeback now that we have these AI things that can just put stuff together for us instead of like, oh, I need to depend on this library and that library. Like, I just need to take a few arguments and have a little help text. And it's like, well, you've already got this built-in thing. Oh, who knew?
You know, people are like, oh, I didn't even know. I thought I used typer or click or something, right?
There's, you know, the typers and clicks of the world. But sometimes you just want the simplest thing. And ArgParse is pretty great at that. Although it has many quirks that are probably and most definitely unfixable at this point. Because bugs are features when you have things that have been around as long as Python. But yeah, no, I mean, AI loves to write Python. I think it's like the language used the most, AI-generated code.
I'll just say we live in weird times, very weird times.
I would love a precedented time at some time.
Exactly. Yeah. Can we just get the boring times? No, nothing interesting, please. What I said about GraphQL may sound like a bit of a smash, but I didn't mean it in a negative, super negative way anyway. Like it used to be all the enterprises were all about soap and wisdom and like subscribing your tooling. Please don't write me. I'm not trying to bash on your technology. All right. Jonathan, also welcome. Hi.
Yeah, I'm not nearly as famous as everyone else in this call. I'm more infamous internally at FastAPI Cloud, I would say, for a bunch of things.
I've heard of emojis or something along the lines of line.
One Mima way. You're just one Mima way. Just one Mima way. Yeah, that's true. We keep piling them up internally. But yeah, I used to work with Patrick together for years, also on Craftia. Same library as him. That's how I know him. And that's why I, well, made a weird sound when you said soap. I've been with FastAPI Cloud since EuroPattern, actually, the last one.
I promised Sebastian I would implement server-send events in FastAPI, and I haven't started with it yet at all, but somehow I'm still here. So that's great.
Well, actually, yeah, and it was actually like a sneak peek, I guess. We already started having a bunch of chats and discussing what we do. Should we do it here? Should we do it there? What should we do? So like, yeah, it's something that is coming to FastAPI probably soon-ish. Like there was a lot of things that needed to happen before that. Like Patrick is slightly smiley, like, oh no, this is pressure.
There were some things that needed to happen in FastAPI, as you know, dropping support for Pydantic version one or things like that, that just made the internal code so complex. And now that it's over, we can actually work more on improving performance, adding features and things like that.
I definitely want to dive into how FastAPI Cloud has sort of influenced the whole FastAPI side of things. But I made aware that there is, in fact, an entire website, an entire website dedicated to the meme. Yeah. And out in the audience, we get, hey, everyone, is that the guy from the meme? And meme is greater than Nobel Prize. So, you know what? It may be true. It may be true.
I recognize the person saying, this is the guy from the Ming.
He might be my husband.
Incredible. Incredible. All right, well, let's start with FastAPI Cloud, and then we'll bring it back around to the FastAPI. Let's talk origin story. So what is this FastAPI Cloud? Nice.
So if you were looking at the FastAPI Labs website, that doesn't really show that much. If you click on the join the waiting list that takes you to the website for FastAPI Cloud, there we can see this is what we are building. This is the thing that we are doing. It's actually super simple. The funny thing is that the pitch, the explanation of the product is so short. So it's one command. It's FastAPI Deploy. You have a FastAPI app, you just hit FastAPI Deploy, and then it's on the cloud.
We take care of everything. We build a thing, deploy it, handle HTTPS, auto-scaling, all this stuff. and then you can just like focus on building the application, building apps. The funny thing is that it's super short to explain, but then building it is so cold, Blake.
I'm glad it's so short. So thanks for being here. That was a great show, y'all. Well, no, just kidding. I think it's a little bit like Jupyter Notebooks in that sense that like you all are taking one for the team so that other people can have a simple experience. Whereas, you know, it's like those Jupyter folks, they write tons of TypeScript and do all sorts of things that nobody wants to necessarily do in the data science space so that you can just drag your widgets around.
You know what I mean?
I think that is a great analogy.
I feel like the deployment space, it's a bit of a mixed bag. And I've been really frustrated to the point such that I wrote a book about it, that I think about an alternative, that I think over the last five plus years, it's just trended towards a little more complex, a little more complex. could we just add one of these things? And oh, now we got these three. We need one more thing to like make sure those things are doing, you know what I mean?
And it's just like, wow, why are there 200 choices in my console to use this?
Which is like kind of funny, right? Because I feel like a lot of these companies started with this, like, I don't want to understand all the ins and outs of all the infrastructure that comes with the cloud service provider. And that's really complicated to understand because I'm an app dev and I don't know anything about, you know, whatever, right? Now we're like, I don't know, kind of slowly accumulating.
complexity but i think one of the cool things about what we're building and i like i've worked on cloud tooling before is like this is like just spoke for python developers and i think that's like quite like unique in that like we are really trying to like bring the bleeding edge and like all the new tooling that people are using and making sure that we play well with like uv and like i think like the there's a lot of thought and care put into that by the team that's a super good
point. I mean, I remember Azure came out with like, here's your platform as a service. You just upload your web app and we'll just take it and go. And now that thing is so complicated along with many, many others, right? It's not just them. It's you've got AWS, you've got Vercel. There's lots of things we could point at for, wow, there's a lot of options here, you know?
And then there are a lot of tools and like, you know, like many tools and many companies are also like doing a great job at many of the things that they are doing. But in many cases, it's just so complex, it's so complicated. You know, like I was, I have always been so, what, so adamant, I think is the word, to just teaching people how to use the tools. I think I have the most documentation about how to deploy things on your own than any other framework. I have so much information.
MARK MANDEL: I hear that all the time from people. They say one of the reasons they chose FastAPIs is because how clear the documentation was, you know?
FRANCESC CAMPOY: And then the thing is, you know, like just learning all those concepts and learning all the stuff that needs to be learned just to deploy something, and then you barely have the minimum. It's like, this is just too much. It's too much complacency. I think for me, I guess personally, my analogy is that FastAPI Cloud is the equivalent of what FastAPI is to building web APIs and backend. You could do the same with any other framework. You could validate data.
You could generate open API. You could have automatic docs, But you will probably have to do a lot of the wiring yourself and making sure that it's actually correct and that it doesn't explode, all that stuff. That is, you know, like we are trying to do a lot of that work for the final users.
Yeah, and I think it's great. I think it's really nice to just provide this on-ramp because, as you said at the opening, when I asked, you know, what the origin story is just FastAPI deploy. That solves so many stories. But I'm sure behind the scenes, what happens is just about as simple as that. Oh my gosh.
About that. Some of us don't even get to write Python anymore to make all of this happen. So speaking about taking one for the team.
Yeah, that is taking one for a team, right? It is. This portion of Talk Python To Me is brought to you by us. I'm thrilled to announce a brand new app built for developers created by yours truly. It's called Command Book. You know that thing you do every morning? Open up six terminal tabs, CD into this directory, activate that virtual environment, run the server with --reload. Now, CD somewhere else, start the background worker, another tab for Docker, another one to tail production logs.
Every tab just says Python, Python, Python, Docker tail. And you're clicking through them going, which Python was that again? Where my app is running? Then sometime later, your dev server silently dies because it tried to reload while you're in the middle of a code edit, unmatched brace, a half-written import, or something. Now you're hunting through tabs to figure out which process crashed and how to restart it. My app, CommandBook, gives all of these long-running commands a permanent home.
You save a command once, the working directory, the environment, three commands like git pull, and from then on, you just click run. You can even group commands together to start and stop everything for a project with a single click. It also has what I call honey badger mode, auto restart on crash. so when your dev server goes down mid-reload, Command Book just brings it right back up and does so over and over until the code is fixed.
It also detects URLs from your output so you're never scrolling through thousands of lines of logs just to figure out how to reopen your web app. And it shows you uptime, memory usage, and all sorts of cool things about your process. The whole thing is a native macOS app. No Electron, no Chromium, just 21 megs. And it comes with a full CLI so anything you've configured in the UI, you can fire off from your terminal with just a single command.
Right now, it's macOS only, but if there's enough interest, I'll build a Windows version too, so let me know. Please check it out at talkpython.fm/commandbook app. Download it for free, level up your developer workflow. The link is in your podcast player's show notes. That's talkpython.fm/commandbook. I really hope you enjoy this new app that I built. Let's save the internals for a little bit later.
Maybe what we could do right now, Maybe we could do a bit of a walkthrough of just kind of what it's like to set up an app from scratch, right? Nice. I see that uv is here, which is, I've been certainly an advocate for uv in all sorts of deployment, but especially when you have like repeated build type of scenarios for like Docker, Docker Compose or Kubernetes or whatever, uv makes that stuff so much faster and so on.
So who would like to be my guide that just kind of talks us through what it means to set up a new project here?
I mean, there is like this really nice command that Savannah built, just FastAPI new, which I think is something like, I don't know, like super helpful.
What does FastAPI new do? Like, is that kind of a cookie cutter-esque experience or what is it?
Yes, exactly. At the moment, Onesco holds a super basic FastAPI application using uv. It also installs dependencies, creates a folder, everything that you need. In future, I think we're going to plan support for templates so you can build multiple kind of things as well. But for now, it's just basically just uv FastAPI new, sorry, uvx FastAPI new, and then that scaffolds the project for you. I don't know if you want to try it live or...
No, go ahead. Just, I would think it might disrupt you. Just let's talk us through it.
It could work. I'm just going to put that out there.
I'll tell you the most insane, like let's do that live on the podcast experience. I'm pretty sure, yeah, this is definitely the most insane. I had Matthew Rocklin on from Coiled, and those guys are all about like, hey, we're going to scale up like a bunch of available servers for you, right? So that you can do your data science. Like I want to do some ML thing, and it needs 500 servers. So during the podcast, he's, oh, let me just spin up 2,000 EC2 instances. Hold on.
And then we ran some code on it during the show. And he's like, oh, let's try that on ARM. And then spin up another 2,000 on ARM Linux machines. I'm like, okay, that's nuts. But let's just. That's a lot of power. So I was impressed, but Patrick, sorry, I kind of did realty there.
Let's talk through it. Yeah, so you do uvx FastAPI app, FastAPI new, then you specify the name of the application. And that's almost there. You just need one more command to deploy, which is FastAPI deploy. The first time it's going to ask you to log in or join the waiting list if you haven't been invited yet. It's still in beta. And then you follow the steps. So like FastAPI deploy, log in, decide the team.
If you have multiple teams, design the application name, and then you wait a few seconds and the application is going to be live.
And just to be clear, FastAPI new is not required if you already have a FastAPI app. If you've already written your own code and you have your application, you can just go right into logging in and deploying. This is just so that if you're starting something new, you don't have to do any thinking about all the right things that need to be there. So this is more of a greenfield application. I'm bootstrapping a project.
Right, right, because you want to have the best structure. Now, it uses uv. It is nodes required. Yeah, I was going to say, do I have to use the uv project management type of thing? Do I have to use the uv.lock files and uv add uv sync? Can I do requirements.txt? What's the story there?
Yes, so we support uv with uv lock. We also support the, forget the name, the other, the PyLock file. And we also support plain requirements.txt. And maybe something else, I don't know, Jonathan, can you?
PyLock's pretty new, right? I think Brett Cannon just got that out pretty recently, right?
Brett was pretty excited.
I know.
Implemented that.
Oh, was he? Okay, I'm sure he was. That's awesome. He put years of work into that.
And he also said that one of the motivations was also like, you know, like cloud providers. So it's like, yes. The other thing is like, you know, if you use other different package managers, if they use the standard PyProject Autonomous format, that will also be supported. That means that, you know, like if you use PDM or if you use poetry with one of the recent versions, like that will work.
If you use a very old version of poetry or like you use some other strange package manager or something, that will probably be problematic. But for like most of the use cases that use the standard package formats, it will just work. And if you use uv, then like you're going to have the best experience because we are fans of uv and Astro.
They've definitely put a dent in the way that sort of Python gets started and making that a lot easier. So it totally makes sense. And also, I noticed, speaking of uv, that there's, at least in the recommended way, or the way in the docs, let's say, it doesn't say, here's how you install FastAPI. You just, here's how you run FastAPI-new, leveraging uv, which then will silently install and manage. All right, that's pretty neat. That helps you guys tell a simpler story, right?
Instead of, here's how you create the virtual environment to install our thing and so on, you know?
The idea is to make it like, as I was saying, just super simple for people just to start from scratch. Like no idea how to create an app, how to start, how to create an environment. It's just you run this command and you're off to go. Off to the races, I'm missing sands. Anyway, that's what Colombians do. But then if you already have an app, you have like, you know, like anything with FastAPI standard installed, then like that also just works.
And Savannah, you pointed out that it doesn't have to be a new project. If you want to start from an existing one, that's totally fine. But what do I got to do if I'm starting from, if I'm migrating an existing one? Like how easy or hard is this?
I have some like legacy project demo apps I've built at other companies I've worked with that have used FastAPI. And I literally just ran like FastAPI login and then FastAPI deploy and it just worked, which felt really magical.
Right. Like I think that's like, I don't know, like having worked on cloud products for quite a while, like I think one of the biggest gaps is like the just I don't know, like the disparity between like my local dev environment and what is actually like lives up in the cloud somewhere. And so being able to just run one command and having the project as it exists on my machine go and work somewhere without having to think about like the infrastructure.
And of course, like, you know, we want to be like amenable to folks who do want a little bit, you know, like higher touch. But we also want to work for people who are like learning FastAPI and Python, right? Like educators and people that are teaching Python. I think this is like something that you've had some interest in as well from those folks.
Yeah, I was just listening to the Teaching Python podcast books just the other day and thinking, you know, like this, when I look at this, I know this is not necessarily your focus, but certainly people who are trying to teach a class, be it college class or high school class or whatever. And if you build anything on the web, the next question is, this is cool. How do I share it with people? And then they're like, oh, no. Oh, no. Hold on.
Like coding boot camps, right? Like if you're teaching someone how to write Python or how to build an API with FastAPI, like actually setting up the environment for them to deploy is not part of it, right? Like that's not actually part of the curriculum. It's like this peripheral thing that ends up eating up a bunch of the educator's time or the student's time trying to understand both like how to write code and then also understand cloud stuff.
And that's like a lot to ask people when they're fresh up the gate.
I feel the same way about like tutorials and stuff at conferences.
Yeah, totally.
Yeah. Or training sessions. If you're doing like corporate training or like, they're all like, Oh, well, let's get everybody's machine working. There goes an hour and whatever. But yeah, if you can just say, look, I think when you're either, when you're trying to learn something, you'll be it through school or on your own or through these like more structured ways,
like bootcamps and training and so on. I think if it's not the main purpose, I feel so often there's like, we're going to do 20 steps for four hours before you get any sort of reward of what you've done. And if you can go, okay, do you have it running? Okay, now you run this command. Look, now it's on the internet. Like, oh, wait, awesome. I got an app on the internet. Everybody look at me. You know what I mean? And I think shortening that cycle to where people can
have that aha moment. And then later they can dive into like, well, how is it really working? And what do we really need to understand? But that quick iteration cycle, especially in the early parts of
in new tech. It's really important. But also, you know, like down the line as well, I think, like, I don't know, there are so many things that I have been wanting to build and I don't, but I didn't because it was just so complex to deploy stuff. You know, like knowing, knowing how to do the whole thing, how to set up the clusters, the machines, install the Linux systems, deploy the cluster, whatever, like all that stuff, deploy the things,
handling load balancers and HTTPS. I'm like, you know, like I know how to do that. I built one of the most popular websites teaching how to use Docker to ARM, which was like the contender before Kubernetes won everything. I like it. But still, it's just so complicated, like doing all those steps that are like, yeah, no, I'll just not do it. Like some other day. Now I can just like play around and do random stuff and just like deploy when it just works. It is, I really like that.
I guess like coming back to that, like taking one for the team point earlier, like I feel like building Python tooling. It's kind of like taking one for the team sometimes because you have these folks that are like, you know, brand new to Python. Like Python is an extremely approachable language for people who are new to writing code. But then, you know, we also want to make FastAPI
cloud work for someone that's building like an enterprise grade application, right? And so like, like pretty wide spectrum of folks with like a million different use cases and different types of applications they want to deploy with different constraints and like security stuff. And like, so yeah, I think, I don't know, maybe that's just like Python tooling. It's a lot of work, I guess, to like build something that works for the masses.
Yeah, well, it's certainly tough to make something that feels simple, but it's not overly simplistic, you know, that can actually solve the problems.
Has the right knobs for the right users too, right?
I would argue we're not only trying to do it simple and easy. I feel like we're choosing a particular flavor of simple, which is... We have this discussion a few times. It's like, if you make a cloud, how do we make it feel Pythonic? What does that mean in a cloud setting? We talk about Pythonic libraries, Pythonic coding style in the community a lot.
And now we kind of try to transfer that flavor, that feeling to the cloud and make everything around that feel just like we want our libraries to feel. So you feel at home as a Python developer and it just feels right. So that's extra step on top of making it simple. And we discuss that a lot. That's how I feel about it. I love it.
I think it's one of the coolest things about this team. Like, you know, like people are being able to hear a few of us. There's like, there are like a bunch of others, but like that each one of us is so passionate about the things that we are working on. So like, you know, like each one of us is trying to make the best out of the things that we are building. And then like, we are so passionate about the thing that we care about and that we are building.
that I think that ends up being an amazing result. For example, the CLI. We wanted to have some specific, you know, like behavior, some look and feel. And like we wanted to be able to have like the best kind of CLIs. So Patrick went ahead and built this bunch of tooling that we needed to be able to have it and like made it open source and everything. So we could have this great experience when working with CLIs.
Jonathan recently was doing so much stuff about the something that caches and handling security, making sure that everything was super secure, super fast, super snappy. You know, like Alejandra is super careful about all the UI. Martin is super careful about all the infra. You know, it's like this passionate mess, which is a word I just made up. This, Alejandra goes and says, like, this thing doesn't have the proper margins. We need to increase this a little bit. I don't like it.
She just goes and fixes it. The same with Marvin. He says, like, we need to have, like, this sort of thing in infrastructure. And, like, just comes and tells me, hey, we are doing this. And he's like, yes, sir. Like this with the OpenVPN, like, Unix, for example, that is mainly focused on the open source, is constantly looking at all the discussions, PRs, conversations, making sure that everything that we do, that doesn't.
So why, you know, like, there have been, like, recently way more releases of FastAPI friends of the open source projects and very fast book fixes, very fast responses to handle everything for the community. Now we actually have people that is paying attention constantly to what is happening, what are the things that we have to do, and that really care about that part as well. So I think this extreme care about what we are doing. You know, like Savannah is making Python.
This detail that each one of us cares so, so much about each one of the things that we build, making sure that the product is actually amazing. It's as good as it can be, and we can all feel at home when... I get so excited for talking about it because I really enjoy the end result of the product and of being able to use it. I would use it in the end. I would use to work with it. It's super simple.
Yeah, that's awesome. Hey, let me adjust your mic real quick. I think it was like ducking, ducking out a little bit.
We just went through a lot, a lot of content and a lot of sweating because your microphone went through like six different stages of weirdness.
I think that really leads to like something I wanted to talk about is just what impact has this had on FastAPI? And before you jump in and answer that question, everyone, there's especially I think with Astral, but with because they've had so much success, there's been an undercurrent of concern of like, oh, my gosh, commercialism is getting into our open source. And what if it pollutes it and causes these negative aspects?
But just hearing all of the energy around FastAPI with so many people, because of FastAPI Cloud, that's super neat. So I wanted to throw out to you all, how has this building FastAPI Cloud and the existence of FastAPI Cloud been giving back to FastAPI, I guess?
I'm waiting to see if someone will speak FastAPI. I'm always the one that is speaking the most.
I mean, it might be your project. Like, you may have started the project.
Yeah, maybe so.
Like, last year, I had, like, a few keynotes in some picons in different places. And, like, one of the key points that I wanted to bring was this idea that I'm trying to show that, in many cases, people worry about the boss factor. And the boss factor is just this idea.
Yes, yes, I've heard this, yes.
Yeah, you know, like, the boss factor is the idea that, oh, what happens if, like, there's one person doing this work? What happens if a boss runs over this person? And there's so much worry about this boss factor.
It's sort of a morbid analogy, but I understand, right? Like, what will happen to the open source project if the maintainer vanishes for some reason, right?
Exactly. But, you know, like, it also applies to projects and to many other different things. But what I think is that it's a disproportionate amount of attention to this detail of the boss factor. And I think every time people talk about the boss factor, you know, like one of my points in what I was trying to say in these talks was I would like people to think about the boss ticket factor. Who is paying for those tickets? It doesn't matter how big is the team.
You know, like you have seen Google, Amazon, Meta, all the big ones. They don't have a small boost factor. They have a lot of people in their payroll and still they finish products. They just cancel them. Open source or private or whatever. is not the main factor defining the success of a project, being it commercial or open source of any type, is not really how many people are behind it.
It's more of what is the value that whoever is putting the effort to keep it alive is getting from putting all that effort. It could be just satisfaction. It could be like open source, like, oh, I feel so good that I'm contributing to society. And that is valid. It doesn't pay the rent, but it's still valid. It might last for a while.
But then also like, you know, like when you see like there are so many Python projects, so many Python, so many open source projects that can do well or can do bad. And it doesn't really depend on how many people they have. And when you are using a project, when you're using an open source project or when you are using a product of any type, I will encourage you to think about what is the best ticket factor of this project?
What are the things that whoever is building this is receiving in exchange for giving it away? So like, you know, like what are they expecting to sell you at some point? Or what are they receiving in exchange? You know, for example, Bun, the JavaScript Brompton LiDAR. Like it was like, we don't know what they're going to sell. But now, you know, Cloud and Entropic really want to have like this thing keep working because they are using it internally. So you can say like, OK, I'm going to use it.
I'm going to use it for free. I know that what they receive for me using is just like that they just really want it. So I can just like, whenever you are using bond, you are getting, now you are getting free services from Antropoc, that's it. But you know, like every time you are using a project, you can think about why are people receiving an exchange for giving this away for me? This is like the thing that I would like people to think about, you know, like also like how can they give back?
Maybe they can actually contribute to that community or to that project. There are many ways and in many cases, the thing that is needed the most is just like help and work, just answering questions and issues.
this portion of talk python enemy is brought to you by us i'm excited to talk about my first solo book talk python in production it's an inside look at how we host all the talk python sites apis mobile apps and way more here's the thing i believe most hosting stories sold to developers and data scientists are way over complicated and overpriced you've heard me say you're not google you're not netflix so you shouldn't run your infrastructure the way they do but if not that
then what? This book is both a blueprint for what I chose for Talk Python and a story arc of 10 years of running my own infrastructure from a complete newbie, apprehensive to Linux, to some pretty neat infrastructures code DevOps. It covers Docker, Nginx, Let's Encrypt, self-hosted analytics and monitoring, CDN setup, framework migrations, and a whole philosophy that I've termed stack native, keeping things streamlined, powerful, and free of cloud lock-in. And it's more than just your
standard tech book. It comes with code and figure galleries on GitHub, a discussion forum, and something unique, over an hour of audio readers briefs, short conversations that bookend each chapter to prime your focus or broaden your takeaways. Oh, and 0% of this book was written by AI. Every word is mine, written over the course in high months, for better or worse. I've made the first third of the book available for free online. After that, you can grab the DRM
free EPUB and Kindle editions. And I'm working on a paperback edition as well. Please check it out at talkpython.fm/DevOps, or just click book in the nav bar on the website. It's a great way to support the podcast. And I hope it changes a bit how you think about running your apps in production.
Kind of related to what you're saying, I think one of the angles that I really appreciate about the way we think about FastAPI and FastAPI Cloud is like where like a lot of our team was involved in open source before coming to work at FastAPI Cloud on various projects around the Python ecosystem, outside of Python.
And I think all of us have deep appreciation and understanding of the value of open source and really, really try and build in a way that is like, I mean, Sebastian, you've talked about this a lot, but solving a real problem for folks, right? And so FastAPI Cloud is sort of this extension of this open source ecosystem people would be using. FastAPI Cloud may be an option. Maybe someone picks some other cloud for some reason. I don't think like, I think we're all very mindful of that.
But like the angle that's very cool, I think, is that like, because we all work at FastAPI Cloud, like I know that I personally have time, more time for my open source work and my employer understands the value of my open source work, which isn't that positive for the open source community. Like I get to work on CPython sometimes and I have, you know, the bandwidth to go and do my steering council work or upcoming release management work.
I understand like this sort of like, tempering, like open source, commercial, bad, all bad. It's not all bad. It's actually like really good in a lot of cases for folks to build business.
Look at uv for an example to hold up, right?
Astral, yeah, yeah, totally.
Yeah, yeah.
I think there are some really good examples of this. So I think like that's another angle that, I mean, I really, I get a lot of energy out of our team because we all, I don't have to, I don't have to fight the open source battle at FastAPI Cloud. I think that's really cool.
I do think that's super cool as well. Let me put out two examples for you. here that I think everyone will be aware of as sort of to add to what Sebastian was saying is look how much Apple freaked out when Steve Jobs died and how many people work at Apple, right? Like that was still like, oh my gosh. But, you know, I think there's, they're hanging in there.
They're going to be probably making it. They are not in our business. I tell you what,
they got some of my money. That's for sure. But also, you know, look at Flask, right? Armin drifted away, which is totally fine. And David Lord and Pallets picked it up and kept running, right? Like it's still one of the most popular frameworks out there, right? So it's, I think the bus factor is over, overblown a bit, but also looking at the team of folks here, I think it's, it's even more obvious that there's a bunch of people who are on the inside, you know?
For example, Flask, you know, like I learned so many things from Flask and like, the thing is, I feel like sometimes, sometimes people go and complain about the tool and say like, oh, this is not working for this or for that. And in many cases, it's in this insensitive way towards the people that are working on that. And it's like, you know, like in the end, realize that there's actually people behind the scenes doing the work. And like, in many cases, it's just like
one or two people doing a lot of work in many cases, just for free. And, you know, like, I think it's worth calling that out. Like all the work that David Lord does for Flask is just like so
much work. And yeah, deserves a lot of respect. I totally agree. The other thing that I forgot to
mention is that there are so many ideas of potential products that I could build over the years, and I never did, and I never started a company because I didn't have clarity of what will be a good thing to actually sell and will have a good alignment. The cloud product has such a good alignment with the open source side because as more successful FastAPI is, the more successful FastAPI cloud has a potential to be.
The more people using Python effectively, the more people might end up checking out FastAPI and the more people might end up checking out the product. So if FastAPI does well, if the open source does well, if Python does well, that's better for the company. So it doesn't really depend on my personal principles and values or something like that. It's aligned with, it's financially aligned with the company. So it's just going to be beneficial in the end It doesn't depend on good intentions.
And FastAPI is open source. It has like 7,000 forks or something. So if a boost runs over me, there are 7,000 forks. It's not going away.
I definitely agree with you on that. I feel like I should maybe give a little bit of a, I'll tell a little bit of the story of what's going on with, where did I put it? I don't think I pasted it over here, is what's going on with Tailwind right now. And I think Tailwind is having a tough time, Tailwind CSS. Traffic to Tailwind is up six times year over year on npm downloads. But the revenue of Tailwind is down five times.
You know, I mean, these are completely out of whack things because instead of people going to docs to learn about it, it's just like, well, when you go to the docs, you learn they also have premium offerings, right? And I think you guys are different because it's not just, oh, here's a little bit nicer of a thing, right?
I feel like it would be a little bit as if you were selling cookie cutter templates for FastAPI apps, you know, it's like, well, the AI can make the shape of the thing that comes out of the cookie cutter, to be honest. But you're offering something that has ongoing value that it costs more and is more complex in other places. And so I think maybe just thinking about the how this just keeps the team going for FastAPI is really awesome. And I think it's got a nice flywheel effect there.
is I'll link to this, I guess, audio track. I don't know what I call it. It's a blog post that has one sentence, but a 30-minute audio you can check out from the guy, Adam, who's one of the founders of Tailwind, talking about going into this. It's kind of rough. I think I don't necessarily want to go into a deep AI, what it means for the industry. Like, let's stay focused on what you guys are doing. But I think it's going to be its own series.
I mean, Stack Overflow had as many questions asked this month as they did in the first month of their existence, right? Three or 4,000, whereas at their peak, they were 200,000 questions a month. There's like real turmoil that's coming from some of these things, which is tricky. But I'm really excited to see you all doing this because I'm a big fan of FastAPI. And I think this is just sustaining and more for FastAPI, right? Like, what do you all think?
That's what we hope that is going on.
I thought about Taiwan for a second, right? It's not like we're immune to what happened to them. Like we also have a lot of documentation online. AI could train on that. And if it's good enough, it could maintain your infrastructure and stuff. It's just too hard at the moment. And there's an additional thing we're kind of selling, which is like, I guess, responsibility. Like you're shifting the risk from like letting your AI or your infantry team maintain your infrastructure to us.
So we're staying up at night and worry about it. that has a lot of value as well. And that's probably not going to get removed by AI.
Here's a very common cloud code, cursor, whatever conversation. Hey, build me something with Python and needs an API. Okay, we built it with FastAPI. How do I host it? Right, that doesn't just, it will build a cloud for you, right? It's going to recommend something out there. And a real natural way to how do I host FastAPI is FastAPI cloud, right? Like if it suggests, oh, you're just going to like spread it across Lambda by breaking. Like, whoa, no, I want something simple.
Okay, give me FastAPI cloud, right? I think that that's a really good thing. And then on the enterprise side, enterprise folks are notoriously not good at supporting open source in that they're not like paying for it. I know some companies are big supporters of the PSF and Python and open source. But in general, it's like, yeah, we have this project with 5,000 people working on it. It's all Python. And are we sponsoring this? Nope. We're just enjoying the money, right? And we're a bank.
So we got the money. We got all the money. So they're just not good at paying for like a really great framework that they use a lot. But they got plenty of hosting, plenty of internal apps that they just need to make run and stuff. So I think both on like the low end and the high end, there's a lot of synergy between these things.
That is not just, you know, slightly advanced, not to diminish it, but slightly advanced UI widgets that you could ask your AI to build or something or like cookie cutter templates for project starters.
I think we are in a somewhat fortunate position of like, you know, like FastAPI. FastAPI has grown so much. Like, you know, like when you check the statistics about downloads or GitHub stars or entries in developer surveys, like it's at the top in like in each category. It's like, you know, like the backend framework with the most GitHub stars across languages, even like, you know, like Java, Go, Ruby, JS, like whatever. It's like the top one, at least in GitHub stars.
So like, you know, like FastAPI is like people are liking it, fortunately. And there's probably going to be people deploying things to FastAPI Cloud. So that's probably going to be like, we are probably going to be fine. I think, you know, like the, I guess it will be like a good point to ask people to go and check where the open source project is that they are using and check where is the bus ticket factor for those open source projects.
You know, like if you are using Tailwind CSS, it would have been very cool if at some point you check if the premium things were useful for you and for your company or your project or something like that, you know? Yeah, because what is the thing that keeps that project going?
Exactly. And I really personally admire if a project or something offers like more value, not just, hey, buy me a coffee, but here's a thing that you get way more of, you know? And in that regard, I think Tailwind was doing that, right? They were offering this suite of pre-built things. And I think that that's great. But yeah, I do think you've got more of these crazy AI things are going to maybe recommend FastAPI Cloud more than they're just going to undercut it. So I think that's really great.
And by the way, I was just looking for the GitHub Stars graph. Like there's a whole, I can't remember what the domain of that site is. And I ran across, by the way, I just want to give a quick shout out. Like your cult repo documentary on FastAPI was awesome.
Right? That was so fun. They made me look good.
I didn't see that coming. Yeah, it came right on the heels of the Python official documentary, the one hour one. This is the same group, and the production quality is really nice. So like--
When they released the trailer for the Python documentary, before releasing the documentary, when they released the trailer, they contacted me and said, hey, we're doing these mini documentaries about different frameworks, different tools, and we want to include FastAPI there. I was like, oh, nice. But then I was just trying to stay excited, but super excited.
Oh, that's so cool. Yeah, I watched it as soon as it came out. So I'll link to that. People should definitely, it's only like 10 minutes or something, but it's worth it. We're checking out. So it's not a huge investment time. People can watch it, I suppose. It's not TikTok. I mean, it's not like, oh, I saw the documentary, but it doesn't take you on huge about it.
You have to listen for 10 minutes, overly excited Colombian.
I don't understand what's happened to the attention span of society. I'm really, honestly a little concerned. I used to, when I would create my courses, people would say, you know, like a four hour course and there'd be like a 10, 15 minute sort of, Hey, here's how you set up your computer. And here's all the introduction and people, Oh, that's so awesome. I loved how you kind of set the stage. I'm really motivated to take the course.
Nowadays, I just get messages like, why are you still talking? This is five minutes long. Do you understand? I'm like, this is your job. You can't spend five minutes. Oh my gosh. Anyway, that's, that's sort of the origin of my comment there. It's all right. So we're kind of getting so much time, I think I want to talk about a couple of things. Let's talk a little bit about internals. Like what, I don't know who wants to take this one, but let's talk about just how, when I say
FastAPI deploy, then what? It's just a uv pip install and it just goes and it's magic and it's
easy, right? We have a nickname for Jonathan. Can we say it or no? I don't know. It's so funny.
This happened because I told my friends, I'm so concerned about being at the podcast because Because everyone here is a visionary, and then I'm the back-end guy. I think the things I could contribute to this conversation, I should probably keep to myself. But you're just leaking your turnouts, right? There are some things that are not really secret. Like, as Sebastian said earlier, Kubernetes 1 in the infrastructure and deployment field, to some extent. So that's somewhere in there, right?
But it's all the way deep down, so no one has to worry about it. But it's still a foundation. which is a good foundation. I think one thing that's, you might have guessed it, but FastAPI Cloud is built on FastAPI, which kind of makes sense, right? And that also has an effect on like recent patches, updates and stuff. Because if we find something internally which we're not happy with, then we just fix it. And that's how some releases came out faster than months before.
Power of dogfooding.
Yeah, that's awesome. Dogfooding a lot. Also all the related libraries like SQL model and, well, others. they experience the same thing.
New library is coming out. Patrick will announce at some point soon.
It's not just FastJPay and friends. We're like really open. Like recently, Patrick just open-sourced everything we use for authentication authorization, for example. Is it open-source yet? Did they just leak something?
It will be announced soon at some point.
We build stuff internally in the moment really. Like we build it in a way, like in a separate package, just like an open-source library. And if we feel like the time is ripe, it's just getting open-sourced because a lot of things are reusable. And that's in all departments. That happens a lot. When I started there, I already realized that. Everyone was building open source, but now I joined in myself as well.
I open source the library for compressing and decompressing archives in Python because the internal top high thing is just slow and we needed it to be faster because we're staring at the deployment process and we're like, hey, we could probably shave off a few seconds here. Then that's just open source for everyone to use. So we're contributing to the old Python ecosystem as well.
You have to say the name. It's so good.
Is it good? No, it's just, it's faster because it's, you know, faster than just tar.
Fast tar? I love it. Fast tar, yes. And you can say with that very, very German accent, fast tar.
I'll go star it. We'll get you some stars. This is going to happen.
That's the irony about it. Like, it literally has no stars. But if you scroll down, you see the downloads. That's going to prove we're actually using it.
Yeah, I like it. It's a little context manager.
It's almost working the same as the TAL file in the standard library. Like the same, like almost similar API to that. It's basically a drop-in replacement, more or less.
But they know they need everything to happen in Rust.
Because Rust. Because Rust, yeah.
Well, as soon as it becomes infrastructure and you've got to run it a million times, that starts to make sense, right? Yeah. Python is one of the fastest programming languages in the world. when you think about human time to build the things, right? Like that's one of its real superpowers is like, I mean, there's the whole story of Google Video and YouTube, right?
And Google Video was written in C++ with 100 engineers and YouTube was a small team in Python and they just couldn't keep up with the features. So they bought this little old thing, YouTube, and see if we're going to make something with it. And last I checked, it was still in Python. I'm sure some of it isn't, but a few years ago it was, which is wild. Anyway, there's different ways of fast, But when it's down to like little utilities, yeah.
I know some people that are trying to make Python fast. I know a couple.
Yeah. And honestly, massive success in the last five years, right?
Like since 3.11, since the specializing adaptive interpreter, there's been pretty big improvements.
3.9 and 3.11 did a lot of like foundational work. And then 3.9 onward really just uncorked a lot of innovation there. Yeah, that's pretty awesome. All right. It sounds like, Sebastian, you've talked a lot about Kubernetes. So I imagine Kubernetes is happening. Do we get to pick what data centers it runs on? Do we get to pick what clouds it runs on?
You're going to get to pick some of these things. Not yet. It's not released yet. But, you know, like it's top, of course. Like we have like regular cloud providers on the MIT and there's a bunch of Kubernetes. Then there's a bunch of additional stuff that needs to run on top.
Then there's like custom Kubernetes controllers and things that Jonathan was saying that he's having to write in Go so that people in Python can be happy to be able to, you know, like manage all the Kubernetes shenanigans that need to happen because there's so much complexity that needs to be handled. There's a lot of that. We do a lot of advanced tricks also. Jonathan was recently doing a bunch of advanced tricks to handle the caches for the builds.
So the way that we handle caches, and we also like tap into uv and how things work so that builds can be super, super fast because it's like something is, we are, you know, like we are very much targeted at FastAPI and Python in general. So we can take advantage of knowing how things run internally, how things are installed, how to optimize everything. So everything is just like super fast, super fast to install, to run, to like do everything.
I imagine you all have base Docker images that are like just one layer away from whoever's code is running. You know, like you've got it all optimized, already pre-built with FastAPI and whatever settings of Python you want.
A bunch of things and tricks. But there are also different things, like the different ways that we do to actually build the things and install things and put them inside of the actual build application. There's a lot of sourcing that we do there, and Jonathan has been working on a lot of that. And there's also all the logic and all the stuff. We have a bunch of stuff on top of that to handle out of scaling, which is something that is actually not that easy to find in different providers.
We have auto-scaling based on requests, including scaling down to zero, which saves costs. But this is not Lambdas. It's not AWS Lambdas. It's like the full deployed application, the full container or whatever it is, which is the full thing with all the dependencies. It's running for whenever it has to run, but we can scale based on requests.
So I guess it's like the type of thing that you will have if you have this giant cluster for a huge enterprise with a bunch of infra people making sure everything just works perfectly. But you just pay us to do that for you.
This is also a good time for us to probably say lots of stuff is coming and we're in private beta. And so you should sign up for the wait list so that you can get admitted and try out these very cool things we've been talking about.
Absolutely. And I think I'll let Tech Insider out in the audience sort of lean into it.
Public release one. Sebastian, when? Public release one.
My final topic, which is just what's the roadmap? When is this stuff? Like, how do we get into it here? Why would they like Litestar?
We have the, right now we have the waiting list and we are onboarding people. We already have like a bunch of people in the private beta. We're going to keep onboarding people from the waiting list and like, you know, like ramp that up. But it will be like, you know, like through the waiting list is the main place where we are onboarding. People will want to make sure that everything is super fine-tuned. And we're going to keep it that way for a while.
So like people that are on the waiting list are going to be like the ones that are going to be able to start using it the soonest. At some point, we'll probably have ways for people to invite others and things like that. About the things that we are building, we want to, you know, like we are super focused on FastAPI and then Python in general. at some point will probably support different tools, different ways to run, also like Python code in general, probably different frameworks.
It will also depend a lot on what the users are asking for, whether like the tools, the frameworks, the use cases, the things that they need to build. And like, we're going to evolve the platform and the system based on what people need out of it.
We have like a GitHub repo where we have issues, but we also have like a Slack that once people are admitted, they can talk directly to us and that feedback is really, really valuable for shaping the roadmap and figuring out all the fun things you want us to support.
Awesome. Of course, you're going to charge money for it. It runs on servers and you guys are not a charity, but can you give any sense of what you're thinking about that kind of stuff or join the waitlist and see?
Well, first join the waitlist and see, but we don't have like that predefined yet, but they will be on the ballpark of what you could get from different cloud providers. So different similar-ish providers will be on the ballpark of what you will get. But it's not written in stone yet. It's still a little bit different because we can auto-scale based on requests.
So we can increase the amount of replicas of your application automatically, and then we can decrease them automatically, and we can scale down to zero. So you can probably handle all the load that you need and in the end spend a lot less because you don't have to have a bunch of instances constantly running or things like that, you know. So it will probably work a little bit different than what it will be for other providers. But in the end, it should be roughly similar.
Okay. And given the fact that you all handle so much of it as a platform as a service type of thing, you don't have to have a cloud expert on hand or a DevOps expert necessarily, right? As soon as a company hires somebody to be an AWS cloud architect or something like that, it's no longer just what is your AWS bill.
It's also a little bit of pain that we are swallowing so you don't have to take it.
Exactly. It's part of taking one for the team, right? Yes.
Yes.
Indeed. All right, so I had one or two things specifically that I was seeking. It's like custom domains. How far off are custom domains? I was like, oh, I could put some cool things on there. I could tell Jonathan is psyched about this. It'd be really fun to put one of my really small FastAPI projects over there, something I set up for some of my courses or something, and then I can point people to go, look, it's running on FastAPI Cloud. How neat, you guys can check that out over there.
And I'm like, but it's on its own domain, that domain is baked into the course videos, you know what I mean? And it's written in stone. It's marketing. Yeah, exactly. So I can't really move it because it has, you know, some subdomain of Talk Python, right?
I was working on it. And then I got the notification by Google Calendar that I should join a certain podcast. So...
Are you telling me we don't have custom domains? Because I'm here asking you about custom domains. How meta is that?
You got it. It could be here already. But no, you have to wait a bit more.
Okay. But soon?
Yeah. As soon as broad enough, but I'm actively working on it. Let's put it like that.
Okay. That sounds great. And then, I mean, just, it's never simple. You know, I just, I set up some stuff and it's like, you get the pop-up. Oh, you got to put this, you know, this TXT record or this CNAME or whatever record into your DNS and then we're checking it. Oh, it might take three days for your DNS to propagate. So hang in there and just, I can imagine like
you're having fun yeah i guess you're kidding me that's like wow i i thought i'm almost off work but no you're bringing it all back but yeah that's a that's a thing i'm sure the company
could support therapy to like work work through the issues and the trauma that you've suffered from the dns it's always dns that's right i mean you got that's an yes it's always dns yes
i guess one of our goals with custom domains also to make it super simple for you to set up them Like, for example, if you're using one of the providers that support OAuth, we can also just do one click and then it's going to be automatically. Oh, that's cool. Yeah, that's really nice. But unfortunately, it depends on the platform you're using. All of them support this.
This is said by the person in charge of most of the integrations. So Patrick has built, we have integrations for a bunch of database providers and things like that. I think now Patrick knows by memory, open ID specification. I don't know.
Yeah, the other thing I wanted to talk a bit about was just integrations, like what kind of stuff you guys have coming in. I saw that Hugging Face is going to be integrated soon. You've got Supabase, which is kind of Postgres as a service. There's a lot of those things out there that theoretically could be added.
Someone also asked for MongoDB. Maybe that's one that we're going to take a look into. It really depends on the provider. So at the moment, we don't want to ask databases for you because that's also another kind of rabbit hole. Jonathan is probably not ready for that. But yeah, definitely database. But I guess we can say that we're also talking with the people from Pydantic so we can integrate maybe Logfire automatically, that kind of stuff.
Yeah. And also things like Redis, which is also another kind of database.
That's also coming soon. Yeah, there's a couple of database as a service type things that don't require too much other than just connecting API keys and something like that, right? Those seem like low-hanging fruit.
Like the kind of goal with the integration is not just done. Like, yeah, right now it's just setting up an environment variable. But the idea is also to more, I don't know, like the proper integration, I would say. Like, for example, for things like Superbase, if, yeah, I think that's support branching. Like, for example, once we support ProQuest Previews for GitHub, like we can also create a branch automatically for you if you have the Superbase integration enabled.
And we can do this kind of stuff as well. Or even we could show like some information about database. I don't know, like load or like memory usage, things are directly from our dashboard. So you don't have to go there. That's the main reason why we're building this infrastructure
for the integration. Well, people can sign up to the waiting list and hopefully get on the private beta.
We actually check the waiting list. We actually check the use cases, team sizes, like what are people building with it? Like we actually go and check it and we bring in people from the waiting list.
Nice. You know, I didn't join the waiting list directly. I was added by some guy I know who was very kind to help me get some behind-the-scene look. So I don't know what the process is. Do you actually say what you want to do with it? And you evaluate that a little bit as well based on, like, hey, this would be a cool use case for us to support?
There are many types of applications and many types of different team sizes, many types of things that people might want to build. And we try to see, like, okay, where is a case where we could be a good fit and we can provide a great service? And where are the things that people are trying to build? Also, it also helps us see, like, you know, like, what are people trying to do with Fasted Vehicle so that we know what we have to provide?
But we actually go and check those, you know, like those submissions on, like, sexually thousands of people in the waiting list, but we still go and check and approve kind of manually still to bring a bunch of people on board in the different ways that we have been bringing people. So if people go and join the waiting list and actually tell us what they are, what is their use case, their team, what are they planning on doing?
There's a much higher chance that we are going to go on to bring them up.
MARK MANDEL: Awesome. So everyone, go join the waitlist. If you're doing FastAPI, I'll link to it in the show notes, of course. Thank you all for being here and sharing the story. And I, for one, am very excited to see FastAPI Cloud exist and just one more way to make FastAPI stronger and more resilient and so on.
FRANCESC CAMPOY: Thank you very much.
Thank you for having us. Yeah, it's super fun. Thanks for having us. Yeah, you bet. Bye, everyone.
Bye, folks.
Bye-bye. Bye. This has been another episode of Talk Python To Me. Thank you to our sponsors. Be sure to check out what they're offering. It really helps support the show. This episode is brought to you by CommandBook, a native macOS app that I built that gives long-running terminal commands a permanent home. No more juggling six terminal tabs every morning. Carefully craft a command once, run it forever with auto-restart, Ural detection, and a full CLI.
Download it for free at talkpython.fm/command book app. And it's brought to you by the Talk Python in Production Book, an inside look at 10 years of the real-world DevOps behind the Talk Python sites and apps. Check it out at talkpython.fm/DevOps book. If you or your team needs to learn Python, we have over 270 hours of beginner and advanced courses on topics ranging from complete beginners to async code, Flask, Django, HTML, and even LLMs. Best of all, there's no subscription in sight.
Browse the catalog at talkpython.fm. And if you're not already subscribed to the show on your favorite podcast player, what are you waiting for? Just search for Python in your podcast player. We should be right at the top. If you enjoy that geeky rap song, you can download the full track. The link is actually in your podcast blur show notes. This is your host, Michael Kennedy. Thank you so much for listening. I really appreciate it. I'll see you next time. I'm out.